RE: Tracing sessions

If the tracing event has been enabled at process level (with oradebug event) then the tracing will persist across all sessions within that process. However in normal case, when you exit your sqlplus/client then a disconnect is also done, causing process to die, so tracing will effectively be disabled.  

Btw, this v$session.sql_trace still shows DISABLED status when you enable the tracing using alter session set events '10046...'  

Tanel.

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Allen, Brandon
Sent: Saturday, October 28, 2006 05:51
To: Oliver.Jost_at_ca.fujitsu.com; oracle-l Subject: RE: Tracing sessions

The trace dies when the traced session dies. I've never heard of a trace being automatically restarted for a new session with the same SID and serial# as an earlier trace, but I've never tested it and I suppose it's possible. On a related note, old trace files will be appended by later traces/dumps for processes with the same PID.  

I just found that in 10g, you can identify active traces by checking the v$session.sql_trace value. This column didn't exist in earlier versions, but the information may have been there in one of the x$ table columns that just wasn't exposed in v$session, or maybe in a different v$ view, but if so I'm not aware of it. In 10g, the v$session.sql_trace value comes from x$ksuse.ksuseflg2, which doesn't exist in 9i.  

Regards,
Brandon
Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

--
http://www.freelists.org/webpage/oracle-l