Re: Problems with DBSPACETEMP

In article <7sfuli$1u6$1@nnrp1.deja.com>, Stephan Stresing <st@mr- informatik.de> writes >Hi, >we have IDS 7.30.UC8 running here on a Sun Solaris 2.6 box. We've >encountered a problem with DBSPACETEMP: we've set this parameter to >dbs1:dbs2 (and we tried also dbs1,dbs2) in the onconfig file. After >starting a big print job IDS claims temporary space to collect the data. >But after dbs1 runs full it doesn't switch over to dbs2 but fails with >an error message (I think it was -264); the essential result was that no >more space was left on dbs1. The only solution (or better: workaround) >we found out was to remove dbs1 from DBSPACETEMP definition and to use >only dbs2 where is a lot more space available for temporary actions. >Is there sth with this parameter or are we missing sth? >Any help/comment is appreciated! > Temporary tables are fragmented round robin under later IDS 7.3x versions. So you need all temp dbspaces to be the same size! Feature request anyone? >TIA, > Stephan. > >-- >Stephan Stresing > >MR Informatik GmbH >mailto:st@mr-informatik.de > > >Sent via Deja.com http://www.deja.com/ >Before you buy. -- David Williams