Error :
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reachedORA-609 : opiodr aborting process unknown ospid (4397_47562687353296)ORA-609 : opiodr aborting process unknown ospid (28545_47989084123600)ORA-609 : opiodr aborting process unknown ospid (4703_47579510747600)Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/product/dbhome/diag/rdbms/orcl/ORCL/trace/ORCL_dbrm_15032.trc"Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached
Solution :
ALTER SYSTEM SET max_dump_file_size=sizek/m;
- The parameter
MAX_DUMP_FILE_SIZE
defines the maximum size of trace files, excluding the alert log. Adjust this limit if you are concerned about excessive disk space usage by trace files. A numerical value for
MAX_DUMP_FILE_SIZE
represents the maximum size in operating system blocks, whereas a number followed by the suffix 'K' or 'M' specifies the size in kilobytes or megabytes.The special value
UNLIMITED
removes any upper limit on trace file size, allowing dump files to grow as large as the operating system permits.
Comments
Post a Comment