That doesn't answer the question. Do you have temporary tablespace for SYS
or SYSTEM pointed at the tablespace which you have designated for temporary
segments? If so, then either SYS or SYSTEM is building temporary segments
there and it is quite normal. If you want to get rid of them, point
temporary tablespace for SYS and SYSTEM at the SYSTEM tablespace and then
bounce the database. At that point you should be able to shrink the
tablespace.
"David F. Newman" wrote:
>
> Kenneth C Stahl <BlueSax_at_Unforgettable.com> writes:
>
> > Do you have the temporary tablespace for SYS and SYSTEM set to that
> > tablespace? There are some instances where the engine itself needs to build
> > a temporary table that is persistant until the instance is bounced. Your
> > choices are either to accept that this happens or set temporary tablespace
> > for SYS and SYSTEM back to the SYSTEM tablespace. I've done it both ways
> > and have yet to see any adverse effects other than taking up space in the
> > temporary tablespace.
> >
>
> But my point is that the segments are persistant even after
> the database has been bounced. The reason I know is because
> when it created these segments I was already in the process
> of building a big index and so it put these other temporary
> segments at the end of the tablespace because that was the
> only place where there was room. Now that my index is done
> and those segments have long since gone away, those system
> temporary segments are still there. The problem is that I
> want to shrink that tablespace but I can't because of those
> segments at the very end of the tablespace. In fact, that
> segment has been autoextending and it grabs space at the
> begining of the file, as it should.
>
> --
> David F. Newman
> Oracle DBA
> dnewman_at_ourvillage.com
Received on Tue Sep 28 1999 - 08:10:06 CDT
