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

Question

Options

• AIt requires the database to be open.
• BIt analyzes the performance of specified objects.
• CIt implements all recommendations automatically.
• DIt recommends solutions and quantifies expected benefits.
• EIt retains snapshots in the SYSAUX tablespace until the database is restarted.
• FIt analyzes the snapshots stored in the Automatic Workload Repository (AWR).

• A
  74% (40)
• B
  6% (3)
• C
  17% (9)
• E
  4% (2)

Explanation

https://docs.oracle.com/database/121/TGDBA/pfgrf_diag.htm#TGDBA94240 With Oracle Database, the statistical data needed for accurate diagnosis of a problem is stored in Automatic Workload Repository (AWR). Automatic Database Diagnostic Monitor (ADDM): - Analyzes AWR data on a regular basis - Diagnoses the root causes of performance problems - Provides recommendations for correcting any problems - Identifies non-problem areas of the system Because AWR is a repository of historical performance data, ADDM can analyze performance issues after the event, often saving time and resources in reproducing a problem. ADDM provides the following benefits: - Automatic performance diagnostic report every hour by default - Problem diagnosis based on decades of tuning expertise - Time-based quantification of problem impacts and recommendation - Identification of root cause, not symptoms - Recommendations for treating the root causes of problems - Identification of non-problem areas of the system - Minimal overhead to the system during the diagnostic process An ADDM analysis can be performed on a pair of AWR snapshots and a set of instances from the same database. The pair of AWR snapshots defines the time period for analysis, and the set of instances define the target for analysis. For RAC, ADDM has three analysis modes: - Database - In Database mode, ADDM analyzes all instances of the - Instance - In Instance mode, ADDM analyzes a particular instance of - Partial - In Partial mode, ADDM analyzes a subset of all database For Non-RAC, ADDM can only function in Instance mode because only one instance of the database exists. An ADDM analysis is performed each time an AWR snapshot is taken and the results are saved in the database. The time period analyzed by ADDM is defined by the last two snapshots (the last hour by default). The types of problems that ADDM considers include the following: - CPU bottlenecks - Is the system CPU bound by Oracle Database or some other application? - Undersized Memory Structures - Are the Oracle Database memory structures, such as the SGA, PGA, and buffer cache, adequately sized? - I/O capacity issues - Is the I/O subsystem performing as expected? - High-load SQL statements - Are there any SQL statements which are consuming excessive system resources? - High-load PL/SQL execution and compilation, and high-load Java usage - Oracle RAC specific issues - What are the global cache hot blocks and objects; are there any interconnect latency issues? - Sub-optimal use of Oracle Database by the application - Are there problems with poor connection management, excessive parsing, or application level lock contention? - Database configuration issues - Is there evidence of incorrect sizing of log files, archiving issues, excessive checkpoints, or sub-optimal parameter settings? - Concurrency issues - Are there buffer busy problems? - Hot objects and top SQL for various problem areas ADDM Recommendations In addition to diagnosing performance problems, ADDM recommends possible solutions. When appropriate, ADDM recommends multiple solutions from which you can choose. ADDM recommendations include the following: - Hardware changes - Adding CPUs or changing the I/O subsystem configuration - Database configuration - Changing initialization parameter settings - Schema changes - Hash partitioning a table or index, or using automatic segment space management (ASSM) - Application changes - Using the cache option for sequences or using bind variables - Using other advisors - Running SQL Tuning Advisor on high-load SQL statements or running the Segment Advisor on hot objects

No community discussion yet for this question.