Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
SYMPTOMS
Alert log showing a regular occurrence of the following error:
Non critical error ORA-48113 caught while writing to trace file "/u01/oracle/diag/rdbms/prddb/prddb5/trace/prddb5_lmon_24925.trc"
ORA-48113: unable to write to stream file because of out of space condition
CHANGES
Either:
SQL_TRACE is set to true either on system level or sesions level
-- OR --
DBMS_MONITOR and DBMS_SESSION packages, which do the same like SQL_TRACE, are used by Applicaiton development
CAUSE
Out of space on the location of the trace files , e.g. "/orav_dump/diag/rdbms/hmbmesv1/HMBMESV1/trace/xxxxxxxxx"
The system is unable to write the requested number of bytes to a stream file. This is due to an out of space condition. The additional information shows how many bytes were not written.
SOLUTION
The message is an informative one and indicates that Oracle failed to write to trace files due to out of space. Please find below the explanation from the manual:
The action that should be done are:
Make sure that there is enough space on the location of the trace files, e.g. /u01/oracle/diag/rdbms/prddb/prddb5/trace/
-- OR --
Check with your development team to see if they are enabling sql_trace on session level or if they are using DBMS_MONITOR and DBMS_SESSION packages which have the same behavior as sql_trace.