See Oracle BUG: error message about the alert of Rman backup.

See Oracle BUG: error message about the alert of Rman backup.
Symptom:
During database backup, the alert Log prompts an error message and provides a trc file with detailed error information.

Recommended reading:

RMAN: Configure an archive log deletion policy

Basic Oracle tutorial-copying a database through RMAN

Reference for RMAN backup policy formulation

RMAN backup learning notes

Oracle Database Backup encryption RMAN Encryption
 
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:
<<===
 
However, the trc file has no exception information:
[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

* ** 10:23:19. 906
* ** Action name: (0000089 STARTED16) 10:23:19. 873
* ** Module name :( backup full datafile) 10:23:19. 873
* ** Service name: (MMS) 10:23:19. 873
* ** Session id: (891.56220) 10:23:19. 873
* ** Action name: (0000093 STARTED111) 10:23:24. 597
[Oracle @ MMSDB admin] $
 
Analysis:
1. confirm that the alert error message occurs during Backup;
MMS_ora_9140.trc:
* ** Module name :( backup full datafile) 10:23:19. 873
2. Is the trc file truncated?
3. Check whether Oracle has a BUG.
 
For 1, check the backup script and rman log, and confirm that the backup script is set correctly without any abnormal rman log. Exclude 1
For 2, check the max_dump_file_size parameter settings:
SQL> show parameter max_dump_file_size
NAME TYPE VALUE
--------------------------------------------------------------------------------------------------
Max_dump_file_size string UNLIMITED <= No problem
You can also view the operating system space.
For 3, you can find bugs in Metalink.
Trace File Created when RMAN issues the Controlfile Autobackup [ID 335731.1]
 
Applied:
Oracle Database-Enterprise Edition-Version 10.1.0.2 to 10.2.0.1 [Release 10.1 to 10.2] <=== our DB Version is 10.2.0.1
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:
 
/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)
 
* ** 11:22:02. 425
* ** Action name: (0000064 STARTED111) 11:22:02. 403
* ** Module name :( backup full datafile) 11:22:02. 403
* ** Service name :( SYS $ USERS) 11:22:02. 403
* ** Session id: (538.56240) 11:22:02. 403
* ** 11:27:00. 173
* ** Action name: (0000670 STARTED111) 11:27:00. 173
* ** Module name :( backup archivelog) 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] <== no one-off patch, this BUG is fixed in 10.0.2.2
 
Solution:
Ignore the error message or upgrade the database to 10.2.0.2 or later.