Init parameterDiagnostics & licensing

DIAGNOSTIC_DEST

What it controls

Root of the Automatic Diagnostic Repository: alert log, traces and incidents.

Know this before you change it

Put it where there's room, and clean it with ADRCI purge policies.

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'diagnostic_dest';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'diagnostic_dest' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET diagnostic_dest = '/u01/app/oracle' SCOPE = BOTH SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET diagnostic_dest SCOPE = SPFILE SID = '*';

Related scripts

• Where the alert log and trace files areThe ADR home, alert log directory, trace directory and this session's own trace file.
• 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.

Open in the parameter referenceOracle's reference

More in Diagnostics & licensing

• CONTROL_MANAGEMENT_PACK_ACCESSWhich management packs are enabled: the Diagnostics Pack (AWR, ASH, ADDM) and the Tuning Pack.
• MAX_DUMP_FILE_SIZEThe largest trace file a process may write.