Re: TEMP tablespace problem

Thank you all, I found what the problem was.

Apperently there is a bug in Oracle 8.17: when you define a temporary tablespace and set it to no-logging mode it doesnt clean !

Ive checked it many times by running a large join in all possible situations and that was the conclusion. Now I set it to log mode and it doesnt grow anymore.

Guy Shilo

Karen Abgarian <abvk_at_ureach.com> wrote in message news:<3DC5FF95.D9845AA2_at_ureach.com>...
> Could it be that some piece of sw is actually attempting to use it?
> Check v$sort_usage and v$sort_segment.
>
> We once had a similar problem with the monitoring software.
>
> Regs
> AK
>
>
>
> Guy wrote:
>
> > Hello
> >
> > Ive been dealing with Oracle for few years now, but havent seen this
> > kind of problem before.
> >
> > When I install a new DB, I usually set a TEMP tablespace with
> > 200-500MB of space. And unless the database has really huge sorts,
> > this works fine.
> > Now I got a DB that was installed by someone else. The TEMP tablespace
> > grows and grows and it seems like it isnt cleaned at all. If I set a
> > size limit (say 500 MB) it eats it up in 2-3 days and then it gets
> > stuck with full tablespace. If I set it to auto-extend it continues to
> > grow and in about a week I end up with a 14 GB tablespace (then I have
> > to recreate it).
> >
> > Does anyone have an idea why this happens ? or any solution ?
> > Doesnt TEMP tablespace supposed to clean unnecessary data ?
Received on Wed Nov 06 2002 - 10:20:11 CST