Skip Headers
Oracle® Database Reference
12c Release 1 (12.1)

E17615-24
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

MAX_DUMP_FILE_SIZE

Property Description
Parameter type String
Syntax MAX_DUMP_FILE_SIZE = { integer [K | M | G] | UNLIMITED }
Default value UNLIMITED
Modifiable ALTER SESSION, ALTER SYSTEM
Range of values 0 to unlimited, or UNLIMITED
Basic No

MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the alert log). Change this limit if you are concerned that trace files may use too much space.

When the trace file is limited in size, it may be automatically split into multiple files, called segments, if needed. The segments will have the same file name as the active trace file, but with an extra segment number appended.

The trace file can be split into a maximum of 5 segments, and the size of each segment will typically be 1/5th of the trace file limit.

When the combined size of all the trace file segments exceeds the specified limit, the oldest segment is deleted, and a new, empty segment is created. Thus, the trace file always contains the most recent trace information.

Note that the first segment is never deleted, because it may contain relevant information about the initial state of the process.

See Also:

Oracle Database Administrator's Guide and Oracle Database SQL Tuning Guide for more information on setting this parameter