ORA-48913: Writing into trace file failed, file size limit [50000000] reached

检查某环境的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


 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: ORA-19502是Oracle数据库的一个错误代码,表示在写入文件时发生了错误。这个错误通常是由于磁盘空间不足、文件系统权限不足或磁盘故障等原因引起的。如果遇到这个错误,需要检查磁盘空间、文件系统权限和磁盘状态,以确定问题的根本原因并采取相应的措施来解决它。 ### 回答2: ORA-19502是Oracle数据库的错误代码,表示在写入文件时发生了错误。 这个错误通常是由于以下几个原因之一造成的: 1. 磁盘空间不足:在进行写操作时,数据库需要足够的空间来存储数据。如果磁盘空间不足,就会出现ORA-19502错误。解决方法是释放一些空间或者增加磁盘容量。 2. 磁盘读/写错误:可能出现了硬件故障或者磁盘损坏,导致无法写入文件。在这种情况下,需要修复或更换损坏的硬件,或者修复数据库文件系统。 3. 文件权限问题:数据库文件的权限可能设置不正确,导致无法写入文件。在这种情况下,需要检查文件权限并更正。 4. 写入目录不存在:如果写入目录不存在或者无法访问,就会出现ORA-19502错误。需要确保指定的目录存在并且可读写。 5. 其他软件或进程占用了文件:其他正在运行的软件或进程可能占用了数据库文件,导致无法写入。在这种情况下,需要关闭并释放对文件的占用。 总之,ORA-19502错误是由于在写入文件时发生了错误,可能是由于磁盘空间不足、磁盘读/写错误、文件权限问题、写入目录不存在或者其他软件/进程占用文件等原因。根据具体情况,我们可以采取相应的措施来解决该问题。 ### 回答3: ORA-19502: 写文件错误是Oracle数据库中的一个错误代码,它意味着在数据库备份或恢复操作过程中,Oracle无法将数据写入指定的文件中。 这个错误通常由以下原因引起: 1. 磁盘空间不足:当磁盘空间不足时,Oracle无法将数据写入文件。请确保备份或恢复操作所需的目标文件的磁盘空间足够。 2. 文件权限问题:如果数据库无法在指定的文件上执行写操作,可能是由于文件权限设置不正确导致的。请确保数据库进程具有对目标文件的写权限。 3. 文件系统故障:如果目标文件所在的文件系统出现故障或损坏,Oracle将无法将数据写入文件。请检查文件系统状态,并修复任何故障或损坏的情况。 4. 被占用的文件:如果目标文件正在被其他进程占用或打开,Oracle将无法将数据写入文件。请确保没有其他进程正在使用目标文件,或者将其关闭,然后重试操作。 如果发生ORA-19502错误,您可以通过以下步骤来解决问题: 1. 检查磁盘空间:确保备份或恢复操作所需的目标文件的磁盘空间足够。 2. 检查文件权限:通过检查文件权限设置,确保数据库进程具有对目标文件的写权限。 3. 检查文件系统状态:检查目标文件所在的文件系统是否正常运行,并修复任何故障或损坏。 4. 检查文件占用情况:确保目标文件没有被其他进程占用或打开,或者将其关闭,然后重试操作。 总之,ORA-19502错误意味着Oracle无法将数据写入指定的文件中,可能是由于磁盘空间不足、文件权限问题、文件系统故障或被占用的文件导致的。通过检查和解决这些问题,您可以解决ORA-19502错误。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值