Re: temporary space - doesn't scale?

In article <3A37BFC4.CDCF8D26@cs.umass.edu>, Matthew Cornell <cornell@cs.umass.edu> wrote: > > What is the value of DBSPACETEMP? > Sorry. Here it is: > > DBSPACETEMP tempdbs # Default temp dbspaces> > tempdbs was created using: > > onspaces -c -d tempdbs -t -p ~informix/links/chunk2 -o 0 -s2000000 > > matt > This looks like it should work to me. Did you bounce the database after you added the tempdbs and changed the ONCONFIG file? I am assuming none of the tables in this are views. Maybe run update statistics on all of the tables. The only other thing I can think of is to do a set explain on; and then run the query, to find the query plan. Good luck, Will Sent via Deja.com http://www.deja.com/

If you do not have the opportunity to bounce the instance, you can set the DBSPACETEMP environment variable immediately prior to starting dbaccess. This will enable you to test the parameter change without possibly jeopardizing the other users. "William Rice" <ricew@operamail.com> wrote in message news:918jet$4hk$1@nnrp1.deja.com... > In article <3A37BFC4.CDCF8D26@cs.umass.edu>, > Matthew Cornell <cornell@cs.umass.edu> wrote: > > > What is the value of DBSPACETEMP? > > Sorry. Here it is: > > > > DBSPACETEMP tempdbs # Default temp dbspaces> > > > tempdbs was created using: > > > > onspaces -c -d tempdbs -t -p ~informix/links/chunk2 -o 0 -s> 2000000 > > > > matt > > > > This looks like it should work to me. Did you bounce the database after > you added the tempdbs and changed the ONCONFIG file? > > I am assuming none of the tables in this are views. > > Maybe run update statistics on all of the tables. > > The only other thing I can think of is to do a set explain on; and then > run the query, to find the query plan. > > Good luck, > Will > > > Sent via Deja.com > http://www.deja.com/