1Z0-062 · Question #288
The performance of your database degrades between 11:00 AM and 3:00 PM. Automatic Workload Repository (AWR) snapshots are collected on an hourly basis. What is the most efficient way of diagnosing…
The correct answer is A. Create a custom ADDM task for the period defined by the snapshots taken between 11:00 AM and 3:00. To diagnose a specific performance degradation window efficiently, the best approach is to create a custom ADDM task targeting the AWR snapshots collected during that precise problematic period.
Question
The performance of your database degrades between 11:00 AM and 3:00 PM. Automatic Workload Repository (AWR) snapshots are collected on an hourly basis. What is the most efficient way of diagnosing this problem?
Options
- ACreate a custom ADDM task for the period defined by the snapshots taken between 11:00 AM and 3:00
- BAnalyze the latest Automatic Database Diagnostic Monitor (ADDM) report.
- CAnalyze the hourly ADDM reports generated between 11:00 AM and 3:00 PM.
- DCreate a SQL Tuning Set (STS) for the currently cached SQL statements in the shared pool and run
How the community answered
(34 responses)- A74% (25)
- B18% (6)
- C3% (1)
- D6% (2)
Why each option
To diagnose a specific performance degradation window efficiently, the best approach is to create a custom ADDM task targeting the AWR snapshots collected during that precise problematic period.
Creating a custom ADDM task allows you to specify a particular time range, defined by start and end AWR snapshots, for analysis. This is the most efficient way to diagnose a performance problem that occurs consistently within a specific time window, providing a focused report on that period.
Analyzing only the latest ADDM report would not necessarily focus on the specific problem period of 11:00 AM to 3:00 PM and might miss the underlying cause.
Concept tested: Custom ADDM analysis for specific periods
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/tgsql/using-automatic-database-diagnostic-monitor.html#GUID-6F27663F-0309-4C51-B245-A7B8E5F690B4
Topics
Community Discussion
No community discussion yet for this question.