Database Reference
In-Depth Information
Figure 6-23. OEM - Top Consumers chart
The benefit provided for monitoring activity at the service level does not stop here. Tracing user operations is also
available at the module and action level. Oracle generates one trace file per session connecting to the database using
the SERVICE_NAME . Users connecting to the database may get attached to any one of the available instances supporting
the service. The advantage of tracing at this level is when multiple trace files are generated from the current instance
or across instances in the cluster. Data related to a specific action type can be grouped together. For example, the
following procedure will enable tracing of a service at the module and action level:
DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE (<SERVICE_NAME>,<MODULE NAME>,<ACTION TYPE>);
SQL> EXEC DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE ('TAPS','Process Orders','UPDATE');
Apart from the basic SQL level trace information, additional information such as wait events encountered
(collected by default), bind variables, and values used, etc. can also be collected. For example,
EXEC DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE (
SERVICE_NAME => 'TAPS',
MODULE_NAME => 'Process Orders',
ACTION_NAME => DBMS_MONITOR.ALL_ACTIONS,
WAITS => TRUE,
BINDS => TRUE);
the SERV_MOD_ACT_TRACE_ENABLE utility generates trace files similar to the trace files generated using
event 10406 at level 1. enabling wait events and binds will be similar to generating tracing using 10406 at level 12.
Note
 
 
Search WWH ::




Custom Search