database performance management workshop · database performance management 6. look for the status...

An Oracle Hands-on Lab Workbook February, 2013

Database Performance Management Workshop

of 35

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab

Objective: The objective of this lab to provide exercises designed to showcase the new database performance management capabilities in Oracle Enterprise Manager Cloud Control 12c. Functional Coverage: In this lab you will go through following features:

A. Overview of the Database Home Page (5 minutes) B. ASH Analytics (15 minutes) C. SQL Monitoring (8 minutes) D. Real Time ADDM (10 minutes) E. SQL Performance Analyzer (8 minutes)

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab Getting Started

I-Pre-requites -

Enterprise Manager (EM) should be running on your lab VM. To verify that EM is running - go to the EM URL provided, you should get the EM login page. If you get an error page, please contact your lab administrator or start Enterprise Manager yourself by following the instructions provided in the lab cheat sheet.

II- Starting lab environment. Before you start with this lab, you‘ll need to start the necessary targets and other processes (as applicable). All the steps have been automated in an EM job ‘1-START DB PERFORMANCE MGMT LAB’. To execute this job follow the following steps.

1. Login to Enterprise Manager using username and password dbuser / oracle12.

2. Navigate to ‘Job Library’ page by clicking on menu – Enterprise Job Library

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 3. Select job ‘1-START DB PERFORMANCE MGMT LAB’ and click ‘Submit’ button.

4. Click on ‘Submit’ button again.

5. To ensure that job ran successfully, click on the job activity link provided in the confirmation message.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 6. Look for the status ‘Succeeded’. Job takes ~30 seconds. Therefore you might need to refresh page a few times.

7. You can now move on to the lab exercises. Please allow at least 30 minutes for Database load charts to show up data. Enterprise Manager login has been provided at the beginning of exercise.

III- Shutting down lab environment After you complete this lab and before moving to next lab, please make sure to stop this lab environment by running the EM job ‘1-STOP DB PERFORMANCE MGMT LAB’. To run this EM job you can follow the steps for starting lab environment, and select stop job.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab A. Overview of the Database Home Page

Estimated Time to Complete Use Case: 5 minutes Business Problem/Use Case

This Use Case is intended to familiarize the user with the new functionality of the Database Home page. We have made some significant modifications to the Database Home page in Oracle Enterprise Manager 12c. The homepage has been divided into regions that can be personalized based on the requirement of the users. The performance region allows the administrator to quickly gauge system resource utilization by wait classes or by various database services. The Monitored SQL region gives a snapshot of all queries currently executing and can be very useful to identify long running queries.

1.1 Login to Enterprise Manager using username and password dbuser / oracle12.

1.2 Navigate to Databases: From the menu, Targets -> Databases

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 1.3 Click on Database Name: prod.oracle.com

1.4 This will take you to the database home page for prod.oracle.com

1.5 As an example of how pages can be personalized, let’s move one region to a different location on the page. Scroll down and find the region “SQL Monitor – Last Hour”.

Click on the header and drag the region to the top of the page, placing it above the “Performance Region”

of 37


1.6 Once the move is completed, the home page should look like this:

1.7 Students can continue to play with the Actions menu to show that the Home Page can be personalized.

1.8 Students can better understand the Performance region by reviewing the active sessions chart by Wait Classes, and then move onto the Services Tab

of 37


of 37


B. ASH Analytics Estimated Time to Complete Use Case: 15 minutes Business Case

Oracle Enterprise Manager 12c introduces ASH Analytics, a new tool to explore the ASH (Active Session History) data that allows the administrator to rollup, drilldown, and slice or dice performance data across various performance dimensions. With the ability to create filters on various dimensions, identifying performance issues has never been easier. The built-in Loadmap view allows administrators to explore performance data using predefined performance dimension hierarchies.

2. Understanding the ASH Analytics page

2.1 Log on to Enterprise Manager.

2.2 Navigate to prod database Ash Analytics page via menu Targets Databases

Choose prod as your database.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab Navigate to ‘ASH Analytics’ page from the specific database page via ‘Performance’ ‘ASH Analytics’

2.3 On the Database login page, select ‘Named Credentials’, wait for login credentials to auto-populate and click login button.

Tip: If you have already logged to this database earlier, you will not be shown this page.

2.4 Shown below is the ASH Analytics Home Page. Notice the following:

2.4.1 Select the Hour Time Period for investigation: Use the slider at the top of the chart to select a time period which has a high workload. The graph below the time window is a close-up detail of the time window’s time period. Click on Day or Week period to view different levels across days then choose Hour.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 2.6 The detail graph’s drop-down menu defaults to Wait Class. The graph’s legend on the right always

matches the drop-down menu on the upper left.

2.7 Review the different Wait Classes:

2.7.1 In the 2nd chart from the top, students will observe the detailed view of the time window that has been selected.

2.7.2 By default the wait class dimension is selected. Observe the different wait classes for the window selected (blue for USER_IO, green for CPU etc.)

2.8 Become familiar with the different dimensions: For example, change the dimension from Wait Class to SQL ID.

From the drop down, choose Top Dimensions -> SQL ID. Observe the change in the chart. The use of different performance dimensions allows the user to get a perspective of what is currently running and how the system resources are being utilized.

of 37


2.9 Let’s examine the different filtering capabilities of ASH Analytics:

2.9.1 Select Service as the Top Dimension. From the drop down, select Top Dimensions -> Service

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 2.9.2 Click on the chart for the service ‘prod.oracle.com’ and set it as a filter.

Note: Depending on the workload characteristics and time period chosen you might not see the exactly the same services. If you don’t find prod, then choose the service with biggest block of color.

2.9.3 Once the filter is set, it will be indicated next to the filter label. Filtered view shows the wait classes view for the specified service.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 2.9.4 Observe how view changes with filter. Let‘s see how other dimensions are affected by the same

filter. With the filter enabled, change the dimension from “Wait Class” to “Module”.

Select Top Dimension Module.

2.9.5 Observe the breakdown of waits by module.

In the table at the bottom by default you can view the SQL ID, and Session by Average Active Session. Drilling down into the SQL ID is NOT included in this lab, although the sql details page is accessible by clicking on the sql_id (please do not click the sql_id)

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 2.10 Remove all the filters by clicking on the icon and select the Wait Class via drop down Top

Dimension Wait Class

2.11 Explore the Load Map view: Click on the Load Map button.

2.12 Select a predefined view - Simple mode, and Service/Module/SQL ID

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 2.13 Increase the number of visible dimensions: Drag the slider to 3. The SQL IDs will be added to the chart.

2.14 Experiment with other pre-set treemaps and add filters: Select different Load Map dimensions and change from 2 to 3 to understand how the chart changes.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab C. SQL Monitoring

Environment Details:

The target database is running a load on the sample schema provided via the Examples (or companion) software accompanying the Oracle database software. There are other schemas created to simulate specific performance scenarios.

Estimated Time to Complete Use Case: 8 minutes

Business Case

The first step in SQL tuning is identifying poorly performing SQL that are consuming excessive system resources. Traditionally, DBAs have always struggled with long-running SQL in live production environments because they never had the tools to figure out if the long-running query was moments away from completion or a run-away query that could take an inordinate amount of time to complete. Real-Time SQL Monitoring introduced in Oracle Database 11g provides the fastest and easiest way to identify and fix performance problems with long running SQL statements. Live visual displays track the details of SQL execution using new, fine-grained SQL statistics that are updated automatically at no cost to the performance of production systems.

3. Understanding the SQL Monitoring

3.1 You should already be logged on to Enterprise Manager. If you are not, please follow the instructions

detailed in earlier section of this workbook.

3.2 To enable this exercise, we first need to launch a script that generates certain SQL statements/activity. We will launch this job from the Job Library section of Enterprise Manager.

From any page, access the Job Library via Enterprise -> Job -> Library

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 3.3 Select the radio button at “Start SQL Monitoring” and click Submit

3.4 Click Submit again.

This job will run in the background. Proceed to the next step.

3.1 Now, let’s examine the effect of this job.

Navigate to prod database homepage via menu Favorites prod.oracle.com prod database instance

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 3.5 Go to the SQL Monitoring Page. Click on Performance -> SQL Monitoring

3.6 On the Database login page, select ‘SYSDBA Database Credentials’, wait for login credentials to auto-populate and click login button.

Tip: If you have already logged to this database in the earlier labs, you will not be shown this page.

3.7 Explore the Monitored SQL Executions page. By drilling down on each of the SQL statements on the list, it is possible to get an insightful view into the execution of each one of them.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 3.8 The SQL Monitoring job that we have launched generates a number of different SQL statements. We will

be looking at one in particular - g3r7n3w7j4dt6.

Note: In case you don’t see the specified SQL ID, then wait for ‘Start SQL Monitoring’ job to complete and run this job again in a new window and refresh the ‘Monitored SQL Execution’ page. Selecting a different SQL ID will not show the desired results.

Click on the Sundial to drill down into the SQL statement.

3.9 Explore the Monitored SQL Execution Details Page.

The upper portion of the page lists general information as well as cumulative wait class statistics similar to what is displayed on the Monitored SQL Executions page.

of 37


3.10 Click on the “Parallel” Tab in the details section. Expand the Parallel Sets by clicking on the plus inside of the square icon to the left of the Parallel Set name

The Parallel tab displays the distribution of resources between two Parallel Sets as well as across the Parallel Servers in each Parallel Set. This is very useful for detecting parallel execution skews for a PQ.

Notice that parallel set #2 is experiencing more load than the other.

3.11 Click on the “Plan” Tab.

Notice that there are two views: Graphical and Tabular.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab Use the radio button to switch between them.

3.12 Click on the “Activity” tab.

This permits the viewing of the Active Session History (ASH) data in the graphical format. This page can be carefully studied to get insightful knowledge on the details of the SQL execution process.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 3.13 Click on the “Metrics” tab. Review each chart and note the CPU , IO , PGA and Temp usage

3.14 This concludes the SQL Monitoring exercise

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab D. Real-Time ADDM

Environment Details:

The target database is running a load on the sample schema provided via the Examples (or companion) software accompanying the Oracle database software. There are other schemas created to simulate specific performance scenarios.

Estimated Time to Complete Use Case: 10 minutes

Business Case This use case is intended to give an idea of the basic functionality of the Real-Time ADDM (where ADDM stands for Automatic Database Diagnostics Monitor). Real-Time ADDM is an innovative way to analyze problems in extremely slow or hung databases. Real-Time ADDM runs through a set of predefined criteria to analyze the current performance and helps the DBA to resolve deadlocks, hangs, shared pool contentions and many other exception situations which force the administrator to bounce their databases today.

4. Understanding Real-Time ADDM

4.1 You should already be logged on to Enterprise Manager. If you are not, please follow the instructions detailed in earlier section of this workbook.

4.2 This exercise requires users to launch a job that causes a hung job. In order to do that, go to the Job Activity Page from any page.

Select Enterprise -> Job -> Library

4.3 Initiate the Real Time ADDM Load. Select the radio button for Job “Setup Database Hang”, and click submit.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 4.4 When the job screen opens, click submit again.

Note: Make sure the job starts running. It will run for 10 minutes – the duration of the exercise.

Note: Make sure the job starts running. If it shows Scheduled (1) then click the Refresh icon (2) until its status is Running. Then go to the next step below. It will run for 10 minutes – the duration of the exercise.

4.5 Log out of Enterprise Manager and all objects you are connected to. Then log back in.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 4.6 Go to Targets -> Databases.

4.7 Given that the job that we just launched put the database in a hung state, you might receive messages

that it is having difficulty connecting to the database, or that it failed to connect. This is expected.

4.8 From the Database Home Page, select target menu Performance -> Real-Time ADDM.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 4.9 On the Database login page, select ‘Named Credentials’, wait for login credentials to auto-populate and

click ‘Submit’ button.

Tip: If you had stayed logged into the database instead of logging out, you may not have seen this page.

4.10 When the Real-Time ADDM page opens, you will see two sections - the graphical section on top, and the Details section on the bottom. Real-time ADDM is able to access the database even though it’s hung.

4.11 In the Details section, click on the Start button.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab Because the database is hung:

1. Observe the Normal Connections window will not be populated, but instead will continue spinning 2. When the Number of Findings turns to “1”… 3. …Then click on the Findings tab.

4.12 Click on the Findings tab.

Here you will see the offending process id. Make note of the operating system process id. In this particular example, there is only one offending OS process.

Note: Depending on the load characteristics, you might see two processes instead of one. In that case please kill both the processes in the next step.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab To kill the process, you’ll need to connect to the VM. You can either use VNC viewer (VNC Viewer, Tight

VNC) or PuTTY. VNC server name : <Your VM IP address>:1 VNC and OS Passwords : oracle12

4.13 To open a terminal session in the VNC, right click on desktop and click ‘Open Terminal’.

4.14 To kill the OS process, execute “kill -9 <process id>” in the command window.

4.15 Return to the Real Time ADDM page. Click on the ‘Progress’ tab.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab The page might take 60-90 seconds to refresh itself, but once it does, it should show status as (1)

‘FINISHED’ reflecting that the database is no longer in a hung state.

Click on the (2) Hang Data tab.

The OS process ID is the same one we just killed. This screen shows the database was hung and also shows the sessions and users affected.

4.16 This completes the Real Time ADDM exercise.

of 37


E. SQL Performance Analyzer Estimated Time to Complete Use Case: 8 minutes

Business Case

SQL Performance Analyzer (SPA), introduced in Oracle Database 11g, can help predict and prevent SQL execution performance problems caused by system changes. SQL Performance Analyzer provides a granular view of the impact of changes on SQL execution plans and execution statistics by running the SQL statements in isolation before and after a change. In this lab we will use SQL Performance Analyzer to simulate the improvement in interconnect IO that can be seen by moving from legacy hardware to the Oracle Exadata Database Machine.

4. Understanding SQL Performance Analyzer

6.1 You should already be logged on to Enterprise Manager. If you are not, please follow the instructions

detailed in earlier section of this workbook. Go to Targets -> Databases and select Prod as your database.

Now choose Performance -> SQL -> SQL Performance Analyzer.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 6.2 Select “Named Credential” and click Submit.

6.3 Click on Exadata Simulation as the workflow.

4.1 Now, let’s select a job and compare its current performance to its estimated performance on Exadata.

1. Type in a Test Name 2. Click on SQL Tuning Set then 3. Choose TPCH and 4. click Select.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 6.4 The SQL Tuning Set name will auto-fill, then click on Submit to submit the job.

6.5 You’ll see a Confirmation that the job has been created. If the Last Run Status says Processing, then click the Refresh button until the status says Completed.

6.6 Once the job is Completed, click on View Latest Report for a rich summary report of the job’s run.

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab 6.7 SQL Performance Analyzer shows us the order of magnitude improvement in for I/O Interconnect Bytes

when using Exadata compared to traditional solutions. SQL Performance Analyzer estimates a 91% improvement overall. It also provides us estimated improvement for each SQL in the SQL Tuning Set.

Click on a SQL statement that shows the highest degree of improvement.

6.8 We see a summary of useful pertinent metrics, all of which show dramatic improvement in SQL Trial 2,

which was simulating Exadata’s impressive interconnect performance. Scroll down the page for more explanation, a quite striking explanation:

of 37

ORACLE ENTERPRISE MANAGER Cloud Control 12c Database Performance Management Lab Here we see the execution plans for the two runs of the query. As we can see, in SQL Trial 2 Exadata’s

predicate push-down capability pushed the most expensive predicate down to the Exadata storage servers. We can even see the precise predicate that got pushed down.

Stop the Database Performance Management Lab

environment This concludes Database Performance Management lab. Before moving to next lab, please make sure to stop this lab environment by running the EM job ‘1-STOP DB PERFORMANCE MGMT LAB’. To execute this EM job, refer the steps given in the ‘Getting Started’ section.

Oracle EM12c Cloud Control Database Performance Management Workshop February, 2013 Author: Deba Chatterjee Contributing Authors: Ankur Gupta

Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A.

Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200

oracle.com

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd. 1010

database performance management workshop · database performance management 6. look for the status...

Documents