A database instance is configured to monitor tablespace usage using server-generated alerts. A "Tablespace Space Usage" warning alert is triggered when usage exceeds 85%. Subsequently, data files are added to the tablespace, reducing usage to 60%. What is the resulting behavior regarding the alert views?

Server-generated alerts for metrics like tablespace usage are "stateful." When the condition that triggered the alert is resolved (i.e., tablespace usage drops below the warning threshold), the database automatically clears the alert. The clearing process involves removing the alert record from the DBAOUTSTANDINGALERTS view, which shows current, active alerts, and moving it to the DBAALERTHISTORY view for historical tracking and auditing purposes. This automated lifecycle ensures that the outstanding alerts view accurately reflects only current problems requiring attention.

B. Cleared alerts are moved to the history view; they do not remain in the outstanding alerts view with a different status.
C. This alert is metric-based and clears automatically when the metric is no longer in the threshold range. It does not require manual acknowledgement via DBMSSERVERALERT.
D. The alert is not deleted entirely. It is archived in DBAALERTHISTORY to maintain a record of past events, which is crucial for system monitoring and analysis.

1. Oracle Database Administrator's Guide, 23c, "Monitoring Operations with Server-Generated Alerts". The section "Viewing Alerts" describes the purpose of DBAOUTSTANDINGALERTS and DBAALERTHISTORY.

2. Oracle Database Reference, 23c, "DBAOUTSTANDINGALERTS". The view description notes that it contains outstanding alerts. Once an alert is cleared, it is moved to DBAALERTHISTORY.