Oracle alerts

Oracle Alerts shows alerts for one monitored Oracle server. Use it for focused Oracle instance triage.

> Community Edition: If this Oracle server is monitored by a Community Edition engine, selecting Alerts shows an explanation instead of this alert-management page. Connect it through a trial or licensed engine to enable alert evaluation, history, configuration, and notifications. Licensed-engine servers remain fully enabled in mixed-engine Consoles. See Alert availability.

Workflow

1. Open Alerts under the Oracle server.
2. Review severity, message, and time.
3. Open the related Oracle monitoring page for supporting evidence.
4. Use Configure and Copy Config to edit or copy alert policy.
5. Use global Alerts for estate-wide alert review.

How to use Oracle alerts

Oracle Alerts are useful when you want to focus on one Oracle server rather than the full estate. Start with high-severity alerts and alerts that are new, repeating, or tied to a known incident window. Then open the linked monitoring page to verify the evidence behind the alert.

Do not treat alerts as standalone proof of root cause. An alert can show that a threshold was crossed, but Oracle Activity, Oracle Queries, Oracle Waits, and Oracle Health Checks help explain why it happened. If several alerts fire at the same time, identify the earliest meaningful signal and the business service affected.

For operational follow-up, record the alert time, severity, affected database, owner, and action taken. This makes alert review useful for service reporting and reduces repeat investigations.

Use Copy, Export, And Import Alert Configuration when Oracle servers should share alert thresholds, notification settings, and custom alert behavior. Review recipient routing and Oracle-specific thresholds before copying between production, test, and customer estates.

Oracle alert FAQ

Why do I see Oracle alerts in two places?

This page focuses on one Oracle server. The global Alerts page is better for estate-wide triage.

Should I acknowledge every alert?

Follow your team's process. At minimum, high-severity and repeating alerts should have an owner and outcome.

What if an alert has no obvious cause?

Check the related monitoring pages and the time window around the alert. If evidence is still unclear, review collection permissions and thresholds.

Next steps after an Oracle alert

After selecting an Oracle alert, confirm whether the condition is current, repeating, or historical. Then open the relevant Oracle page to gather supporting evidence. Performance alerts usually need Activity, Queries, and Waits. Operational alerts may need Health Checks, Memory, or database inventory. Record the owner and outcome for repeating alerts.

Alert type reference

The following Mini DBA Oracle alert detail pages explain why each alert is useful, when to enable it, how to tune thresholds, and what remediation steps to take when the alert is active. Custom Alert is included because each server Alerts page can also hold user-defined query alerts.

Related pages

• Alerts
• Copy, Export, And Import Alert Configuration
• Oracle activity
• Oracle health checks