This section contains detailed guidance for
evaluating each section of an AWR report. An AWR report is very
similar to a STATSPACK report, and it contains vital
elapsed-time information on what happened during particular snapshot
range. The data in an AWR or STATSPACK report is the delta, or
changes, between the accumulated metrics within each snapshot.
This gives an overall summary of the instance during the snapshot
period, and it contains important aggregate summary information.
This shows the size of each SGA region after AMM has changed them.
This information can be compared to the original
at the end of the AWR report.
This important section shows important rates expressed in units of
per second and transactions per second.
With a target of 100%, these are high-level ratios for activity in
This is a good summary of changes to the shared pool during the
This is the most important section in the AWR report. It shows the
top wait events and can quickly show the overall database
This section shows a breakdown of the main wait events in the
database including foreground and background database wait events as
well as time model, operating system, service, and wait classes
This AWR report section provides more detailed wait event information
for foreground user processes which includes Top 5 wait events and
many other wait events that occurred during the snapshot interval.
This section is relevant to the background process wait events.
Time mode statistics report how database-processing time is spent.
This section contains detailed timing information on particular
components participating in database processing.
The stress on the Oracle server is important, and this section shows
the main external resources including I/O, CPU, memory, and network
The service statistics section gives information about how
particular services configured in the database are operating.
This section displays top SQL, ordered by important SQL execution
Includes SQL statements that took significant execution time during
Includes SQL statements that consumed significant CPU time during
These SQLs performed a high number of logical reads while retrieving
These SQLs performed a high number of physical disk reads while
These SQLs experienced a high number of reparsing operations.
Includes SQL statements cursors which consumed a large amount of SGA
shared pool memory.
These SQLs have a large number of versions in shared pool for some
This section contains statistical information describing how the
database operated during the snapshot period.
(Absolute Values): This section contains statistics that have
absolute values not derived from end and start snapshots.
(Thread Activity): This report section reports a log switch activity
This section shows the all important I/O activity for the instance
and shows I/O activity by tablespace, data file, and includes buffer
Tablespace IO Stats
File IO Stats
Buffer Pool Statistics
This section show details of the advisories for the buffer, shared
pool, PGA and Java pool.
Buffer Pool Advisory
PGA Aggr Summary: PGA Aggr Target Stats; PGA Aggr
Target Histogram; and PGA Memory Advisory.
Shared Pool Advisory
Java Pool Advisory
This important section shows buffer cache waits statistics.
This important section shows how enqueue operates in the database.
Enqueues are special internal structures which provide concurrent
access to various database resources.
This section gives a summary about how undo segments are used by the
This section shows detailed history information about undo segment
This section shows details about latch statistics. Latches are a
lightweight serialization mechanism that is used to single-thread
access to internal Oracle structures.
Latch Sleep Breakdown
Latch Miss Sources
Parent Latch Statistics
Child Latch Statistics
This report section provides details about hot segments using the
Includes top segments which experienced high number of logical
Includes top segments which experienced high number of disk physical
These segments have the largest number of buffer waits caused by
their data blocks.
Includes segments that had a large number of row locks on their
Includes segments that had a large contention for Interested
Transaction List (ITL). The contention for ITL can be reduced by
increasing INITRANS storage parameter of the table.
This section exposes details about how the data dictionary cache is
Includes library cache statistics describing how shared library
objects are managed by Oracle.
This section provides summary information about various SGA regions.
This section shows the original init.ora
parameters for the instance during
the snapshot period.
SEE CODE DEPOT FOR FULL SCRIPTS