Long- term and Cross- database Performance Analysis for DBAs

Transcription

1

2 AWR Warehouse Long- term and Cross- database Performance Analysis for DBAs Jagan R. Athreya Senior Director, Product Management Oracle Enterprise Manager 15 January 2015 Copyright 2014, Oracle and/or its affiliates. All rights reserved.

3 Safe Harbor Statement The following is intended to outline our general product direcoon. It is intended for informaoon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or funcoonality, and should not be relied upon in making purchasing decisions. The development, release, and Oming of any features or funcoonality described for Oracle s products remains at the sole discreoon of Oracle.

4 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

5 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

6 EvoluOon of Performance Tuning Methodology Pre- 10g Releases V6: BSTAT & ESTAT & SQL Trace V7.3: Wait events instrumentaoon V : STATSPACK Oracle 10g+: Enhanced Time- Wait Model Database Time (DB Time) Based Methodology New always- on performance warehouse: AutomaOc Workload Repository

7 AutomaOc Workload Repository (AWR) IO / CPU Issues Boost Administrator ProducOvity Automatic Workload Repository Snapshots AutomaOc collecoon of db performance staosocs by MMON background process AWR snapshots: Data collected by MMON slaves every hour on the hour from memory Configurable collecoon frequency Manual snapshot creaoon Self-Diagnostic Engine AWR baselines: named snapshots to capture representaove workload (not affected by retenoon period) High Load SQL RAC Issues Performance & Management Advisors Eliminate Performance Boolenecks Lower IT Management Costs Deliver Higher Quality of Service Persisted under WRH$ and WRI$ tables in the SYSAUX tablespace By default, enabled, collected hourly and retained for 8 days* Contents accessible via DBA_HIST_* views Volume of data controlled by STATISTICS_LEVEL * 7 days for 10g databases

8 AWR Data AWR StaOsOcs Counter staosocs e.g. session logical reads Value staosocs, e.g. logons current Time StaOsOcs, e.g. DB Ome Metrics, e.g. DB Block Gets Per Txn Sampled, e.g. AcOve Session History OperaOng System (OS) staosocs CPU usage (including CPU count) Memory usage (including paging) Viewable via V$OSSTAT and DBA_HIST_OSSTAT Wait Classes & Events Events: Sessions waiong for external events: resources (latches), services (IO), user (idle) Classes: Logical grouping of events (CPU, concurrency, applicaoon, commit) AcOve Session History (ASH) samples of current state of every acove (in database call) session every second AWR snapshots capture sample of ASH data from last hour Top SQL By various criteria: Elapsed Time, CPU Time, Parse Calls, Shared Memory, and Version Count AddiOonal related meta data: SQL Text, SQL StaOsOcs, SQL Plans, Bind Types, Bind Values, OpOmizer Environment

9 Performance DiagnosOcs AWR- based performance advisors AutomaOc Database DiagnosOcs Monitor (ADDM): DB Time based advisor to pinpoint root cause of performance boolenecks Auto SQL Tuning & SQL Tuning Advisor: high load SQL idenoficaoon and automaoc tuning AWR- based out- of- the- box reports AWR report: all staosocs over a snapshot range Compare Period AWR: Comparison of two snapshot periods to compare difference in performance using DB Ome as basis ASH report: Detailed analysis of ASH data along session, SQL, Ome dimensions. Manual analysis of various dimensions of performance System à V$SYSTAT Session à V$SESSTAT Service à Designated in TNS connecoon SQL Statement à V$SQLSTATS Segment à V$SEGSTAT Module- AcOon à Instrumented in applicaoon Client ID à True end user provided by mid- Oer

10 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

11 AWR Report GeneraOng AWR Report from Inputs: DBID, Instance ID Type: html, text, acove- html* Enter n days for recent snapshots, default all snapshots Enter snap id for begin, end Omes Spool file_name.html *: default selecoon

12 AWR Report ConfiguraOon Health

13 AWR SecOons - StaOsOcs StaOsOcs

14 Performance Hub Report New interacove report for analyzing AWR data Single view of DB performance ADDM, SQL Tuning, Real- Time SQL Monitoring, ASH AnalyOcs Switch between ASH analyocs, workload view, ADDM findings and SQL monitoring seamlessly Supports both real- Ome & historical mode Historical view of SQL Monitoring reports

15 Performance Hub Report Performance Hub report generated from OR calling dbms_perf.report_perwub(.) funcoon Inputs: Level: basic/typical*/all select DBID, Instance ID : ID, ALL* Enter Start and End Omes for analysis (last 5 min* default) Spool file_name.html

16 Exadata Details

17 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

18 AWR Warehouse - Business Drivers Default retenoon period of 8 days prevents diagnosis of long term performance problems ( Compare performance during this quarter s books close with last quarter s ) 120% 90% 60% 30% 0% Finance 120% 90% 60% 30% 0% CRM 120% 90% 60% 30% 0% Supply Chain MulOple and separate AWRs don t make it easy to analyze cross- databases performance ( did query from db A cause i/o booleneck affecong db B?) Increasing AWR retenoon period increases overhead in criocal environments ( will analysis of AWR data consume producoon resources?)

19 AWR Warehouse Features Administrators use historical AWR reports in several database diagnosfc features Source Database 1 Source Database 1 Source Database 3 Performance Home ASH AnalyOcs AWR Report Load AWR Snapshots into Repository Compare Period ADDM Compare Period Report Central AWR Repository Database 1 Snapshots Database 2 Snapshots Database 3 Snapshots Database n Snapshots Central warehouse configured for long term AWR data retenoon Historical and ongoing AWR snapshots collected from databases enabled for AWR warehouse ETL jobs moves snapshots from source databases into AWR warehouse RetenOon period configurable for weeks, months, years or forever (default)

20 Configuring AWR Warehouse Available with EM12c: onwards Supported DB versions: & (+patch) DB CredenOals: SYS Storage: SYSAUX tablespace Default retenoon period: Forever (can be set to weeks, months or years) Track overall space uolizaoon Oracle ConfidenOal 20

21 AWR Warehouse Schema Objects CAW_SRC_DB_INSTANCES: Instance informaoon about source databases. CAW_PRIV_GRANTS : View privileges within the EM Console CAW_PROPERTIES : InformaOon about locaoon of dump files, interval, retenoon Ome, etc. for AWR Warehouse. CAW_SRC_DBS : Main info about source db s, version, ETL status, etc. CAW_SPACE_USAGE: Populates resource consumpoon dashboard for AWR. CAW_LOAD_WORKERS : Only used during an actual ETL load process to the AWR Warehouse. CAW_LOAD_METADATA : AWR dump file local, last load, etc. CAW_LOAD_ERRORS : Populates the errors view in the console. CAW_DBID_MAPPING : Used to map all data between Enterprise Manager, AWR Warehouse and Database IdenOfiers. Oracle ConfidenOal 21

22 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

23 Configuring AWR collecoon into AWR Warehouse Pre- configure database (DBA privileges) and host (save snapshots) credenoals for source databases Add source database via AcFons menu (v10.2 & above supported) Define snapshot collect interval (24 hr default) Upload snapshots via immediate run of ETL job on any source target in AWR Warehouse. Disable or Enable in the event of problems Oracle ConfidenOal 23

24 AWR Snapshot ETL DBMS Job on Source Database to directory Enterprise Manager Job in EM Job Service that pulls file from Source Target and then pushes to AWR Warehouse Target Directory AWR snapshot export AWR Warehouse AWR snapshot export Source Target AWR snapshot export Final DBMS Job Inserts data into AWR Warehouse. Oracle ConfidenOal Internal/Restricted/Highly Restricted 24

25 Extract and Transfer Extract by Source Database DBMS Scheduler Job Name: MGMT_CAW_EXTRACT Frequency 3 hour Interval (for inioal setup) 24 hour interval (ongoing) Stop extracts if problems encountered, e.g. file system full Transfer by EM Agent Runs 12hr intervals from Ome source target is added to AWR Warehouse Agent to Agent Direct Push Cleans up azer successful transfer Re- aoempts transfers 3 Omes upon failures and then stops Oracle ConfidenOal 25

26 Agenda AWR Overview New AWR Features Introducing AWR Warehouse Deployment AWR Warehouse Use Cases

27 Performance DiagnosOcs with AWR Warehouse All AWR features available on long term AWR data Performance page AWR report ASH analyocs Compare Period ADDM Compare Period Report Integrated seamlessly into EM UI

28 Demo AWR Warehouse

29 Long Term ComparaOve Analysis of workload June 10, June 10, l_reads_s read_iops_max read_iops_direct read_iops_direct_max How has my I/O workload changed year to year? Changes to overall load Changes to the character of the load (reads vs. writes) l_reads_s read_iops_max read_iops_direct read_iops_direct_max Oracle ConfidenOal Internal/Restricted/Highly Restricted 29

30 Performance Analysis of DBs on Shared Infrastructure Which resource usage shows greatest variaoons across DBs? Which databases on my shared host generates the highest CPU load? Should these databases moved into dedicated servers? Oracle ConfidenOal 30

31 How Current AWR Queries Change in the AWR Warehouse from dba_hist_sys_ome_model stm, dba_hist_snapshot s, gv$parameter p, dbsnmp.caw_dbid_mapping m where stm.stat_name in ('DB CPU','background cpu Ome') and LOWER(m.target_name)= '&dbname' and s.dbid= m.new_dbid and s.dbid = stm.dbid and s.snap_id = stm.snap_id and s.instance_number = stm.instance_number and p.name = 'cpu_count' and p.inst_id = s.instance_number) Oracle ConfidenOal 31

32 AWR Warehouse Resources Support Master Note on AWR Warehouse Doc ID: Oracle Database 12c DocumentaOon: 2 + Performance Tuning Guide Chapter 10 Oracle Learning Library video: Analyze Long- term Performance Across Enterprise Databases Using AWR Warehouse ArOcles: OTN: hop:// awr- em12c html Database Trends & ApplicaOons: hop:// Warehouse- the- Basics- and- Beyond aspx

33 Safe Harbor Statement The preceding is intended to outline our general product direcoon. It is intended for informaoon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or funcoonality, and should not be relied upon in making purchasing decisions. The development, release, and Oming of any features or funcoonality described for Oracle s products remains at the sole discreoon of Oracle.

34

35