Oracle® Database 2 Day + Performance Tuning Guide 11g Release 2 (11.2) Part Number E10822-01 |
|
|
View PDF |
You can run the Automatic Database Diagnostic Monitor (ADDM) manually to monitor current and historical database performance. Typically, you use the automatic diagnostic feature of ADDM to identify performance problems with the database. As described in Chapter 3, "Automatic Database Performance Monitoring", ADDM runs once every hour by default. It is possible to configure ADDM to run more or less frequently. However, in some cases you may want to run ADDM manually.
You can run ADDM manually to analyze a time period that is longer than one ADDM analysis period. For example, you may want to analyze database performance in a workday by analyzing 8 consecutive hours. You could analyze each of the individual ADDM periods within the workday, but this approach may become complicated if performance problems appear in only some ADDM periods. Alternatively, you can run ADDM manually with a pair of Automatic Workload Repository (AWR) snapshots that encompass the 8-hour period. In this case, ADDM identifies the most critical performance problems in the entire time period.
This chapter contains the following sections:
Manually Running ADDM to Analyze Current Database Performance
Manually Running ADDM to Analyze Historical Database Performance
By default, ADDM runs every hour to analyze snapshots taken by AWR during this period. In some cases you may notice performance degradation that did not exist in the previous ADDM analysis period, or a sudden spike in database activity on the Performance page, as described in Chapter 4, "Monitoring Real-Time Database Performance". If the next ADDM analysis is not scheduled to run for 30 minutes, then you can run ADDM manually to identify and resolve the performance problem.
When you run ADDM manually, a manual AWR snapshot is created automatically. This manual run may affect the ADDM run cycle. For example, if you scheduled ADDM to run hourly at the start of each hour and the last ADDM run was at 8:00 p.m., running ADDM manually at 8:30 p.m. causes the next scheduled run to start at 9:30 p.m., not 9:00 p.m. Subsequent ADDM runs will continue on the new run cycle, occurring hourly at the half-hour instead of the start of each hour.
To analyze current database performance by manually running ADDM:
On the Database Home page, under Related Links, click Advisor Central.
The Advisor Central page appears.
Under Advisors, click ADDM.
The Run ADDM page appears.
In this example, the average active sessions with wait events rose at 10:00 a.m., peaking at 10:50 a.m. The number dipped at 11:00 a.m. and then started to rise again at 11:10 a.m.
Select Run ADDM to analyze current instance performance and click OK.
The Confirmation page appears.
Click Yes.
The Processing: Run ADDM Now page appears while the database takes a new AWR snapshot.
An ADDM run occurs for the time period between the new and the previous snapshot. After ADDM completes the analysis, the Automatic Database Diagnostic Monitor (ADDM) page appears with the results.
Click View Report.
The View Report page appears.
Optionally, click Save to File to save the results of the ADDM task in a report for later access.
You can run ADDM manually to analyze historical database performance by selecting a pair or range of AWR snapshots as the analysis period. This technique is useful when you have identified a previous time period when database performance was poor.
In the Performance page, you can monitor historical performance by selecting Historical from the View Data list. In the Historical view, you can monitor database performance in the past, up to the duration defined by the AWR retention period. If you notice performance degradation, then you can drill down from the Performance page to identify historical performance problems with the database, as described in Chapter 4, "Monitoring Real-Time Database Performance". If you identify a problem, then you can run ADDM manually to analyze a particular time period.
To analyze historical database performance by manually running ADDM:
On the Database Home page, under Related Links, click Advisor Central.
The Advisor Central page appears.
Under Advisors, click ADDM.
The Run ADDM page appears.
Select Run ADDM to analyze past instance performance.
Specify a time period for analysis by selecting a pair of AWR snapshots. Complete the following steps:
Select Period Start Time.
Below the chart for the starting snapshot, click the snapshot you want to use for the start time.
A play icon (displayed as an arrow) appears over the snapshot icon.
In this example, database activity peaked from 10 a.m. to 11 a.m., so the snapshot taken at 10 a.m. is selected for the start time.
Select Period End Time.
Below the chart for the ending snapshot, click the snapshot you want to use for the end time.
A stop icon (displayed as a square) appears over the snapshot icon.
In this example, the ending snapshot is at 11:00 a.m.
Click OK.
After ADDM completes the analysis, the Automatic Database Diagnostic Monitor (ADDM) page appears with the results of the ADDM run.
Figure 6-1 Analyzing Historical Database Performance
Click View Report.
The View Report page appears.
Optionally, click Save to File.
If you ran ADDM manually to analyze current or historical database performance, the results are displayed on the Automatic Database Diagnostic Monitor (ADDM) page after the ADDM run has completed.
You can access the ADDM results at a later time, or access the ADDM results from previous run cycles.
On the Database Home page, under Related Links, click Advisor Central.
The Advisor Central page appears.
Complete the following steps:
Under Advisor Tasks, select ADDM from the Advisory Type list.
Select the appropriate search criteria.
For example, you can select All in the Advisor Runs list to view all ADDM tasks.
Click Go.
The ADDM tasks are displayed under Results.
To view an ADDM result, select the desired ADDM task and click View Result.
The results from the selected ADDM task are shown in the Automatic Database Diagnostic Monitor (ADDM) page.