Expert Oracle Exadata - Parent Directory

CHAPTER 12 MONITORING EXADATA PERFORMANCEGlobal Stats============================================================================| Elapsed | Queuing | Cpu | IO | Buffer | Read | Read | Cell || Time(s) | Time(s) | Time(s) | Waits(s) | Gets | Reqs | Bytes | Offload |============================================================================| 1095 | 0.00 | 17 | 1079 | 11M | 170K | 83GB | 96.60% |============================================================================SQL Plan Monitoring Details (Plan Hash Value=3536567600)============================================================================|Id | Operation | Name | Read | Cell | Activity || | | | Bytes | Offload | (%) |============================================================================| 0|SELECT STATEMENT | | | | || 1| SORT AGGREGATE | | | | || 2| PX COORDINATOR | | | | || 3| PX SEND QC (RANDOM) |:TQ10000| | | ||-> 4| SORT AGGREGATE | | | | 0.09 ||-> 5| PX BLOCK ITERATOR | | | | ||-> 6| TABLE ACCESS STORAGE FULL|T4 | 87GB | 96.60% | 99.91 || | | | | | |============================================================================DBMS_SQLTUNE.REPORT_SQL_MONITOR can also take HTML as a value for the TYPE parameter, instead of TEXT,in which case the output is generated as HTML. If you spool this output into an HTML file and open it inthe browser, you will see much nicer output than just text. And starting with Oracle 11.2, you can alsouse ACTIVE as a parameter and spool that output into an HTML file. Now if you open this file in thebrowser, you will see the SQL Monitoring page almost exactly as it looks in the Grid Control! And all thedata required for displaying that report is self-contained in the spooled HTML file —no database accessneeded when opening it! So this is very useful if you want to send a detailed self-contained report withsome SQL execution problem to someone over the email.Controlling SQL MonitoringSQL Monitoring kicks in immediately for all statements executed with parallel execution, no matter howlong they run. For serially executed statements, the SQL Monitoring does not kick in immediately, as it’snot designed to monitor typical fast OLTP queries, which are executed many times per second.Nevertheless, if a serial query has consumed more than 5 seconds of total CPU and/or I/O wait time, it’sconsidered as a long-running query and the SQL Monitoring is enabled for that statement execution.This happens seamlessly on-the-fly, and statement restart is not needed.You can also use MONITOR and NO_MONITOR hints to control the SQL monitoring for a statement.V$SQL_HINT shows all the hints available for use and the version when they were introduced. Forexample:SQL> SELECT name, inverse, version, class, sql_feature2 FROM v$sql_hint WHERE name LIKE '%MONITOR%';392