Tools and Utilities - Expert Oracle RAC Performance Diagnostics and Tuning - page 175

The output generated from this procedure is similar to the one generated by the explain plan but with some
additional information.

REPORT_SQL_MONITOR
-------------------------------------------------------------------------------
Session : RAPTEST (642:3)
SQL ID : cavwma8xnrv97
SQL Execution ID : 16777216
Execution Started : 04/25/2010 11:08:54
First Refresh Time : 04/25/2010 11:09:04
Last Refresh Time : 04/25/2010 11:10:33
Duration : 99s
Module/Action : SQL*Plus/-
Service : raptest
Program : sqlplus@prddb1 (TNS V1-V3)
Fetch Calls : 21

REPORT_SQL_MONITOR
-------------------------------------------------------------------------------

Global Stats
===========================================================================
| Elapsed | Cpu | IO | Cluster | Fetch | Buffer | Read | Read |
| Time(s) | Time(s) | Waits(s) | Waits(s) | Calls | Gets | Reqs | Bytes |
===========================================================================
| 101 | 61 | 37 | 3.29 | 21 | 456K | 3824 | 3GB |
===========================================================================

SQL Plan Monitoring Details (Plan Hash Value=99144695)
===============================================================================

REPORT_SQL_MONITOR

■ Note output is not shown due to its size.

DBMS_SQLTUNE.REPORT_SQL_MONITOR in a graphical view
Using the same procedure available under DBMS_SQLTUNE , the above plan can be displayed in a graphical form
(see Figure 6-22 ) using

•

SELECT DBMS_SQLTUNE.REPORT_SQL_MONITOR(session_id=>sys_context('userenv','sid'),
report_level=>'ALL') AS report
FROM DUAL;