top of page
  • Writer's pictureArun Kumar

Oracle ADDM Report

  • It analysis AWR report to identify potential performance bottle neck.

  • For each identified issue, it locates the root cause and provides recommendations.

  • It is created and stored every time AWR report is run provided STATISTICS_LEVEL parameter is set to TYPICAL or ALL.

To create ADDM Report


Sample output of ADDM report:

FINDING: 59% impact (944 seconds)

  • The buffer cache was undersized causing significant additional read I/O.

RECOMMENDATION 1: DB Configuration, 59% benefit (944 seconds)

  • ACTION: Increase SGA target size by increasing the value of parameter   “sga_target” by 28 M.


  • Wait class User I/O was consuming significant database time. (83% impact [1336 seconds])


Recent Posts

See All

Oracle Optimizer determines the cost of each execution plan based on database, schema, table and other statistics. The changes inside database result in stale statistics. As a DBA, you must gather sta

The first step is to understand how instance size is configured. There are two main configurations: One Instance Size Separate SGA and PGA One Instance Size Oracle MEMORY_TARGET parameter defines the

bottom of page