Hypothetical situation: DBA sets session tracing to ON then starts (very) long running heavy-duty batch job but "forgets" about it, say - goes home... Other DBA takes over to see long job running even longer. Tracing may be set via: - dbms_system.set_sql_trace_in_session or even via - alter session set events '10046.... Disregarding the fact that tracing of long running jobs will create then continiously grow the trace file (which will be sure sign of tracing in progress), is there a way to query Oracle and learn of the fact that tracing is set for some or all of existing sessions? Branimir ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------