The Automatic Database Diagnostic Monitor (hereafter called ADDM) is an integral part of the Oracle RDBMS capable of gathering performance statistics and advising on changes to solve any existing performance issues measured.
Automatic database diagnostic monitoring is enabled by default and is controlled by the STATISTICS_LEVEL initialization parameter. The STATISTICS_LEVEL parameter should be set to the TYPICAL or ALL to enable the automatic database diagnostic monitoring. By default =allThe
types of problems that ADDM considers include the following:- CPU bottlenecks - Is the system CPU bound by Oracle or some other application?
- Undersized Memory Structures - Are the Oracle memory structures, such as the SGA,PGA, and Buffer cache, adequately sized?
- I/O capacity issues - Is the I/O subsystem performing as expected?
- High load SQL statements - Are there any SQL statements which are consuming excessive system resources?
- High load PL/SQL execution and compilation, as well as high load Java usage
- RAC specific issues - What are the global cache hot blocks and objects; are there any Interconnect latency issues?
- Sub-optimal use of Oracle by the application - Are there problems with poor connection management, excessive parsing, or application level lock contention?
- Database configuration issues - Is there evidence of incorrect sizing of log files,archiving issues, Excessive checkpoints or sub-optimal parameter settings?
- Concurrency issues - Are there buffer busy problems?
- At the SQL prompt, enter:
@$ORACLE_HOME/rdbms/admin/addmrpt.sql
No comments:
Post a Comment