oracle 10g ADDM

oracle 10g addm在10g中,大家應該都知道addm是做什麼的吧?如果不熟悉請去看看"Oracle Database 10 g : 為 DBA 提供的最佳前 20 位的特性",在$ORACLE_HOME/rdbms/admin目錄中,addm產生報表的指令碼有addmrpt.sql及addmrpti.sql,addmrpt.sql用於單例項,addmrpti.sql用於多例項.
測試請看如下所示:

SQL> @?/rdbms/admin/addmrpt
Current Instance
~~~~~~~~~~~~~~~~
DB Id DB Name Inst Num Instance
----------- ------------ -------- ------------
1861383692 TEST 1 test

Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id Inst Num DB Name Instance Host
------------ -------- ------------ ------------ ------------
* 1861383692 1 TEST test test
* 1861383692 1 TEST test 10gR2T1
Using 1861383692 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 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
------------ ------------ --------- ------------------ -----
test TEST 157 25 Jul 2005 00:00 1
158 25 Jul 2005 01:00 1
210 27 Jul 2005 05:00 2
211 27 Jul 2005 06:00 2
212 27 Jul 2005 07:00 2
Snap
Instance DB Name Snap Id Snap Started Level
------------ ------------ --------- ------------------ -----
test TEST 213 27 Jul 2005 08:00 2
214 27 Jul 2005 09:00 2
Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Enter value for begin_snap: 211
Begin Snapshot Id specified: 211
Enter value for end_snap: 212
End Snapshot Id specified: 212
Specify the Report Name
~~~~~~~~~~~~~~~~~~~~~~~
The default report file name is addmrpt_1_211_212.txt. To use this name,
press to continue, otherwise enter an alternative.
Enter value for report_name:
Using the report name addmrpt_1_211_212.txt

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

Generating the ADDM report for this analysis ...

DETAILED ADDM REPORT FOR TASK 'TASK_706' WITH ID 706
----------------------------------------------------
Analysis Period: 27-JUL-2005 from 06:00:48 to 07:00:53
Database ID/Instance: 1861383692/1
Database/Instance Names: TEST/test
Host Name: 10gR2T1
Database Version: 10.2.0.1.0
Snapshot Range: from 211 to 212
Database Time: 5089 seconds
Average Database Load: 1.4 active sessions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

FINDING 1: 30% impact (1504 seconds)
------------------------------------
Wait event "Streams capture: waiting for archive log" in wait class "Other"
was consuming significant database time.
RECOMMENDATION 1: Application Analysis, 30% benefit (1504 seconds)
ACTION: Investigate the cause for high "Streams capture: waiting for
archive log" waits. Refer to Oracle's "Database Reference" for the
description of this wait event.
RECOMMENDATION 2: Application Analysis, 30% benefit (1504 seconds)
ACTION: Investigate the cause for high "Streams capture: waiting for
archive log" waits in Service "SYS$USERS".
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Other" was consuming significant database time.
(30% impact [1506 seconds])
FINDING 2: 15% impact (765 seconds)
-----------------------------------
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: DB Configuration, 15% benefit (765 seconds)
ACTION: Investigate the cause for the "Logminer" processes consuming 20%
of the host CPU.
ADDITIONAL INFORMATION:
The instance spent significant time on CPU. However, there were no
predominant SQL statements responsible for the CPU load.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
----------------------
Wait class "Application" was not consuming significant database time.
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.
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 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_211_212.txt