Saturday, April 23, 2016

ORA-48913: Writing into trace file failed, file size limit [10485760] reached Shows In ALERT.LOG

ORA-48913: Writing into trace file failed, file size limit [10485760] reached Shows In ALERT.LOG 

Error:

Non critical error ORA-48913 caught while writing to trace file "/oraotcprd1/app/oracle/diag/rdbms/otcprd1/OTCPRD11/trace/OTCPRD11_ora_14925.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached

Cause:
Parameter MAX_DUMP_FILE_SIZE  is set too low

Solution:
Increase the setting for the parameter MAX_DUMP_FILE_SIZE or set it to unlimited

Note:

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

A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in operating system blocks.

A number followed by a K or M suffix specifies the file size in kilobytes or megabytes.

The special value string UNLIMITED means that there is no upper limit on trace file size. Thus, dump files can be as large as the operating system permits.

Reference metalink Doc ID 1153040.1