1Z0-052 · Question #103
View the Exhibit to examine the output of the DBA_OUTSTANDING_ALERTS view. After 30 minutes, you executed the following command: SQL> SELECT reason,metric_value FROM dba_outstanding_alerts; REASON…
The correct answer is C. The threshold alerts conditions are cleared and the alerts are transferred to BA_ALERT_HISTORY. Rows disappear from DBA_OUTSTANDING_ALERTS when their underlying threshold condition is resolved, at which point Oracle moves those alert records to DBA_ALERT_HISTORY.
Question
View the Exhibit to examine the output of the DBA_OUTSTANDING_ALERTS view. After 30 minutes, you executed the following command:
SQL> SELECT reason,metric_value FROM dba_outstanding_alerts; REASON METRIC_VALUE ----------------------------------------------- ---------------- Tablespace [TEST] is [28 perce 28.125 nt] full 28.125 What could be the reason for the elimination of the other rows in the output?
Exhibit
Options
- AAn Automatic Workload Repository snapshot has been taken recently.
- BThe non-threshold-based alerts are transferred to DBA_ALERT_HISTORY.
- CThe threshold alerts conditions are cleared and the alerts are transferred to BA_ALERT_HISTORY.
- DThe threshold alerts related to database metrics are permanently stored in DBA_ALERT_HISTORY
How the community answered
(17 responses)- A6% (1)
- B6% (1)
- C76% (13)
- D12% (2)
Why each option
Rows disappear from DBA_OUTSTANDING_ALERTS when their underlying threshold condition is resolved, at which point Oracle moves those alert records to DBA_ALERT_HISTORY.
AWR snapshots collect performance statistics but have no effect on the alert mechanism or on the contents of DBA_OUTSTANDING_ALERTS.
Non-threshold-based (stateful) alerts such as 'DB_OPEN_MODE' alerts are transferred to DBA_ALERT_HISTORY when cleared, but the rows that disappeared were threshold-based metric alerts, not non-threshold alerts.
DBA_OUTSTANDING_ALERTS contains only active, unresolved threshold violations; when the metric value drops back below the configured warning or critical threshold, Oracle automatically clears the alert and transfers the record to DBA_ALERT_HISTORY, which is why the other rows vanished after 30 minutes.
Threshold alerts are not permanently stored in DBA_ALERT_HISTORY; they are moved there only when resolved, and DBA_ALERT_HISTORY itself is purged over time by the DBMS_SERVER_ALERT package defaults.
Concept tested: Oracle server alert lifecycle and DBA_OUTSTANDING_ALERTS view
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/DBA_OUTSTANDING_ALERTS.html
Topics
Community Discussion
No community discussion yet for this question.