又见oracle bug:rman备份的alert错误提示，现象：在执行数据库备份时，alert日志提示存在错误信息，并给出了一个详细错误信息的t
又见oracle bug:rman备份的alert错误提示
现象：
在执行数据库备份时，alert日志提示存在错误信息，并给出了一个详细错误信息的trc文件。
推荐阅读：
rman 配置归档日志删除策略
oracle基础教程之通过rman复制数据库
rman备份策略制定参考内容
rman备份学习笔记
oracle数据库备份加密 rman加密
alert.log
tue may 7 10:23:19 2013
errors in file /opt/oracle/admin/mms/udump/mms_ora_9140.trc:
tue may 7 10:23:19 2013
errors in file /opt/oracle/admin/mms/udump/mms_ora_9140.trc:
tue may 7 10:23:19 2013
errors in file /opt/oracle/admin/mms/udump/mms_ora_9140.trc:
但trc文件没有异常信息：
[oracle@mmsdb admin]$ more /opt/oracle/admin/mms/udump/mms_ora_9140.trc
/opt/oracle/admin/mms/udump/mms_ora_9140.trc
oracle database 10g enterprise edition release 10.2.0.1.0 - 64bit production
with the partitioning, olap and data mining options
oracle_home = /opt/oracle/product/10.2.0/db_1
system name: linux
node name: mmsdbz
release: 2.6.18-194.el5
version: #1 smp tue mar 16 21:52:39 edt 2010
machine: x86_64
instance name: mms
redo thread mounted by this instance: 1
oracle process number: 86
unix process pid: 9140, image: oraclemms@mmsdbz
*** 2013-05-07 10:23:19.906
*** action name:(0000089 started16) 2013-05-07 10:23:19.873
*** module name:(backup full datafile) 2013-05-07 10:23:19.873
*** service name:(mms) 2013-05-07 10:23:19.873
*** session id:(891.56220) 2013-05-07 10:23:19.873
*** action name:(0000093 started111) 2013-05-07 10:23:24.597
[oracle@mmsdb admin]$
分析：
1.确认alert错误提示发生在执行备份时；
mms_ora_9140.trc：
*** module name:(backup full datafile) 2013-05-07 10:23:19.873
2.trc文件是否被截断？
3.是否是oracle本身存在bug。
对于1，，查看了备份脚本和rman日志，确认备份脚本设置正确，无异常rman日志。排除1
对于2，查看了max_dump_file_size参数设置：
sql> show parameter max_dump_file_size
name type value
------------------------------------ -------------------------------- ------------------------------
max_dump_file_size string unlimited 查看操作系统空间也是有的。
对于3，在metalink查找，发现有bug存在。
trace file created when rman issues the controlfile autobackup [id 335731.1]
applied to:
oracle database - enterprise edition - version 10.1.0.2 to 10.2.0.1 [release 10.1 to 10.2] information in this document applies to any platform.
***checked for relevance on 03-apr-2013***
symptoms:
error in alert.log on controlfile autobackup and trace file created with rman backups.
issue verified by alert.log showing error:
errors in file /usr/oracle/product/admin/dbtest/udump/dbtest_ora_8477.trc:
control autobackup written to disk device
handle '/orabackup/backup/prod/c-959859059-20050906-01'
and trace file created with:
/usr/oracle/product/admin/dbtest/udump/dbtest_ora_8477.trc
oracle database 10g enterprise edition release 10.2.0.1.0 - production
with the partitioning, olap and data mining options
oracle_home = /usr/oracle/product/10.2
system name: linux
node name: dbtest
release: 2.6.9-11.elsmp
version: #1 smp fri may 20 18:26:27 edt 2005
machine: i686
instance name: dbtest
redo thread mounted by this instance: 1
oracle process number: 26
unix process pid: 8477, image: oracle@dbtest (tns v1-v3)
*** 2005-09-06 11:22:02.425
*** action name:(0000064 started111) 2005-09-06 11:22:02.403
*** module name:(backup full datafile) 2005-09-06 11:22:02.403
*** service name:(sys$users) 2005-09-06 11:22:02.403
*** session id:(538.56240) 2005-09-06 11:22:02.403
*** 2005-09-06 11:27:00.173
*** action name:(0000670 started111) 2005-09-06 11:27:00.173
*** module name:(backup archivelog) 2005-09-06 11:27:00.173
cause:
bug 4596065. development determined these empty trace files are created upon controlfile autobackup when flash recovery area is enabled.
solution:
to implement the solution, please execute the following steps:
1. ignore the trace files until patch can be applied.
10.2.0.2 patch set - list of bug fixes by problem type [id 358749.1]
解决方法：
忽略该错误提示，或者升级数据库到10.2.0.2及以上。