Examine the query and its output:
SQL> SELECT REASON, metric_value FROM dba_outstanding_alerts;
REASONMETRIC_VALUE
———————————– ——————-Tablespace [TEST] is [28 perce 28.125
nt] full
Metrics “Current Logons Count”29
Metrics “Database Time Spent99.0375405
waiting (%)” is at 99.03754 for
event class “Application”
db_recovery_file_dest_size of97
4294967296 bytes is 97.298 used
and has 116228096 remaining
bytes available.
After 30 minutes, you execute the same query:
SQL> SELECT reason, metric_value FROM dba_outstanding_alerets;
REASONMETRIC_VALUE
—————————— —————Tablespace [TEST] is [28 percs 28.125
nt] full
What might have caused three of the alerts to disappear?
A.
The threshold alerts were cleared and transferred to d0A_alert_history.
B.
An Automatic Workload Repository (AWR) snapshot was taken before the execution of the
second
C.
An Automatic Database Diagnostic Monitor (ADOM) report was generated before the execution
of the second query.
D.
The database instance was restarted before the execution of the second query.
Explanation:
A is correct. Even after a restart the conditions triggering the alert still exist.
It is OK that the following threshold alerts disappeared:
“Current Logons Count”
“Database Time Spent for event class “Application”
db_recovery_file_dest_size ….. remaining bytes available.
The question is why?
I think D is more appropriate…….
No…..A is correct
It is A
Entries from DBA_AUTSTANDING_ALERTS are cleared when the alert condition is cleared. They are then moved to DBA_alert_history
A
I think A is correct
DBA_OUTSTANDING_ALERTS: The DBA_OUTSTANDING_ALERTS means describes the outstanding alerts in the database and contains current database alerts.
DBA_ALERT_HISTORY: The DBA_ALERT_HISTORY means lists a history of alerts that have been cleared and provides a history of nonthreshold alerts.
I think the answer is A.
Even after restart, if the condition which triggered the alert still existed, the alert wouldn’t disappear.
And the table d0A_alert_history should be DBA_ALERT_HISTORY
A
A
I think A is the right answer.
from the OCA/OCP oracle database 12c all in one exam guide Pag. #583
“When stateful alerts are raised, they are visible as rows in the DBA_Outstanding_alerts view. They will remain visible until they are cleared. They are cleared because DBA has fixed the problem or in some case the problem will go away in the natural course of the events. For instance, a tablespace-usage alert would usually require DBA action , whereas an activity-related alert, such as the rate of redo generation, might clear automatically when activity reduce. When an alert is cleared, it is removed from the DBA_Outstanding_alerts view and written to the DBA_ALERT_HISTORY”
The answer D can’t be because, after the instance restart, the db_recovery_file_dest_size alert should be still in the DBA_Outstanding_alerts view.