OracleDiagnostics

Where the alert log and trace files are

The ADR home, alert log directory, trace directory and this session's own trace file.

Not yet verified. How scripts are tested

1CLEAR COLUMNS2SET LINESIZE 160 PAGESIZE 100 TRIMOUT ON TAB OFF3COLUMN name  FORMAT A204COLUMN value FORMAT A1205 6SELECT name, value7FROM v$diag_info8WHERE name IN ('ADR Home', 'Diag Alert', 'Diag Trace', 'Default Trace File');

Save it as ora-diag-dirs.sql and run it with SQL> @ora-diag-dirs.

Open in denrepo

Helps with

• ORA-00060: deadlock detected while waiting for resource
• ORA-00600: internal error code, arguments: [%s], [%s], ...
• ORA-01034: ORACLE not available

More Oracle scripts: Diagnostics

• Alert log errors in the last 24 hoursORA- and TNS- errors plus checkpoint warnings from the alert log, read through SQL. It can be slow when the alert log is very large.
• Trace another session with waits and bindsPrompts for a SID and serial number, turns on extended SQL trace, and shows the trace file name. Run the disable line when you've captured enough,…
• Review problems and incidents (ADRCI)ADRCI commands for critical errors like ORA-00600 and ORA-07445, and for packaging an incident to send to Oracle Support.