Which two statements are true about the Automatic Database Diagnostic Monitor(ADDM)?

Which two statements are true about the Automatic Database Diagnostic Monitor(ADDM)? (Choose
two.)

Which two statements are true about the Automatic Database Diagnostic Monitor(ADDM)? (Choose
two.)

A.
The ADDM requires at least four AWR snapshots for analysis

B.
The ADDM runs after each AWR snapshot is collected automatically by MMON

C.
The results of the ADDM analysis are stored in the Automatic Workload Repository (AWR)

D.
The ADDM analysis provides only diagnostics information but does not provide recommendations

E.
The ADDM calls other advisors if required, but does not provide recommendations about the
advisors



Leave a Reply 2

Your email address will not be published. Required fields are marked *


Léon

Léon

Duplicate with Q66

jean

jean

The ADDM analysis is performed every time an AWR snapshot is taken.

The MMON process triggers the ADDM analysis each time a snapshot is taken to do analysis of the period corresponding to last two snapshots. This approach proactively monitors the database and detects bottlenecks before they become significant problem . It is also possible to invoke ADDM manually along with the areas that have problem identified. ADDM also reports areas of the system that have no problem.s This allows you to quickly see that there is little to be gained by performing actions in hose areas.

The Automatic Database Diagnostic Monitor (ADDM) analyzes data in the Automatic Workload Repository (AWR) to identify potential performance bottlenecks. For each of the identified issues, it locates the root cause and provides recommendations for correcting the problem. An ADDM analysis task is performed and its findings and recommendations stored in the database every time an AWR snapshot is taken provided the statistics_level parameter is set to TYPICAL or ALL.

The goal of the analysis is to reduce a single throughput metric called DB time. DB time is the cumulative time spent by the database server in processing user requests. It includes wait time and CPU time of all non-idle user sessions. DB time is displayed in the V$SESS_TIME_MODEL and V$SYS_TIME_MODEL views.