Re: Temporary dbspace

paul.d.finkel wrote: > > I have created a temporary dbspace. It is referenced by the onconfig file > parameter DBSPACETEMP. It was made larger recently because our reports > explicitly create temp table using the "WITH NO LOG" option and the temp > tables created by 2 specific reports can get pretty big. > > It is being appropriately employed as I see temp tables being created and > eventually destroyed. Its size: 67500 2K pages. > > At this time it is down to "0" available pages free. How do I determine > what process is using that space? Where is the overflow(if any) going? > How do I free that space up for re-use? (Short of bringing down instance?) > What temporary tables (names) are being created in that dbspace? This would > lead me to understand which reports are using that space. > > Please e-mail and post reply. > > Thank you. > -- > Do unto others ... then split! > MaryAnne Stasium And the chain goes on and on and on.... I had the same question not too long ago. Here's the response: ---------- From: Dianne Pendleton To: Juan R. Guzman Cc: dianne.pendleton Subject: Re: Freeing up temp dbspace Date: Thursday, March 21, 1996 4:27PM You cannot free temp space when the session is gone. If the session was still there you could do an onmode -z and kill it. You have to bounce it. Isn't it a nice feature? I've had the same problem.... Dianne