Oracle alert log

Start Here

Manual Home Installation Windows Installation Linux Engine Container Linux Console Container Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Mode Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Performance History Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

The Oracle Alert Log page shows recent significant entries from Oracle diagnostic alert log data. It is designed for triage of ORA errors, background process failures, warnings, and deadlock-related messages without exposing Oracle diagnostic internals as separate tabs.

What the page shows

Distinct alert-log messages from the last 24 hours.
Severity derived from Oracle message level, ORA code, and message text.
ORA code, component, process, and container context where Oracle exposes it.
A deduplicated count so repeated messages appear as one row with the latest time.
A detail panel for the selected row with the full message and problem/location context.

Click a grid row to inspect the selected message. Use Refresh to rebuild the grouped rows from the latest engine snapshot.

AI review

Use the page AI assistant to explain the visible alert-log entries. The assistant receives the grouped alert-log rows, severity, ORA code, component/process, container context, and recurrence counts, then combines that with the current Oracle instance context.

The assistant should be used for triage and next-step planning. Do not treat it as a replacement for Oracle trace-file review, DBA investigation, or your normal change-control process.

Permissions

This page uses V$DIAG_ALERT_EXT. The same view supports Oracle deadlock detection, alert-log health checks, and the Alert Log Errors alert.

The recommended monitoring setup is a common CDB user with:

GRANT CREATE SESSION TO C##MINIDBA_MONITOR CONTAINER = ALL;
GRANT SELECT ANY DICTIONARY TO C##MINIDBA_MONITOR CONTAINER = ALL;

For stricter environments, ask a DBA to grant explicit select access to V$DIAG_ALERT_EXT and the other views shown in the Oracle permissions modal.