In which three situations can you use threshold server-generated alerts to help diagnose and fix problems?

Question

Options

• Awhen free space in a dictionary managed tablespace falls below a specified percentage
• Bwhen free space in a locally managed tablespace falls below a specified percentage
• Cwhen the total number of locked user account exceeds a specific value
• Dwhen the number of logons per second exceeds a specific value
• Ewhen a resumable statement is suspended
• Fwhen the total number of logons exceeds a specific value

• A
  90% (18)
• C
  5% (1)
• E
  5% (1)

Explanation

Oracle's threshold server-generated alerts (managed via the DBMS_SERVER_ALERT package and monitored by the MMON background process) fire when a tracked metric crosses a configured threshold value. Tablespace space utilization - both dictionary-managed (A) and locally managed (B) - are the primary and most common use case, triggering a warning or critical alert when free space drops below a set percentage. Total logons (F) is a cumulative statistic Oracle tracks as a threshold metric, making it a valid candidate for this alert mechanism.

Why the distractors are wrong:

• C (locked user accounts): Account-locking state is not exposed as a threshold metric; it's monitored via DBA_USERS or auditing, not server-generated alerts.
• D (logons per second): This is a rate-based derived metric, whereas Oracle's threshold alert system operates on absolute/cumulative statistics like total logon count (F) - not per-second rates.
• E (resumable statement suspended): Resumable space allocation uses a dedicated event-based mechanism (AFTER SUSPEND system event / DBMS_RESUMABLE), which is separate from the threshold alerting framework.

Memory tip: Think "S-T-A" - threshold alerts cover Space (tablespaces A & B) and Total Accumulated statistics (total logons F). Anything rate-based, event-based, or state-based (locked accounts) falls outside this framework.

No community discussion yet for this question.