Skip to main content

Difference between AWR, ADDM and ASH reports


AWR:

Automatic Workload Repository gathers, processes and maintains performance stats used for problem detection and self-tuning the databases.

Different Components that uses AWR are:
Automatic Database Diagnostic Monitor
Undo Advisor
SQL Tuning Advisor
Segment Advisor


Different types of AWR Reports for different purposes:

For Single Instance Environment:
@$ORACLE_HOME/rdbms/admin/awrrpt.sql

For Oracle RAC Environment :
@$ORACLE_HOME/rdbms/admin/awrgrpt.sql

For a particular SQL Statement :
@$ORACLE_HOME/rdbms/admin/awrsqrpt.sql

For Comparing the reports :
@$ORACLE_HOME/rdbms/admin/awrddrpt.sql

ADDM:

Automatic Database Diagnostic Monitoring Report analyzes the AWR data on a regular basis, to give you overview of the root cause of the problem which is affecting your database’s performance. It also provides suggestions or recommendations for rectifying any problem identified and lists the areas which are having no issues. ADDM recommends multiple solutions for the DBA to choose from which includes,

Database Configuration
Hardware changes
Schema changes
Application changes &
Other advisories

generate ADDM:

@$ORACLE_HOME/rdbms/admin/addmrpt.sql

ASH:

ASH is an integral part of the Oracle Database self-management framework and is extremely useful for diagnosing performance problems. ASH gathers sampled data at the session level rather than at the instance level. By capturing statistics for only active sessions, ASH collects a manageable set of data.


Below mentioned is the script which you can run to generate your ASH report,

@$ORACLE_HOME/rdbms/admin/ashrpt.sql

For Oracle RAC Environment :

@$ORACLE_HOME/rdbms/admin/ashrpti.sql

Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more