Comments on: Tracing Enabled for Sessions After Instance Restart

By: Charles Hooper

Charles Hooper — Thu, 15 Sep 2011 19:49:33 +0000

I think that I might have found something interesting that is related to this blog article: Doc ID 556756.1, "SQL TRACE GENERATING TO TRACE FILES NEVER STOPS" Just out of curiosity, has anyone noticed that if a 10046 trace is enabled system-wide (ALTER SYSTEM or DBMS_MONITOR.DATABASE_TRACE_ENABLE) that the trace cannot be disabled for certain sessions (likely background processes)? I thought that I encountered this problem the last time I tested system-wide 10046 traces, and I thought that I recalled reading that this was a problem that could only be resolved by bouncing the database.

By: Charles Hooper

Charles Hooper — Tue, 09 Mar 2010 00:57:46 +0000

Coskan,

That is a great idea. Initially, when I read your comment I thought that reviewing DBA_SOURCE would be a very time consuming task – in part because of the number of different ways that a 10046 trace could be enabled. However, the portion of the trace file posted by the OP provided text that could be used to search the DBA_SOURCE view: “alter session set events ’10046 trace name context forever, level 12′” – so searching DBA_SOURCE probably would not have been too difficult.

By: coskan

coskan — Mon, 08 Mar 2010 19:59:14 +0000

I think instead of checking triggers checking dba_source for possible 10046 or sql_trace statement might be on spot in case if it is not trigger like this.

By: Charles Hooper

Charles Hooper — Sat, 13 Feb 2010 04:06:05 +0000

Timur,

That does sound like it would be hard to troubleshoot. Bouncing the database in your case probably would have magically fixed your problem, but that might not have been a possibility for you.

Thanks for the reminder. It appears that you could also end up in the same situation by executing an ALTER SYSTEM call to enable a 10046 trace.

By: Timur Akhmadeev

Timur Akhmadeev — Fri, 12 Feb 2010 09:50:14 +0000

Oh, that one was simple Just yesterday I have the same issue on my test 11.2.0.1 database – 10046 was on and I couldn’t disable it. I’ve tried:
1) 10046 off
2) dbms_session.session_trace_disable
3) oradebug 10046 trace name context off
and nothing helped. I thought maybe SQL_TRACE is not only deprecated, but has a bug which prevents it from turning off. It turned out dbms_monitor.database_trace_enable can’t be overridden on the session level, which is strange.