on critical error ORA-48113 caught whilewriting to trace metadata file

最新推荐文章于 2025-08-28 18:00:50 发布

原创最新推荐文章于 2025-08-28 18:00:50 发布 · 5.2k 阅读

0 ·

CC 4.0 BY-SA版权

体系专栏收录该内容

13 篇文章

订阅专栏

本文详细介绍了Oracle数据库中遇到的非关键错误ORA-48113的常见原因和解决步骤，包括空间不足导致无法写入跟踪文件的问题及其解决方法。

检查alert发现如下报错

Fri Dec 11 09:26:06 2015

Error message:

Writing to the above trace file is disabledfor now on...

Non critical error ORA-48113 caught whilewriting to trace metadata file (.trm)

Trace file name:"/u01/PROD/db/tech_st/11.2.0/admin/PROD_erpdb/diag/rdbms/prod/PROD1/trace/PROD1_ora_68773.trc"

Error message:

Writing to trace metadata is disabled fornow on...

Fri Dec 11 09:26:20 2015

Non critical error ORA-48113 caught whilewriting to trace metadata file (.trm)

Trace file name:"/u01/PROD/db/tech_st/11.2.0/admin/PROD_erpdb/diag/rdbms/prod/PROD1/trace/PROD1_lmon_24698.trc"

Error message:

Writing to trace metadata is disabled fornow on...

官方解释：

Non Critical Error ORA-48113 Caught While Writing To Trace File (文档 ID 1494817.1)

In this Document

APPLIES TO:

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.