Re: ordebug flush

Hi,  

what is the case, if the user starts tracing using alter session ?  

is there any way we can stopit other tahn killing session/shut the instnace.  

Thanks,
Raj

Mladen Gogala <gogala_at_sbcglobal.net> wrote:

On 08/03/2005 09:34:09 PM, raja rao wrote:
> Hi All,
>
> Some session is throwing the trace which is causingg the mountpoint to fill up.
>
> But when i remvoe the trace, the space is not being reclaimed and mountpoint is still 100% filled.
>
> Is there any way we can stop the session throwing trace.

Yup. Turn off the event that is causing the session to spew trace. If the event is 10046, which is very rare, you could do something like:

exec sys.dbms_support.stop_trace_in_session(sid,serial)

If the event is not 10046, then the only recourse is to get into oradebug, attach it to the proper session and turn the event off like this:

SQL> oradebug event 10053 trace name context off Statement processed.

>
> I tried to use the below:
>
> oradebug setorapid nnn
> oradebug flush
> oradebug close_trace
>
> But that did not help. (at last I had to kill the session to stop trace)

Of course it didn't. The event causing the session to spew trace was sill active.

>
> Is there any way to stop trace for a currently conected session.

See above. Another way of would be to shut down the instance. I believe that "shutdown abort" can be used for that purpose.

-- 
Mladen Gogala
http://www.mgogala.com



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
--
http://www.freelists.org/webpage/oracle-l