1Z0-052 · Question #114
Your database is functional with a peak load for the last one hour. You want to preserve the performance statistics collected during this period to be used for comparison when you analyze the…
The correct answer is B. Create a baseline on a pair of snapshots spanning the peak-load period. To preserve peak-load AWR snapshots for future comparison, you create an AWR baseline that pins the relevant snapshot pair against automatic purge.
Question
Your database is functional with a peak load for the last one hour. You want to preserve the performance statistics collected during this period to be used for comparison when you analyze the performance of the database in the future. What action would you take to achieve this task?
Options
- AInsert finding directives for ADDM tasks in the future.
- BCreate a baseline on a pair of snapshots spanning the peak-load period.
- CDecrease the snapshot interval in the AWR to collect more snapshots during the peakload period.
- DSet the snapshot retention period in the Automatic Workload Repository (AWR) to zero to avoid automatic
How the community answered
(39 responses)- A3% (1)
- B85% (33)
- C8% (3)
- D5% (2)
Why each option
To preserve peak-load AWR snapshots for future comparison, you create an AWR baseline that pins the relevant snapshot pair against automatic purge.
ADDM finding directives influence how future ADDM tasks are analyzed but do not preserve or pin historical snapshot data from a past peak-load window.
An AWR baseline anchors a pair of snapshots covering a specific time window, preventing the Automatic Workload Repository from purging them under the normal retention policy. This lets you reference the baseline in future ADDM analysis and performance comparisons to identify regressions or improvements relative to the peak-load period.
Decreasing the snapshot interval increases granularity for future collection but does not protect already-collected snapshots from being purged when the retention window expires.
Setting the AWR retention period to zero means retain indefinitely in some Oracle versions, but this is a global setting and is not the targeted, recommended mechanism for preserving a specific peak-load period.
Concept tested: AWR baseline creation for performance comparison
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/tgdba/gathering-database-statistics.html
Topics
Community Discussion
No community discussion yet for this question.