PREVIOUS Audit log

NEXT Listener log

Alert log

The alert log captures messages and errors including:

  • All internal errors (ORA-600), block corruption errors (ORA-1578) and deadlock errors (ORA-60)
  • Admin operations, such as CREATE/ALERT/DROP statements, STARTUP, SHUTDOWN and ARCHIVELOG statements
  • Messages and errors relating to the functions of shared server and dispatcher process
  • Errors occurring during the automatic refresh of a materialized view
  • System crashes
Devo is able to differentiate the categories of errors. For example, you will be able to search for all ORA-00600 errors through the trace logs and alert logs.

The table below provides the default location for the log file and the query you can run in case location has changed.

Log format Oracle version Tags Default file location
Plain text 10g/11g/12c (Linux and Windows)


  • For 10g: 

$ORACLE_BASE/admin/$ORACLE_SID/ bdump/alert_$ORACLE_SID.log

  • Query this location by issuing:

show parameter background_dump_dest;

  • For 11g/12c:

$ORACLE_BASE/diag/rdbms/$ORACLE_SID/$ORACLE_SID/ trace/alert_$ORACLE_SID.log

  • Query this location by issuing:

select value from v$diag_info where name = 'Diag Trace';

XML 11g/12c (Linux and Windows)


$ORACLE_BASE/diag/rdbms/$ORACLE_SID/$ORACLE_SID/ alert/log.xml

  • Query this location by issuing:

select value from v$diag_info where name = 'Diag Alert';

  • You can monitor the alert logs in either text format or XML format, depending on what the Oracle Database administrator has configured.
  • As listed in the table above, the text format and XML format alert logs coexist in 11g/12c. You only need to monitor one of them.
  • Note that the alert log in XML format has more information than the one in plain text.
The alert log source types oracle.alert.text and oracle.alert.xml do not map to the Common Information Model.

Have we answered your question?

If not, please contact our technical support team via email by clicking the button below.


PREVIOUS Audit log

NEXT Listener log