https://www.oraclescripts.com/tags/dbms_monitor/Recent content in DBMS_MONITOR on Oracle ScriptsHugo -- gohugo.ioenOracleScripts.comFri, 10 Jul 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-enable-10046-trace/Fri, 10 Jul 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-enable-10046-trace/ <h2 id="enable-a-10046-trace-for-an-oracle-session">Enable a 10046 Trace for an Oracle Session</h2> <h2 id="purpose">Purpose</h2> <p>A 10046 trace returns wait events only if the level includes them. Enabling the trace at level 1 and then wondering why the file shows no waits is the most common 10046 mistake in production diagnosis — the output has elapsed times and call counts, but none of the <code>db file sequential read</code>, <code>latch: cache buffers chains</code>, or <code>enq: TX - row lock contention</code> events that explain where those seconds actually went. Choosing the wrong level produces a trace file that answers a different question than the one being investigated.</p>