Database Reference
In-Depth Information
EVENTS
The
EVENTS
dump is not a true diagnostic dump. It merely writes the enabled events to a trace
file. If you are uncertain which events are active in a session, process, or instance, this is the
correct way to find out. Here is an example:
SQL> ALTER SESSION SET EVENTS '10046 trace name context forever, level 8';
Session altered.
SQL> ALTER SESSION SET EVENTS '4031 trace name heapdump level 3';
Session altered.
SQL> ORADEBUG SETMYPID
Statement processed.
SQL> ORADEBUG DUMP EVENTS 1
Statement processed.
SQL> ORADEBUG TRACEFILE_NAME
/opt/oracle/obase/admin/TEN/udump/ten1_ora_20206.trc
Sample trace file contents generated by
ORADEBUG
DUMP
EVENTS
are shown here:
Dump event group for level SESSION
TC Addr Evt#(b10) Action TR Addr Arm Life
B72DB4F4 4031 1 b72db560 0 0
TR Name TR level TR address TR arm TR life TR type
HEAPDUMP 3 0 1 2 -1221853072
B72DB3F8 10046 1 b72db464 0 0
TR Name TR level TR address TR arm TR life TR type
CONTEXT 8 0 -1 2 -1221853072
The levels supported by the
EVENTS
dump are listed in Table 37-2 along with the method
for setting an event at the respective level. Note that the scope of events set with
ORADEBUG
EVENT
is the process, which was previously attached with
ORADEBUG
SETORAPID
or a similar command.
Table 37-2.
ORADEBUG DUMP EVENTS Levels and Scope
Level
Event Scope
Command Used
ALTER
SESSION
,
DBMS_SYSTEM.SET_EV
1
Session
ORADEBUG
EVENT
2
Process
ALTER
SYSTEM
4
Instance
ERRORSTACK
As stated earlier, a program call stack may be obtained with the
ERRORSTACK
diagnostic dump.
Depending on the dump level, an
ERRORSTACK
dump contains more information than merely a
call stack. Table 37-3 gives an overview of the trace file sections for dump levels 1, 2, and 3. The
information applies to Oracle10
g
. Trace file contents vary from release to release.
