Database Reference
In-Depth Information
Outline Data:
/*+
BEGIN_OUTLINE_DATA
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.3')
DB_VERSION('11.2.0.3')
ALL_ROWS
OUTLINE_LEAF(@"SEL$1")
FULL(@"SEL$1" "T"@"SEL$1")
END_OUTLINE_DATA
*/
Optimizer state dump:
Compilation Environment Dump
optimizer_mode_hinted = false
optimizer_features_hinted = 0.0.0
...
_px_numa_support_enabled = true
total_processor_group_count = 1
Bug Fix Control Environment
fix 3834770 = 1
fix 3746511 = enabled
...
End of Optimizer State Dump
The lists of initialization parameters and bug fixes are especially long. For this reason, depending on the release
you're using, about 10-30KB of data is written to the trace file even for the simplest SQL statement. The generation of
such a trace file might be a significant overhead. You should therefore only activate the event 10132 if you really need it.
The event 10132 can be enabled and disabled in the following ways:
•
Enable and disable the event for the current session.
ALTER SESSION SET events '10132 trace name context forever'
ALTER SESSION SET events '10132 trace name context off'
•
Enable and disable the event for the whole database. Warning: this setting doesn't take effect
immediately, but only for sessions created after the modification.
ALTER SYSTEM SET events '10132 trace name context forever'
ALTER SYSTEM SET events '10132 trace name context off'
Each server process writes all data about the SQL statements it parses in its own trace file. This means not only
that a trace file can contain information about several SQL statements but also that several trace files will be used
whenever the event is enabled in several sessions. For information about the name and location of trace files, refer to
the “Finding Trace Files” section in Chapter 3.
