oracle error ORA-48913

Sat May 09 15:57:04 2020
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/mdb/mdb/trace/mdb_dbrm_7134.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [20971520] reached
Writing to the above trace file is disabled for now on...

初步看应该是超过了max dump file参数的限制，trace file达到了21M，而客户环境MAX_DUMP_FILE_SIZE参数值为 40960

[oracle@mdb ~]$ du -sh trace/
1.3G trace/

[oracle@mdb ~]$ du -sh trace/*dbrm*
21M trace/mdb_dbrm_7134.trc
1.3M trace/mdb_dbrm_7134.trm

--修改数据库参数

16:02:14 SYS@mdb(mdb)> show parameter MAX_DUMP_FILE_SIZE

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size string 40960

alter system set MAX_DUMP_FILE_SIZE=unlimited scope=both;

16:03:03 SYS@mdb(mdb)> show parameter MAX_DUMP_FILE_SIZE

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size string UNLIMITED
16:05:12 SYS@mdb(mdb)>

扫描二维码关注公众号，回复： 11456763 查看本文章

mos上解释如下：
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 18-Aug-2014***
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

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

--防止磁盘占满（主机的inode），把可以删除的文件进行删除

--删除7天前的trc

find . -name "*.trc" -mtime +7 -exec rm {} \;

find . -name "*.trm" -mtime +7 -exec rm {} \;