ORADEBUG SQL Plus Command - Secrets of the Oracle Database - page 488

Chain 3 : <cnode/sid/sess_srno/ospid/wait_event> :
<0/150/38/440/Streams AQ: qmn slave idle wait>
Chain 4 : <cnode/sid/sess_srno/ospid/wait_event> :
<0/152/1/5440/Streams AQ: waiting for time man>
Chain 5 : <cnode/sid/sess_srno/ospid/wait_event> :
<0/154/1/4584/Streams AQ: qmn coordinator idle>
Extra information that will be dumped at higher levels:
[level 4] : 1 node dumps -- [REMOTE_WT] [LEAF] [LEAF_NW]
[level 5] : 4 node dumps -- [SINGLE_NODE] [SINGLE_NODE_NW] [IGN_DMP]
[level 6] : 1 node dumps -- [NLEAF]
[level 10] : 11 node dumps -- [IGN]
MODIFIED_PARAMETERS
This dump records any initialization parameters that were modified with ALTER SESSION or
ALTER SYSTEM in a trace file. Level 1 is sufficient. Higher levels do not produce more detailed
output. In the following example, the initialization parameters PGA_AGGREGATE_TARGET and
SKIP_UNUSABLE_INDEXES are modified. Thus, these parameters and their new values appear in
the MODIFIED_PARAMETERS dump.
SQL> ALTER SYSTEM SET pga_aggregate_target=512m;
System altered.
SQL> ALTER SESSION SET skip_unusable_indexes=true;
System altered.
SQL> ORADEBUG DUMP MODIFIED_PARAMETERS 1
Statement processed.
The trace file contains an entry for each modified parameter.
Received ORADEBUG command 'DUMP MODIFIED_PARAMETERS 1' from process Windows thread
id: 3580, image:
DYNAMICALLY MODIFIED PARAMETERS:
pga_aggregate_target = 536870912
skip_unusable_indexes = TRUE
PROCSTAT and Process-Level Operating System Statistics
Process-level operating system statistics may be dumped to a trace file with the command
ORADEBUG PROCSTAT . CPU usage is reported at a more granular level than by the statistic “CPU
used by this session” in V$SESSTAT . Here is an example:
SQL> ORADEBUG PROCSTAT
SQL> ORADEBUG TRACEFILE_NAME
/opt/oracle/obase/admin/TEN/udump/ten1_ora_8739.trc
SQL> !cat /opt/oracle/obase/admin/TEN/udump/ten1_ora_8739.trc
----- Dump of Process Statistics -----
User time used = 500
System time used = 1750
…