Database = 11.2.0.3.0
The default value for the database parameter trace_enabled is TRUE. My question is whether this setting has any impact on the level of detail of a sql trace of an individual session. Even with trace_enabled set to FALSE, you can still run a sql trace. That's not the issue. The question is whether I will get less information in my trace file with this set to false. The documentation makes it sound like this parameter is useful for diagnosing database errors or crashes. But at the same time, it sounds like with trace_enabled set to true, the database is keeping valuable information in memory that *might* show up in a trace file. Does anyone have any experience with this setting with respect to sql trace?
The following is copied from the documentation for TRACE_ENABLED
TRACE_ENABLED controls tracing of the execution history, or code path, of Oracle. Oracle Support Services uses this information for debugging.
When TRACE_ENABLED is set to true, Oracle records information in specific files when errors occur.
Oracle records this information for all instances, even if only one instance terminates. This allows Oracle to retain diagnostics for an entire cluster.
Although the overhead incurred from this processing is not excessive, you can improve performance by setting TRACE_ENABLED to false. You might do this, for example, to meet high-end benchmark requirements. However, if you leave this parameter set to false, you may lose valuable diagnostic information. Therefore, always set TRACE_ENABLED to true to trace system problems and to reduce diagnostic efforts in the event of unexplained instance failures.