ORA-48913 caught while writing to trace file, ORA-48913: Writing into trace file failed

By
Advertisement

Error Message:

Non critical error ORA-48913 caught while writing to trace file,
ORA-48913: Writing into trace file failed, file size limit [10485760] reached Writing to the above trace file is disabled for now on...

Log file:

Tue Feb 07 13:05:18 2017
Non critical error ORA-48913 caught while writing to trace file "/u01/oracle/db/12.1.0/admin/DEV_dbacentral/diag/rdbms/dev/DEV/trace/DEV_ora_18128.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached
Writing to the above trace file is disabled for now on...

Solution:

Here,
File size limit = (MAX_DUMP_FILE_SIZE ) * (OS block size)
You can find the MAX_DUMP_FILE_SIZE and OS block size by using below queries.

If the file size limit reached to (MAX_DUMP_FILE_SIZE) * (OS block size) then the solution is to increase MAX_DUMP_FILE_SIZE to specific or unlimited.
Here,
5M = 5 megabytes each trace file, but could be any value or unlimited.
BOTH = Make the change at memory and spfile level at same time.
SID='*' = Because the change must be done in all instances.
You don't need to bounce the instances if you are using an spfile. If not, you can make the change at memory level by using SCOPE=MEMORY parameter.

0 comments:

Post a Comment