Init parameterDiagnostics & licensing

MAX_DUMP_FILE_SIZE

What it controls

The largest trace file a process may write.

Know this before you change it

Cap it instance-wide to protect the disk, and raise it for a session you're tracing.

Default: unlimited

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'max_dump_file_size';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'max_dump_file_size' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET max_dump_file_size = '500M' SCOPE = BOTH SID = '*';11 12-- Or for your own session only13ALTER SESSION SET max_dump_file_size = '500M';14 15-- Remove it from the spfile to go back to the default at the next restart16ALTER SYSTEM RESET max_dump_file_size SCOPE = SPFILE SID = '*';

Related scripts

• 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,…

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.
• DIAGNOSTIC_DESTRoot of the Automatic Diagnostic Repository: alert log, traces and incidents.