What might have caused three of the alerts to disappear?

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?

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.



Leave a Reply 1

Your email address will not be published. Required fields are marked *