RE: Waking SMON Not Doing Trick

I think this little gem is what you are looking for. Listers, correct me if I am wrong about what this event does. Thanks to K. Gopalkrishnan for reminding me of it.

alter session set events 'immediate trace name drop_segments level ts#+1';

You get the ts# from sys.ts$:
select ts#, name from sys.ts$

so for ts# = 6, you would use:

alter session set events 'immediate trace name drop_segments level 7';

I think this event cleans up temporary segments like SMON does, but right away, without waiting.

Anyway, it should be easy to test. I know it is non-destructive to permanent segments.

--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton

On Fri, 21 Sep 2001, Bellefeuille, Wayne S wrote:



> Thanks, but if there wasn't enough space, then when I restarted it

> should have failed again, right?  I expect what is happening is that by

> the time I get logged into the system and restart the rebuild index

> process, SMON finally got around to cleaning up the temp segments.  That

> is why the index successfully rebuilds on the restart, but then an index

> later in the process fails.

> Wayne



-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jeremiah Wilton
  INET: jwilton_at_speakeasy.net

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).