Non critical error ORA-48913 caught while writing to trace file

檢查某客戶資料庫alert警告日誌發現如下錯誤：
Non critical error ORA-48913 caught while writing to trace file "/u01/oracle/jzh/db/tech_st/11.1.0/admin/jzh_dpebsr12/diag/rdbms/jzh/jzh/trace/jzh_ora_9568606_owc.trc"
Error message: ORA-48913: 鍐欏靉璺熻釜鏂囦歡澶辮觸, 杈懼埌浜嗘枃浠跺ぇ灝忛檺鍒?[10485760]
Writing to the above trace file is disabled for now on...
Mon Jan 19 10:40:46 2015
20150119 10:40:46ip:192.168.217.22 WORKGROUP\jzh SQL*Plus want ddl(CREATE)SYSTEM.BDUMPDIR.
Mon Jan 19 10:46:03 2015
20150119 10:46:03 ip:192.168.58.48 VM-48 SYSTEM OraWrapper.exe want logon SYSTEM
Errors in file /u01/oracle/jzh/db/tech_st/11.1.0/admin/jzh/diag/rdbms/jzh/jzh/trace/jzh_ora_1442508.trc:
初步看應該是超過了max dump file引數的限制，trace file達到了10M，而客戶環境MAX_DUMP_FILE_SIZE引數值為2048。

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大小，或者設定成無限制。