检查某环境的alert_orcl1.log时，发现有很多的ORA-48913报错，细节如下

Sat Jul 22 19:34:04 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_138010.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Sat Jul 22 20:08:08 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_151573.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Sun Jul 23 20:08:17 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_270006.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Mon Jul 24 20:08:01 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_388027.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Tue Jul 25 20:08:20 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_47733.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Wed Jul 26 20:08:12 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_165947.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Thu Aug 03 20:08:10 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_196174.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Fri Aug 04 20:08:05 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_314448.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...
Sat Aug 05 20:08:11 2023
Non critical error ORA-48913 caught while writing to trace file "/u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_432215.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [50000000] reached
Writing to the above trace file is disabled for now on...

查看其中一个trc文件，发现是有备份引起的问题

[root@db1 trace]#  strings orcl1_dw00_432215.trc|more
Trace file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dw00_432215.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name:    Linux
Node name:    db1
Release:    4.1.12-124.16.4.el6uek.x86_64
Version:    #2 SMP Thu Jun 14 18:55:52 PDT 2018
Machine:    x86_64
Instance name: orcl1
Redo thread mounted by this instance: 1
Oracle process number: 131
Unix process pid: 432215, image: oracle@db1 (DW00)
*** 2023-08-05 20:05:04.951
*** SESSION ID:(433.37713) 2023-08-05 20:05:04.951
*** CLIENT ID:() 2023-08-05 20:05:04.951
*** SERVICE NAME:(SYS$BACKGROUND) 2023-08-05 20:05:04.951
*** MODULE NAME:() 2023-08-05 20:05:04.951
*** ACTION NAME:() 2023-08-05 20:05:04.951
KUPP:20:05:04.950: Current trace/debug flags: 00480300 = 4719360
*** MODULE NAME:(Data Pump Worker) 2023-08-05 20:05:04.952
*** ACTION NAME:(SYS_EXPORT_FULL_01) 2023-08-05 20:05:04.952
KUPW:20:05:04.952: 0: ALTER SESSION ENABLE PARALLEL DML called.
KUPW:20:05:04.952: 0: ALTER SESSION ENABLE PARALLEL DML returned.
KUPC:20:05:05.085: Setting remote flag for this process to FALSE
KUPW:20:05:05.189: 0: KUPP$PROC.WHATS_MY_ID called.
KUPW:20:05:05.189: 1: KUPP$PROC.WHATS_MY_ID returned.
KUPW:20:05:05.191: 1: worker max message number: 1000
KUPW:20:05:05.192: 1: Cluster access disabled - all workers and slaves local
KUPW:20:05:05.193: 1: Original job start time: 23-AUG-05 08:05:03 PM
KUPW:20:05:05.199: 1: Seqno 235 is DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
KUPW:20:05:05.199: 1: Seqno 434 is DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/SECONDARY_TABLE/INDEX/TABLE_DATA
KUPW:20:05:05.199: 1: KUPP$PROC.WHATS_MY_NAME called.
KUPW:20:05:05.199: 1: KUPP$PROC.WHATS_MY_NAME returned. Process name: DW00
KUPW:20:05:05.199: 1: KUPV$FT_INT.GET_INSTANCE_ID called.
KUPW:20:05:05.200: 1: KUPV$FT_INT.GET_INSTANCE_ID returned. Instance name: db1:orcl1
KUPW:20:05:05.201: 1: ALTER SESSION ENABLE RESUMABLE called.
KUPW:20:05:05.202: 1: ALTER SESSION ENABLE RESUMABLE returned.
KUPW:20:05:05.203: 1: KUPF$FILE.INIT called.
KUPW:20:05:05.216: 1: KUPF$FILE.INIT returned.
KUPW:20:05:05.216: 1: KUPF$FILE.GET_MAX_CSWIDTH called.
KUPW:20:05:05.217: 1: KUPF$FILE.GET_MAX_CSWIDTH returned.
KUPW:20:05:05.217: 1: Max character width: 4
KUPW:20:05:05.217: 1: Max clob fetch: 8181
KUPW:20:05:05.217: 1: Max varchar2a size: 8181
KUPW:20:05:05.217: 1: Max varchar2 size: 1990
KUPW:20:05:05.217: 1: In procedure GET_PARAMETERS
KUPW:20:05:05.217: 1: In procedure GET_METADATA_FILTERS
KUPW:20:05:05.218: 1: In procedure GET_METADATA_TRANSFORMS
KUPW:20:05:05.219: 1: In procedure GET_DATA_FILTERS
KUPW:20:05:05.219: 1: In procedure GET_DATA_REMAPS
KUPW:20:05:05.220: 1: In procedure CREATE_MSG
KUPW:20:05:05.220: 1: KUPV$FT.MESSAGE_TEXT called.
KUPW:20:05:05.220: 1: KUPV$FT.MESSAGE_TEXT returned.
KUPW:20:05:05.220: 1: In procedure PRINT_MT_PARAMS
KUPW:20:05:05.220: 1: Master table             : "SYS"."SYS_EXPORT_FULL_01"
KUPW:20:05:05.220: 1: Metadata job mode        : DATABASE_EXPORT
KUPW:20:05:05.220: 1: Debug enable             : TRUE
KUPW:20:05:05.220: 1: Profile enable           : FALSE
KUPW:20:05:05.220: 1: Transportable enable     : FALSE
KUPW:20:05:05.220: 1: Metrics enable           : TRUE
KUPW:20:05:05.220: 1: db version               : 11.2.0.4.0
KUPW:20:05:05.220: 1: job version              : 11.2.0.4.0
KUPW:20:05:05.220: 1: service name             :
KUPW:20:05:05.220: 1: Current Edition          : ORA$BASE
KUPW:20:05:05.220: 1: Job Edition              :
KUPW:20:05:05.220: 1: Abort Step               : 0
KUPW:20:05:05.220: 1: Access Method            : AUTOMATIC
KUPW:20:05:05.220: 1: Data Options             : 0
KUPW:20:05:05.220: 1: Dumper directory         :
KUPW:20:05:05.220: 1: Master only              : FALSE
KUPW:20:05:05.220: 1: Data Only                : FALSE
KUPW:20:05:05.220: 1: Metadata Only            : FALSE

处理办法

1、查看max_dump_file_size的值为50m，确实不够大，调整max_dump_file_size的值到512M

SQL> show parameter max_dump_file_size

NAME                                     TYPE     VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size                         string     50M
SQL> alter system set max_dump_file_size='512m' scope=both;

System altered.

SQL> show parameter max_dump_file_size

NAME                                     TYPE     VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size                         string     512M
-----------------------------------------

2、手动执行expdp备份不再报错，但trc文件有60M。打开备份脚本查看发现备份命令加了METRICS=Y TRACE=480300参数，删除参数后再次备份，trc很小了。

[root@db1 trace]#  du -sh orcl1_dw00_286274.trc
60M    orcl1_dw00_286274.trc