If the trace file reached its maximum specified size then we got this error. MAX_DUMP_FILE_SIZE parameter specifies the maximum size of the trace file. If you increase the value of this parameter clears the error.
SQL> show parameter MAX_DUMP_FILE_SIZE
NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
max_dump_file_size string 10M
Check the mount point has the free space to increase the MAX_DUMP_FILE_SIZE parameter. If
it has the enough free space then increase the value.
SQL> alter system set MAX_DUMP_FILE_SIZE ='20m';
System altered.
Even we can set the MAX_DUMP_FILE_SIZE parameter value to 'unlimited'.
SQL> alter system set MAX_DUMP_FILE_SIZE = unlimited;
UNLIMITED means there is no upper limit on trace file size. Thus files can be increase to operating system level limits. But it causes the disk utilization high.
SQL> show parameter MAX_DUMP_FILE_SIZE
NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
max_dump_file_size string 20M
If the mount point in which trace files are located, doesn't have the enough space then you just zip the trace file to subsidize this error (Temporary fix).
No comments:
Post a Comment