Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Temp tablespace Database File Overgrown (20 Gigs)
Walt wrote:
> On one instance, the size of the TEMP01.DBF file is enormous - over
20
> Gigs (none of the other .dbf files are more than a gig or so) This
has
> maxed out the disc space - apparently it's just grown until the disk
has
> become full.
>
> Now, according to my research (limited, so far) this should clean
itself
> up automatically eventually, and bouncing the instance should clean
it
> up right away.
>
> That is not my experience. Bouncing the instance has no effect.
Try bouncing the instance twice. Never have found a good reason for that, but it has worked for me. I suspect a locking issue, since you can't drop a locked segment.
>
> Any suggestions? Since this is temp data, I should be able to throw
it
> away with no ill effect, right? Unfortunately, I'm not sure how to
> dump the temp data.
Note 47400.1 on metalink has an event you can set, but that didn't work for me (at least in 8i).
>
> BTW, I've verified that there are no permanent objects in the temp
> tablespace (SELECT * FROM DBA_SEGMENTS WHERE TABLESPACE_NAME =
'TEMP';)
>
> sort_area_size == 524288
> Oracle 9.2 on W2k3.
There's a doc on metalink 160426.1 you might review.
jg
-- @home.com is bogus. "An alternative is to wait until active transactions to commit." - from ORA-30036Received on Mon Apr 25 2005 - 19:39:31 CDT