ASH, AWR AND ADDM

01 03

02
ASH Report ADDM Report
ASH report contains data Automatic
that helps you to: Triage AWR Report performance
transient performance diagnostic report
Automatic Workload
problems that typically last every hour by default
Repository (AWR) collects,
for a few minutes
processes, and maintains
performance statistics for
problem detection and self-
tuning purposes.
Automatic Database Diagnostic Monitor (ADDM)
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 Automatic Database Performance Monitoring, ADDM runs once
every hour by default. You can configure ADDM to run at a different time interval. 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.
Manually Running ADDM to Analyze Current 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 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 continue on the new run cycle, occurring hourly at the half-hour instead
of the start of each hour.
 ADDM analyze current DB performance

To analyze current database performance by manually running ADDM:

1. Access the Database Home page.
See "Accessing the Database Home Page" for more information.
2. From the Performance menu, select Advisors Home.
If the Database Login page appears, then log in as a user with administrator privileges. The
Advisor Central page appears.
3. Under Advisors, select ADDM. The Run ADDM page appears.
4. Select Run ADDM to analyze current performance and click OK.
The Confirmation page appears.
5. 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.
6. Click View Report.
7. The View Report page appears.
Optionally, click Save to File to save the results of the ADDM task in a report for later access.
 ADDM to Analyze Historical DB Performance
Manually Running ADDM to Analyze Historical Database Performance
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 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:
Access the Database Home page:
See "Accessing the Database Home Page" for more information.
From the Performance menu, select Advisors Home.
If the Database Login page appears, then log in as a user with administrator privileges. The Advisor Central page appears.
Under Advisors, select ADDM. The Run ADDM page appears.
Select Run ADDM to analyze past 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
 Accessing Previous ADDM Results
Accessing Previous ADDM Results
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.
To access the ADDM results:
Access the Database Home page.
See "Accessing the Database Home Page" for more information.
From the Performance menu, select Advisors Home.
If the Database Login page appears, then log in as a user with administrator privileges. 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.
Running ADDM from command line:
SQL script for getting ADDM Report on RAC database:
SQL>@$ORACLE_HOME/rdbms/admin/addmrpti.sql
SQL script for getting ADDM Report for single instance:
SQL>@$ORACLE_HOME/rdbms/admin/addmrpt.sql
 ADDM & Analysis
The Automatic Database Diagnostic Monitor (ADDM):
It is a tool that analyzes data in the Automatic Workload Repository (AWR) performing accurate and timely
diagnosis of the problem. It locates the root cause and provides recommendations for correcting the problem.
For those who are new to performance tuning, AWR (Automatic Workload Repository) is a built-in repository
(in the SYSAUX tablespace) that exists in every Oracle Database. At regular intervals, the Oracle Database
makes a snapshot of all of its vital statistics and workload information and stores them in the AWR to know
more about AWR check our previous blog on Automatic Workload Repository (AWR): Database Statistics.

The ADDM Analysis Includes the following:

CPU load
Memory usage
I/O usage
Resource intensive SQL
Resource intensive PL/SQL and Java
RAC issues
Application issues
Database configuration issues
Concurrency issues
Object contention
ADDM monitor & Reccomendation
ADDM also monitors the non-problem areas of the system like wait event classes
that are not significantly impacting the system performance, they are identified and removed from the
tuning consideration at an initial stage, saving time and effort that would have been spent on items that
do not impact overall system performance.
ADDM not only recommends problem diagnostics it also provides possible solutions for the problem.
ADDM recommends one or more solutions for the DBA to choose from consisting of a variety of
recommended solutions including:
Hardware changes
Database configuration
Schema changes
Application changes
Using other advisors

ADDM Analysis:
An ADDM analysis will be performed on a pair of AWR snapshots and a collection of instances from
equivalent information. The pair of AWR snapshots outline the period of time for analysis, and the set of
instances define the target for analysis.
If you’re using Oracle Real Application Clusters (Oracle RAC).
The findings (problems) are listed in order of potential impact on database performance, along with
recommendations to resolve the issue and the symptoms which lead to its discovery.
 ADDM in Performance & Database Mode

Diagnosing Performance Problems with ADDM:

To diagnose performance problems ADDM analysis results that are automatically created each time an AWR
snapshot is taken is reviewed. You can run ADDM manually if need long analysis period or if you want to use
different DBIO_EXPECTED setting or change in the analysis mode is required.
ADDM analyzes two AWR snapshots condition being both snapshots are still stored in the AWR and analyze
instances that are started before the beginning snapshot and remain running until the ending snapshot.
Whenever possible, you should run ADDM using the Oracle Enterprise Manager. If Oracle Enterprise Manager is
unavailable, then you can run ADDM using the DBMS_ADDM package. To run the DBMS_ADDM APIs, the user must
be granted the ADVISOR privilege.

ADDM in Database Mode

In RAC configurations, you can run the ADDM in Database mode to analyze all instances of databases. You
can still run ADDM in Database mode for single-instance configurations; ADDM behaves as if running in
Instance mode.
task_name [specifies the name of the analysis task that will be created]
begin_snapshot [specifies the snapshot number of the beginning snapshot in the analysis period]
end_snapshot [snapshot number of the ending snapshot in the analysis period]
db_id [database identifier of the database that will be analyzed]