Effec%ve Use of Oracle s 12c Database Opera%on Monitor

Transcription

1 Managed Services Cloud Services Consul3ng Services Licensing Effec%ve Use of Oracle s 12c Database Opera%on Monitor UTOUG Training Days 2016 Kasey Parker Enterprise Architect Kasey.Parker@centroid.com

2 Centroid Overview Leader in Technology, Consulting and Managed Services since 1997 Part of Oracle s Top 25 Strategic Partner Program Focused on Consulting, Managed Services, Cloud Services and Resell Capabilities From Oracle Applications to Technology to Infrastructure Oracle Engineered Systems & Tech Partner of the Year Winner: 2014 & 2015 Top 25 Strategic Partner Specializations Oracle Database & Core Technologies Oracle Engineered Systems Oracle Server & Storage Solutions Oracle Performance Tuning Oracle Data Warehousing Oracle Business Intelligence Oracle Applications

3 About Kasey Parker QUICK FACTS Reside in Plano, TX with wife and 5 kids recently moved from Utah Oracle Architect / DBA Over 15 Years of Oracle Experience Oracle CerGfied Exadata Specialist Oracle CerGfied Professional - DBA Performance Tuning specialist Data Warehousing specialist Last 5 years focused on Oracle Engineered Systems Many industries Financial Services, Manufacturing, Health/NutriGon, City/County Government, Retail Serve on Board of the Utah Oracle Users Group (UTOUG) Academic Brigham Young University Alumnus Management InformaGon Systems

4 Agenda What is the Real-Time DB Opera3ons Monitor? What is rela3onship between DBOM and RSM? How do I enable it? How do I access it? What can I get from it and how do I interpret? Q&A

5 How s Your SQL Tuning Going? How do I see trace information while my statement is running? How do I interpret execution plans that are 100+ lines long? I want a simpler way to trace my SQL I want a tracing tool I can use without going to a DBA What s a good way to trace parallel processes? Is there an easy way to see if I got a Smart Scan? How can I best trace a full user experience and not just a statement?

6 Real-%me Database Opera%on Monitor Database Opera3on One or more database tasks, defined by you Contains one or more SQL or PL/SQL statements In one or more sessions Database Opera3on Monitor (DBOM) Named Real-3me SQL Monitor (RSM) prior to 12c Extension of Real-3me SQL Monitor Monitor single SQL or PL/SQL opera3ons (pre 12c) Monitor composite database opera3ons (12c)

7 DB Opera%on Monitor Architecture DBMS_SQL_MONITOR BEGIN_OPERATION [SQL Statement(s) ] [PL/SQL Block(s)...] END_OPERATION Developers DBAs DBMS_SQL_MONITOR. REPORT_SQL_MONITOR Database Opera%ons AWR User-Defined Opera%ons Real-Time SQL Monitor V$SQL_MONITOR V$SQL_PLAN_MONITOR V$SQL_MONITOR_SESSTAT

8 DBOM / RSM Overview Part of Diagnos3cs & Tuning Packs CONTROL_MANAGEMENT_PACK_ACCESS = DIAGNOSTICS+TUNING Feature includes views, hints, func3ons and reports Most value in Ac3ve XML SQL Monitor Report New 12c Features Composite DB Opera3ons In-Memory and Adap3ve Execu3on Plan Monitoring Historical Reports Stored in AWR Run-away Query Logging My opinion: Best SQL diagnos3c tool created by Oracle

9 DBOM / RSM Basics Detailed monitoring of SQL Statements while execu3ng No Performance Penalty Informa3on efficiently captured by background processes Similar to AWR and ASH Statements Monitored by Default if: Consuming >5 seconds of DB 3me Executed in parallel Use /*+ MONITOR */ hint to force

10 DBOM Composite Opera%ons Iden3fy and Execute a Database Opera3on by: Iden3fy the database opera3on Opera3on Name Execu3on ID Start and end the database opera3on DBMS_SQL_MONITOR.BEGIN_OPERATION DBMS_SQL_MONITOR.END_OPERATION SQL> VAR dbop_eid NUMBER; SQL> EXEC :dbop_eid := DBMS_SQL_MONITOR.BEGIN_OPERATION ('ORA.ETLLOAD.FINANCE', FORCED_TRACKING => 'Y') SQL> INSERT /*+ APPEND */ * INTO tab1 SELECT...; SQL> INSERT /*+ APPEND */ * INTO tab2 SELECT...; SQL> EXEC DBMS_SQL_MONITOR.END_OPERATION ('ORA.ETLLOAD.FINANCE, :dbop_eid)

11 DBOM Composite Opera%ons Cont. Iden3fy Using Tagging for Java and OCI Applica3ons OCI Calls OCIAjrSet OCIAppCtxSet Java setclientinfo OS Environment Variable ORA_DBOP End Opera3on by sekng Tag to NULL

12 DBOM Composite Opera%on Example Single Session Opera%on

13 DBOM Composite Opera%on Example Mul%ple Session Opera%on

14 Accessing SQL Monitor (DBOM) Informa3on Accessible from: Associated V$ views V$SQL_MONITOR, V$SQL_PLAN_MONITOR and V$SQL_MONITOR_SESSTAT Join with other views: V$SQL, V$ACTIVE_SESSION_HISTORY and V$SESSION_LONGOPS Bejer way: SQL Monitor Reports DBMS_SQL_MONITOR.REPORT_SQL_MONITOR Text, HTML, Ac3ve XML Best way: Ac%ve XML SQL Monitor Report Available from OEM, SQL Developer, DBMS_SQL_MONITOR

15 Accessing SQL Monitor (DBOM) Using Enterprise Manager 12c From Performance Menu Using EM Database Express From Performance Hub

16 Accessing SQL Monitor (DBOM) SQL Monitoring Link Opens Monitored SQL Execu3ons

17 Accessing SQL Monitor (DBOM) Clicking an execu3on opens the Ac3ve SQL Monitor

18 Accessing SQL Monitor (DBOM) Using DBMS_SQL_MONITOR package Generate using DBMS_SQL_MONITOR.REPORT_SQL_MONITOR func3on Use DBMS_SQLTUNE prior to 12c Requires many DBA type permissions including: ADMINISTER SQL MANAGEMENT OBJECT ADMINISTER ANY SQL TUNING SET ADVISOR Select rights on many performance views: V$SQL*, V$ACTIVE_SESSION_HISTORY, V$SESSION_LONGOPS and many DBA_HIST* views

19 Accessing SQL Monitor (DBOM) Example: SET LONG SET LONGCHUNKSIZE SET LINESIZE 1000 SET PAGESIZE 0 SET TRIM ON SET TRIMSPOOL ON SET ECHO OFF SET FEEDBACK OFF SET HEADING OFF SET SHOW OFF SET VERIFY OFF SPOOL my_sql_monitor_acqve_report.html SELECT DBMS_SQL_MONITOR.report_sql_monitor( sql_id => '1kf86hqsyvddb, type => 'ACTIVE', report_level => 'ALL') AS report FROM dual; SPOOL OFF

20 Access by Developers Concerned about level of privileges? Use a wrapper func3on Around DBMS_SQL_MONITOR.REPORT_SQL_MONITOR Owned by a privileged user Grant execute on wrapper func3on to developers CREATE OR REPLACE FUNCTION EXEC_REPORT_SQL_MONITOR( p_sql_id in varchar2 ) RETURN clob IS v_report_clob clob; BEGIN v_report_clob := dbms_sql_monitor.report_sql_monitor(sql_id => p_sql_id); RETURN v_report_clob; END;

21 Access by Developers Developers then generate the report using a script: set long set longchunksize column spoolfilename new_value splfile accept sql_id prompt 'Enter value for sql_id: select 'sqlmon_' '&&sql_id' '.html' as spoolfilename from dual ; spool &splfile SELECT EXEC_REPORT_SQL_MONITOR( p_sql_id => '&&sql_id', p_type => 'ACTIVE') AS monitor_report FROM dual; spool off undef sql_id undef spoolfilename undef splfile

22 Access by Developers How to find the SQL ID? Use V$SQL set lines 200 pages 60 set feedback off echo off set verify off set pagesize 999 variable sql_id varchar2(30) variable sql_text varchar2(80) set feedback on select /* NORESULT */ sql_id from gv$sql s where sql_text like '%&sql_txt%' and sql_text not like '%NORESULT%' and sql_text not like 'BEGIN :sql_% order by 1 desc / undef sql_id undef sql_text

23 What s in a SQL Monitor Report Execu3on Plan Plan Sta3s3cs Es3mated vs. Actual Row Counts Bind Variable Values DB Time and Wait Sta3s3cs Execu3on s Dura3on vs. DB Time CPU and Wait Events, and 3me spent, for each execu3on step CPU, IO, Memory and Wait Ac3vity: mapped over statement run 3me IO Sta3s3cs Memory Sta3s3cs Temp Ac3vity Sta3s3cs Parallel Ac3vity Detail Exadata Cell Offload (Smart Scan) Efficiency

24 SQL Monitor Report New in 12c Other, Context-Sensi3ve Plan Line Sta3s3cs Hash Join Row Source

25 SQL Monitor Report New in 12c Other, Context-Sensi3ve Plan Line Sta3s3cs Why was a DOP downgraded? Downgrade Reasons: 350 = due to adap3ve DOP 351 = due to resource manager max DOP 352 = due to insufficient number of processes 353 = because slaves failed to join

26 SQL Monitor Report New in 12c Other, Context-Sensi3ve Plan Line Sta3s3cs Exadata Smart Scan and Flash Cache Exadata Storage Index Use

27 SQL Monitor Report New in 12c Execu3on Plan Note Why was a given DOP Selected?

28 SQL Monitor Report New in 12c In-Memory Query Repor3ng Sta3s3cs Collector Repor3ng From Adap3ve Execu3on Plans

29 SQL Monitor Report New in 12c Composite Database Opera3ons Repor3ng

30 Historical SQL Monitor Reports SQL Monitor Reports Now Persisted in AWR DBA_HIST_REPORTS Stores Report Metadata DBA_HIST_REPORTS_DETAILS Stores Report in XML Format By Default, Only Reports for Longer-running SQL Captured Generate Reports from OEM or DBMS_AUTO_REPORT.REPORT_REPOSITORY_DETAIL

31 Runaway Query Logging DB Resource Manager can now log to SQL Monitor Based on certain thresholds: Es3mated Execu3on Time Elapsed Time (new in 12c) CPU 3me IO requests or IO Bytes Logical IOs (new in 12c) New columns in V$SQL_MONITOR RM_CONSUMER_GROUP RM_LAST_ACTION RM_LAST_ACTION_REASON RM_LAST_ACTION_TIME Can also switch consumer group, Abort Call or Kill Session

32 Interpre%ng SQL Monitor Report 1. Time & Wait Sta3s3cs Find Where SQL is Spending Time Dura3on vs Database Time CPU vs Wait Database Time Breakdown Total Ac3ve DB Processing Time Consumed by Execu3on If Parallel = QC + PX Slaves 2. Ac3vity % in Plan Sta3s3cs Detail If DB Time Mostly on CPU >> Focus on CPU Ac3vity % If DB Time Mostly on Waits >> Focus on Wait Ac3vity % Line(s) with the Most Ac3vity % is Where to Focus 3. Other Plan Sta3s3cs & Metrics Help with Diagnosis

33 Interpre%ng SQL Monitor Report Where Do You Focus?

34 Interpre%ng SQL Monitor Report Where Do You Focus? Are join keys indexed appropriately?

35 DEMO

36 DBOM / RSM Use Cases Long Execu3on Plans Reading, Diagnosing and Quickly Iden3fying Problem Areas Op3mal Use of Indexes Find Bind Variable Values Par3ally Parallelized SQL Verify Parallel DML/DDL Detect Skew Between Parallel Processes Iden3fy latency, network or applica3on, outside of database Find Cause of High Temp Usage Verify Exadata Smart Scans and Cell Offload Efficiency Iden3fy Long-running SQL in Batch or Mul3-statement Processes And many more!

37 SQL Monitor Use Case Long Execu3on Plans: Reading, Diagnosing and Quickly Iden3fying Problem Areas Watch out for Very Long Plans: Plans > 300 lines not monitored _sqlmon_max_planlines = 300 By default, but can be increased See MOS Note: How to Monitor SQL Statements with Large Plans Using Real-Time SQL Monitoring? (Doc ID )

38 SQL Monitor Use Case Find Bind Variable Values for Running SQL

39 SQL Monitor Use Case Verifying Enabling Parallel DML

40 SQL Monitor Use Case Par3ally Parallelized SQL

41 SQL Monitor Use Case Verifying Exadata Smart Scans and Cell Offload Efficiency

42 Summary DB Opera3on and SQL Monitor Oracle s Best Tool to Diagnose SQL Performance New 12c Features Expand Capability Monitor Composite Opera3ons Use Ac3ve SQL Monitor Report Access through OEM or DBMS_SQL_MONITOR Contains Detailed Info About SQL Execu3on Helps Iden3fy and Resolve Most SQL Performance Issues

43 Ques3ons?