重庆思庄Oracle、Redhat认证学习论坛

标题: Non critical error ORA-48913 caught while writing to trace file [打印本页]

作者: jiawang 时间: 2019-5-16 11:41
标题: Non critical error ORA-48913 caught while writing to trace file

报错现象：

Mon Mar 25 11:23:39 2019

Non critical errorORA-48913 caught while writing to trace file"D:\APP\SMIT\diag\rdbms\ris\ris\trace\ris_ora_8408_STATION27_USER155.trc"

Error message:ORA-48913: 写入跟踪文件失败, 达到了文件大小限制 [100000000]

Writingto the above trace file is disabled for now on...初步看应该是超过了max dump file参数的限制

mos上解释如下：
APPLIES TO:Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 29-Jan-2016***
SYMPTOMS

On 11.2.0.1, encountered the following error in the alert.log:

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

For additional information on this parameter, refer to

Oracle Database Reference 11g Release 2 (11.2)
MAX_DUMP_FILE_SIZE

REFERENCES

原因是由于MAX_DUMP_FILE_SIZE太小，解决方法是增加MAX_DUMP_FILE_SIZE大小，或者设置成无限制。

作者: 郑全 时间: 2020-5-7 17:36
你原始的这个参数：MAX_DUMP_FILE_SIZE ，原来的值是多大呢

欢迎光临重庆思庄Oracle、Redhat认证学习论坛 (http://bbs.cqsztech.com/)