Oracle-DB: Evaluation of recorded SQL-Monitor reports with Panorama

SQL-Monitoring records individual executions of an SQL statement in detail if they fulfill one of the following prerequisites:
  • Execution with parallel query
  • CPU- or I/O-activity for more than 5 seconds
  • Optimizer-hint `MONITOR` in SQL statement
SQL-Monitoring reports are stored in table v$SQL_Monitor during SQL execution and for a very short period after execution.

The precondition for using the monitoring reports is licensing of the Tuning Pack for the Enterprise Edition.

Starting with Oracle 12.1, the short-living detailed monitoring reports from v$SQL_Monitor are also available for a longer time within the AWR retention period via DBA_Hist_Reports and DBA_Hist_Reports_Details.

This report can be exported as HTML-page which uses Adobe-Flash to render the Database Activity Report for this SQL execution similar to Enterprise manager.

To generate the HTML-report from v$SQL_Monitor call:

SELECT DBMS_SQLTUNE.report_sql_monitor(
                                      sql_id          => :SQL_ID,
                                      Session_ID      => :SID,
                                      Session_Serial  => :SerialNo,
                                      SQL_Exec_ID     => :SQL_Exec_ID,
                                      Inst_ID         => :Instance,
                                      type            => 'ACTIVE',
                                      report_level    => 'ALL'
                                  )
FROM Dual;

To generate the HTML-report from DBA_Hist_Reports call:
 
SELECT DBMS_AUTO_REPORT.REPORT_REPOSITORY_DETAIL(RID => :Report_ID, TYPE => 'ACTIVE') FROM Dual;








The performance analysis tool Panorama lists SQL monitor reports existing for the respective object (SQL / DB session) and period via the button "SQL Monitor" from:
  • SQL detail view from current SGA
  • SQL detail view from historic AWR data
  • current DB-session detail view








Clicking on the report ID opens the Database Activity Report for this SQL execution in a new browser tab. If an internet connection is available for the browser, it will be displayed as an active Flash page, otherwise as a static HTML page.

p.s.:
If the DB Activity Report is not completely shown in the new browser tab, please check browser console if there are security restriction settings active.
Especially Google Chrome often does not accept Oracle's Flash source URLs.
Location: Dresden, Deutschland

Comments

Post a Comment

Popular posts from this blog

Common pitfalls using SQL*Net via Firewalls

It's very common that firewalls are terminating idle TCP sessions after a limited time, often after approximately one hour. Possible problem If you have a long running SQL or PL/SQL program and the firewall terminates your apparently idle TCP session this may lead to the following scenario: the database is not able to send result to client. After reaching the TCP-timeout the database server terminates the DB-Session the client program stays in socket read forever waiting for the database response Oracle's full solution: SQLNET.EXPIRE_TIME=x in sqlnet.ora Oracle's solution for this problem is setting parameter SQLNET.EXPIRE_TIME=x in sqlnet.ora where x are the minutes between keep alive packets on idle sessions that inform the firewall that this session is always alive. SQLNET.EXPIRE_TIME hast to be set in the sqlnet.ora of your RDBMS' ORACLE_HOME. Normally $ORACLE_HOME/network/admin. If you have a grid infrastructure setting SQLNET.EXPIRE_TIME in sqlnet
Read more

Oracle-DB: How to check for appropriate sequence caching

Image
A common pitfall while using sequences in Oracle-DB is forgetting to define sequence caching. The default for sequences is cache size = 0. That means, every sequence.nextval operation triggers a single write operation on dictionary table sys.SEQ$. Especially if frequently calling sequence.nextval uncached sequences may cause significant performance degradation. Frequently calling sequence.nextval in parallel sessions may lead to ramdom lock scenarios in library cache. Setting a cache size for a sequence may heavy increase performance of nextval-operations. There's a minimal memory overhead for caching a sequence because all that's needed is a counter to increase in SGA memory and a upper limit. If this limit is reached with the counter, the upper limit is increased by cache size and the new upper limit is written down once to SEQ$. The possible drawback for sequence caching is that you loose all your values between the current value and the highest cached value if yo
Read more

Oracle-DB: Link between audit trail and active session history

Unfortunately the audit trail of the Oracle-DB uses a different session identifier (AudSid) than the Active Session History (SID + Serial#). Both identifiers are available in v$Session (AudSid, SID, Serial#). So during lifetime of a session it is possible to link between the session info from v$Session an audit trail. But neither the AudSID is stored in ASH (v$Active_Session_History) nor the SID + Serial# is stored in audit trail. This prevents from combining session info of both sources after the session is closed. There is a possible way to link audit trail with ASH by establishing a logon trigger for that. The LOGOFF records in audit trail (if AUDIT SESSION is active) record also the Client_Identifier from v$Session. So supplying v$Session.Client_Identifier with the needed info allows to retrieve it from DBA_Audit_Trail.Client_ID.  This logon trigger does it: CREATE OR REPLACE TRIGGER Client_ID AFTER LOGON ON DATABASE -- Put unique session identifier into client-id to have it a
Read more