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?
A.
Insert finding directives for ADDM tasks in the future.
B.
Create a baseline on a pair of snapshots spanning the peak-load period.
C.
Decrease the snapshot interval in the AWR to collect more snapshots during the peakload
period.
D.
Set the snapshot retention period in the Automatic Workload Repository (AWR) to zero to avoid
automatic purging of snapshots.
Explanation:
Database Maintenance
Proactive database maintenance is made easy by the sophisticated infrastructure of the Oracle
database, including the following main elements:
The Automatic Workload Repository (AWR) is a built-in repository in each Oracle database. At
regular intervals, the Oracle database makes a snapshot of all its vital statistics and workload
information and stores this data in the AWR. The captured data can be analyzed by you, by the
database itself, or by both.
Using automated tasks, the database performs routine maintenance operations such as regular
backups, refreshing optimizer statistics, and database health checks.
Reactive database maintenance includes critical errors and conditions discovered by database
health checkers:
For problems that cannot be resolved automatically and require administrators to be notified
(such as running out of space), the Oracle database provides server-generated alerts. The Oracle
database by default monitors itself and sends out alerts to notify you of problems. The alerts notify
you and often also provide recommendations on how to resolve reported problem.
Recommendations are generated from a number of advisors, each of which is responsible for a
subsystem. For example, there are memory, segment, and SQL advisors.