如何生成addm报告

运行$ORACLE_HOME/rdbms/admin/addmrpt.sql

D:\>set nls_lang=AMERICAN

D:\>sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Production on Sat Aug 18 22:17:18 2012

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> @G:\oracle\product\10.2.0\db_1\RDBMS\ADMIN\addmrpt.sql

Current Instance
~~~~~~~~~~~~~~~~

   DB Id    DB Name      Inst Num Instance
----------- ------------ -------- ------------
 3913660635 ORALIFE             1 oralife


Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   DB Id     Inst Num DB Name      Instance     Host
------------ -------- ------------ ------------ ------------
* 3913660635        1 ORALIFE      oralife      LAUGHING-PC

Using 3913660635 for database Id
Using          1 for instance number


Specify the number of days of snapshots to choose from
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Entering the number of days (n) will result in the most recent
(n) days of snapshots being listed.  Pressing <return> without
specifying a number lists all completed snapshots.



Listing the last 3 days of Completed Snapshots

                                                        Snap
Instance     DB Name        Snap Id    Snap Started    Level
------------ ------------ --------- ------------------ -----
oralife      ORALIFE            936 16 Aug 2012 00:00      1

                                937 16 Aug 2012 20:23      1
                                938 16 Aug 2012 21:01      1

                                939 17 Aug 2012 20:13      1
                                940 17 Aug 2012 21:00      1
                                941 17 Aug 2012 22:00      1
                                942 17 Aug 2012 23:00      1
                                943 18 Aug 2012 00:00      1

                                944 18 Aug 2012 09:31      1
                                945 18 Aug 2012 10:56      1
                                946 18 Aug 2012 10:59      1
                                947 18 Aug 2012 17:25      1
                                948 18 Aug 2012 18:00      1
                                949 18 Aug 2012 19:00      1
                                950 18 Aug 2012 19:10      1
                                951 18 Aug 2012 19:10      1
                                952 18 Aug 2012 19:23      1
                                953 18 Aug 2012 19:23      1
                                954 18 Aug 2012 20:00      1
                                955 18 Aug 2012 20:30      1
                                956 18 Aug 2012 21:00      1
                                957 18 Aug 2012 21:30      1
                                958 18 Aug 2012 22:00      1



Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enter value for begin_snap: 945
Begin Snapshot Id specified: 945

Enter value for end_snap: 946
End   Snapshot Id specified: 946



Specify the Report Name
~~~~~~~~~~~~~~~~~~~~~~~
The default report file name is addmrpt_1_945_946.txt.  To use this name,
press <return> to continue, otherwise enter an alternative.

Enter value for report_name:

Using the report name addmrpt_1_945_946.txt


Running the ADDM analysis on the specified pair of snapshots ...


Generating the ADDM report for this analysis ...


          DETAILED ADDM REPORT FOR TASK 'TASK_3683' WITH ID 3683
          ------------------------------------------------------

              Analysis Period: 18-AUG-2012 from 10:56:24 to 10:59:50
         Database ID/Instance: 3913660635/1
      Database/Instance Names: ORALIFE/oralife
                    Host Name: LAUGHING-PC
             Database Version: 10.2.0.1.0
               Snapshot Range: from 945 to 946
                Database Time: 1421 seconds
        Average Database Load: 6.9 active sessions

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


FINDING 1: 100% impact (1440 seconds)
-------------------------------------
SQL statements were found waiting for row lock waits.

   RECOMMENDATION 1: Application Analysis, 100% benefit (1440 seconds)
      ACTION: Significant row contention was detected in the TABLE "LAU.T"
         with object id 56826. Trace the cause of row contention in the
         application logic using the given blocked SQL.
         RELEVANT OBJECT: database object with id 56826
      RATIONALE: The SQL statement with SQL_ID "4kg9ytrpamq3d" was blocked on
         row locks.
         RELEVANT OBJECT: SQL statement with SQL_ID 4kg9ytrpamq3d
         update t set id=30000 where id=1

   SYMPTOMS THAT LED TO THE FINDING:
      SYMPTOM: Wait class "Application" was consuming significant database
               time. (100% impact [1440 seconds])

FINDING 2: 100% impact (1421 seconds)
-------------------------------------
SQL statements consuming significant database time were found.

   RECOMMENDATION 1: SQL Tuning, 100% benefit (1452 seconds)
      ACTION: Investigate the SQL statement with SQL_ID "4kg9ytrpamq3d" for
         possible performance improvements.
         RELEVANT OBJECT: SQL statement with SQL_ID 4kg9ytrpamq3d and
         PLAN_HASH 931696821
         update t set id=30000 where id=1
      RATIONALE: Waiting for event "enq: TX - row lock contention" in wait
         class "Application" accounted for 99% of the database time spent in
         processing the SQL statement with SQL_ID "4kg9ytrpamq3d".


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          ADDITIONAL INFORMATION
          ----------------------

Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
CPU was not a bottleneck for the instance.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.

The database's maintenance windows were active during 100% of the analysis
period.

The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.

An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.


End of Report
Report written to addmrpt_1_945_946.txt