Presentation is loading. Please wait.

Presentation is loading. Please wait.

9 Copyright © 2006, Oracle. All rights reserved. Automatic Performance Management.

Similar presentations


Presentation on theme: "9 Copyright © 2006, Oracle. All rights reserved. Automatic Performance Management."— Presentation transcript:

1 9 Copyright © 2006, Oracle. All rights reserved. Automatic Performance Management

2 9-2 Copyright © 2006, Oracle. All rights reserved. Objectives After completing this lesson, you should be able to: Diagnose database performance issues Configure the Automatic Workload Repository Access the database advisors Use the SQL Access Advisor to improve database performance Use asynchronous COMMIT effectively Tuning Statistics SGA Attach AWR Advisors Async. Commit

3 9-3 Copyright © 2006, Oracle. All rights reserved. Tuning Activities The three activities in performance management are: Performance planning Instance tuning SQL tuning

4 9-4 Copyright © 2006, Oracle. All rights reserved. Performance Planning Investment options System architecture Scalability Application design principles Workload testing, modeling, and implementation Deploying new applications

5 9-5 Copyright © 2006, Oracle. All rights reserved. Performance Planning Full Notes Page

6 9-6 Copyright © 2006, Oracle. All rights reserved. Instance Tuning Have well-defined goals. Allocate memory to database structures. Consider I/O requirements in each part of the database. Tune the operating system for optimal performance of the database.

7 9-7 Copyright © 2006, Oracle. All rights reserved. Performance Tuning Methodology The tuning steps: Tune from the top down. Tune: –The design before tuning the application code –The code before tuning the instance Tune the area with the greatest potential benefit. –Identify the longest waits. –Identify the largest service times. Stop tuning when the goal is met.

8 9-8 Copyright © 2006, Oracle. All rights reserved. Statistics Collection Performance tuning depends on the collection of accurate statistics. There are different types of statistics: –Optimizer statistics –System statistics There are different methods of collecting statistics: –Automatically, through GATHER_STATS_JOB –Manually, with the DBMS_STATS package –By setting database initialization parameters –By importing statistics from another database

9 9-9 Copyright © 2006, Oracle. All rights reserved.

10 9-10 Copyright © 2006, Oracle. All rights reserved. Oracle Wait Events A collection of wait events provides information about the sessions or processes that had to wait or must wait for different reasons. These events are listed in the V$EVENT_NAME view. Tuning >Statistics SGA Attach AWR Advisors Async. Commit

11 9-11 Copyright © 2006, Oracle. All rights reserved. V$SGASTAT pool name bytes V$SYSSTAT statistic# name class value stat_id V$SYSTEM_EVENT event total_waits total_timeouts time_waited average_wait time_waited_micro System Statistics V$EVENT_NAME event_number event_id name parameter1 parameter2 parameter3 wait_class V$SYSTEM_WAIT_CLASS wait_class_id wait_class# wait_class total_waits time_waited

12 9-12 Copyright © 2006, Oracle. All rights reserved.

13 9-13 Copyright © 2006, Oracle. All rights reserved. Displaying Session-Related Statistics V$STATNAME statistic# name class V$SESSTAT sid statistic# value V$SESSION sid serial# username command osuser seq# event# event p1/2/3text p1/2/3 p1/2/3raw wait_class wait_time seconds_in_wait state... V$SESSION_EVENT sid event total_waits total_timeouts time_waited average_wait max_wait time_waited_micro event_id V$EVENT_NAME event# name parameter1 parameter2 parameter3

14 9-14 Copyright © 2006, Oracle. All rights reserved. Displaying Service-Related Statistics For n-tier environments, because session statistics are not as helpful, you can see service-level statistics in these views: V$SERVICE_EVENT: Aggregated wait counts and wait times for each service, on a per event basis V$SERVICE_WAIT_CLASS: Aggregated wait counts and wait times for each service on a wait class basis

15 9-15 Copyright © 2006, Oracle. All rights reserved. Instance/Database V$DATABASE V$INSTANCE V$PARAMETER V$SPPARAMETER V$SYSTEM_PARAMETER V$PROCESS V$BGPROCESS V$PX_PROCESS_SYSSTAT V$SYSTEM_EVENT Troubleshooting and Tuning Views Disk V$DATAFILE V$FILESTAT V$LOG V$LOG_HISTORY V$DBFILE V$TEMPFILE V$TEMPSEG_USAGE V$SEGMENT_STATISTICS Contention V$LOCK V$UNDOSTAT V$WAITSTAT V$LATCH Memory V$BUFFER_POOL_STATISTICS V$LIBRARYCACHE V$SGAINFO V$PGASTAT

16 9-16 Copyright © 2006, Oracle. All rights reserved. Dictionary Views The following dictionary and special views provide useful statistics after using the DBMS_STATS package: – DBA_TABLES, DBA_TAB_COLUMNS – DBA_CLUSTERS – DBA_INDEXES – DBA_TAB_HISTOGRAMS This statistical information is static until you reexecute the appropriate procedures in DBMS_STATS.

17 9-17 Copyright © 2006, Oracle. All rights reserved. Diagnosis of Hung or Extremely Slow Databases Use for problem analysis when the database is performing very slowly, or is hung: Direct access to SGA for performance monitoring (memory access mode) – V$SESSION – V$SESSION_WAIT – V$SYSTEM_EVENT – V$SYSSTAT –Hang analysis using Enterprise Manager Tuning Statistics >SGA Attach AWR Advisors Async. Commit

18 9-18 Copyright © 2006, Oracle. All rights reserved. Using Memory Access Mode

19 9-19 Copyright © 2006, Oracle. All rights reserved. Using the Hang Analysis Page Micro-window

20 9-20 Copyright © 2006, Oracle. All rights reserved. Using the Hang Analysis Page (notes only page)

21 9-21 Copyright © 2006, Oracle. All rights reserved. Automatic Workload Repository SYSAUX SGA In-memory statistics 6:00 a.m. 7:00 a.m. 8:00 a.m. Snapshot 1 Snapshot 2 Snapshot 3 Snapshot 4 9:00 a.m. 9:30 a.m. ADDM finds top problems. MMON Tuning Statistics SGA Attach >AWR Advisors Async. Commit

22 9-22 Copyright © 2006, Oracle. All rights reserved. Automatic Workload Repository (notes only slide)

23 9-23 Copyright © 2006, Oracle. All rights reserved. AWR Snapshot Baselines DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE ( - start_snap_id IN NUMBER, end_snap_id IN NUMBER, baseline_name IN VARCHAR2); Relevant period in the past

24 9-24 Copyright © 2006, Oracle. All rights reserved. Advisory Framework: Overview ADDM SQL Tuning Advisor SQL Access Advisor Memory Space PGA Advisor SGA Segment Advisor Undo Advisor Buffer Cache Advisor Library Cache Advisor PGA Tuning Statistics SGA Attach AWR >Advisors Async. Commit

25 9-25 Copyright © 2006, Oracle. All rights reserved.

26 9-26 Copyright © 2006, Oracle. All rights reserved. Database Control and Advisors

27 9-27 Copyright © 2006, Oracle. All rights reserved. Typical Advisor Tuning Session Adjust task parameters. Accept results? Implement recommendations. Yes No Perform analysis. Create an advisor task.

28 9-28 Copyright © 2006, Oracle. All rights reserved. Manually Invoking ADDM

29 9-29 Copyright © 2006, Oracle. All rights reserved. Using the SQL Tuning Advisor: Review Use the SQL Tuning Advisor to analyze SQL statements and obtain performance recommendations. Sources for SQL Tuning Advisor to analyze: –Top SQL: Analyzes the top SQL statements currently active –SQL Tuning Sets: Analyzes a set of SQL statements you provide –Snapshots: Analyzes a snapshot –Baselines: Analyzes a baseline

30 9-30 Copyright © 2006, Oracle. All rights reserved. SQL Access Advisor: Overview SQL Access Advisor Recommendations -Indexes -Materialized views -Materialized view logs Workload specification -SQL statement -SQL Tuning Set -SQL cache contents -Statistics -Schema name

31 9-31 Copyright © 2006, Oracle. All rights reserved. Typical SQL Access Advisor Session

32 9-32 Copyright © 2006, Oracle. All rights reserved. Workload Source

33 9-33 Copyright © 2006, Oracle. All rights reserved. Recommendation Options

34 9-34 Copyright © 2006, Oracle. All rights reserved. Recommendation Options

35 9-35 Copyright © 2006, Oracle. All rights reserved. Reviewing Recommendations

36 9-36 Copyright © 2006, Oracle. All rights reserved. Asynchronous COMMIT The default COMMIT behavior is to wait until redo is saved in the redo log files. The default behavior can now be changed to not wait. Asynchronous COMMIT is useful for high transaction throughput. However, transactions may be lost. –Machine crashes –File I/O problems with redo log files Tuning Statistics SGA Attach AWR Advisors >Async. Commit

37 9-37 Copyright © 2006, Oracle. All rights reserved. Using Asynchronous COMMIT Possible combinations: – IMMEDIATE, WAIT (this is the default) – IMMEDIATE, NOWAIT – BATCH, WAIT – BATCH, NOWAIT System- or session-level examples: COMMIT statement examples: ALTER SYSTEM SET COMMIT_WRITE = IMMEDIATE, WAIT ALTER SESSION SET COMMIT_WRITE = IMMEDIATE, NOWAIT COMMIT WRITE BATCH WAIT COMMIT WRITE BATCH NOWAIT

38 9-38 Copyright © 2006, Oracle. All rights reserved. Summary In this lesson, you should have learned how to: Diagnose database performance issues Configure the Automatic Workload Repository Access the database advisors Use the SQL Access Advisor to improve database performance Use asynchronous COMMIT effectively

39 9-39 Copyright © 2006, Oracle. All rights reserved. Practice Overview: Using ADDM to Diagnose Performance Problems This practice covers the following topics: Viewing and interpreting ADDM findings to diagnose a performance problem Implementing those findings

40 9-40 Copyright © 2006, Oracle. All rights reserved.


Download ppt "9 Copyright © 2006, Oracle. All rights reserved. Automatic Performance Management."

Similar presentations


Ads by Google