Exam 1z0-083 topic 1 question 8 discussion

typo. correct: BC

Best to start with defining stateful/stateless: A stateful alert is a threshold based alert (ie, tablespace usage above 90%), a stateless alert is non-threshold based alert (ie, a capture aborted with an ORA- error). A stateful alert first appears in DBA_OUTSTANDING_ALERTS. When cleared, it goes to DBA_ALERT_HISTORY. A stateless alert goes straight to DBA_ALERT_HISTORY A stateless alert can be considered as a "point in time" error, the DB tells you about it and then forgets that it ever spoke about it. Therefore, each answer: A: FALSE - the DB creates stateful alerts, not a DBA. B: TRUE - a DBA can perform a purge to bulk remove alerts, perhaps based on date C: TRUE - a DBA can clear individual alerts D: FALSE - Stateless alerts are never checked again, by the DB, so cannot be automatically cleared E: FALSE - Stateful alerts are purged from the "Outstanding Alerts" and put into the alert history, where they will remain. Therefore, BC are correct

A. Stateful alerts must be created by a DBA after resolving the problem. --> False, they are created automatically. B. Stateless alerts can be purged manually from the alert history. --> True C. Stateless alerts can be cleared manually. --> False, *MUST be cleared manually. D. Stateless alerts are automatically cleared. --> False, you can only clear manually. E. Stateful alerts are purged automatically from the alert history. --> True.

B and C are corrects.

BC is write see https://docs.oracle.com/cd/E73210_01/EMADM/GUID-D0428ED9-FCA8-44D6-AB5B-B8FF4139BF0D.htm#EMADM12104 section 2.4.3 Clearing Stateless Alerts for Metric Alert Event Types For metric alert event types, an event (metric alert) is raised based on the metric threshold values. These metric alert events are called stateful alerts. For those metric alert events that are not tied to the state of a monitored system (for example, snapshot too old, or resumable session suspended ), these alerts are called stateless alerts. Because stateless alerts are not cleared automatically, they need to be cleared manually. You can perform a bulk purge of stateless alerts using the clear_stateless_alerts EM CLI verb.

"TO PURGE" IS NOT "TO CLEAR". "Background processes periodically flush the data to the Automatic Workload Repository to capture a history of metric values. The alert history table and ALERT_QUE are purged automatically by the system at regular intervals." https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/monitoring-the-database.html#GUID-3B999A58-21A7-40FB-A36E-2A113A83F2CF

I wonder whether the answer should be BD. As stateless alerts go directly to DBA_ALERT_HISTORY, how can C be correct as you wont be able to find that out for clearing manually. Pls help to correct me if I'm wrong.

Correct: B,C A. False. A stateful alert is a threshold based alert (ie, tablespace usage above 90%),the DB creates stateful alerts, not a DBA. B. True. DBA can perform a purge to bulk remove alerts, perhaps based on date C. True. DBA can clear individual alerts D. False. Stateless alerts are never checked again, by the DB, so cannot be automatically cleared. Only resolved alerts are cleared automatiquely E. False. Stateful alerts are purged from the "Outstanding Alerts"(DBA_OUTSTANDING_ALERTS) and put into the alert history, where they will remain.

see comment from xRodge

Stateful alerts are purged after 24 hours

B and C are correct

BC is correct

It's BC

Correct Ans: BC There are two kinds of server-generated alerts: threshold and nonthreshold. Most server-generated alerts are configured by setting a warning and critical threshold values on database metrics. You can define thresholds for more than 120 metrics, including the following: • Physical Reads Per Sec • User Commits Per Sec • SQL Service Response Time Except for the Tablespace Space Usage metric, which is database related, the other metrics are instance related. Threshold alerts are also referred to as stateful alerts, which are automatically cleared when an alert condition clears. Stateful alerts appear in DBA_OUTSTANDING_ALERTS and, when cleared, go to DBA_ALERT_HISTORY. Other server-generated alerts correspond to specific database events, such as ORA-* errors, “Snapshot too old” errors, Recovery Area Low On Free Space, and Resumable Session Suspended. These are non-threshold-based alerts, also referred to as stateless alerts. Stateless alerts go directly to the History table

B and C

C and E

Correct Ans: B,C Student Guide: Except for the tablespace space usage metric, which is database related, the other metrics are instance related. Threshold alerts are also referred to as stateful alerts which are automatically cleared when an alert condition clears. Stateful alert appears in DBA_OUTSTANDING_ALERTS and when cleared go to DBA_ALERT_HISTORY. Other server-generated alerts correspond to specific database events such as ORA-* errors, "Snapshot too old" errors, Recovery Area Low on Free Space, Resumable Session Suspended. These are non threshold based alerts, also referred to as stateless alerts. Stateless alerts go directly to the History table. +++ Most alerts (such as "Out of Space") are cleared automatically when the cause of the problem disappears. However, other alerts (such as generic alert log errors) are sent to you for notification and must be acknowledged by you. After taking the corrective measures, you acknowledge an alert by clearing or purging it. Clearing an alert sends the alert to the Alert History which is accessible from Monitoring sub menu. Purging an alert removes it from the Alert History.