To run ADDM against a set of snapshots, use the addmrpt.sql script located in the $ORACLE_
HOME/rdbms/admin directory.
NOTE
You must have the ADVISOR system privilege in order to execute
ADDM reports.
Within SQL*Plus, execute the addmrpt.sql script. You will be prompted for the beginning and
ending snapshot IDs for the analysis and a name for the output file.
To view the ADDM data, you can use OEM or the advisor data dictionary views. The advisor
views include DBA_ADVISOR_TASKS (existing tasks), DBA_ADVISOR_LOG (status and progress
on tasks), DBA_ADVISOR_RECOMMENDATIONS (completed diagnostic tasks plus
recommendations), and DBA_ADVISOR_FINDINGS. You can implement the recommendations
to address the findings identified via ADDM. Figure 8-1 shows a typical AWR report, generated
from the default baseline; in this example, the snapshot began on 14-Sep-2007 and ended on
22-Sep-2007. This database seems to be lightly loaded with plenty of CPU and memory resources;
for example, latch contention is non-existent, and there is enough memory to perform all sorting
without using disk.
Using the Automatic SQL Tuning Advisor
New to Oracle Database 11g, the Automatic SQL Tuning Advisor runs during the default
maintenance window (using AutoTask) and targets the highest-load SQL statements collected
in the AWR. Once the automatic SQL tuning begins during a maintenance window, the following
steps are performed by the Automatic SQL Tuning Advisor:
1.
Pages:
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466