In this Document
Applies to:Oracle Server - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
***Checked for relevance on 24-May-2012***
RMAN backups are failing with the below error :
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of backup plus archivelog command at 04/10/2008 16:18:43
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/10/2008 16:18:24
ORA-19571: archived-log recid 85 stamp 650564644 not found in control file
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/10/2008 16:18:19
ORA-19571: archived-log recid 63 stamp 650478279 not found in control file
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/10/2008 16:17:35
ORA-19571: archived-log recid 58 stamp 650396427 not found in control file
It seems that the Controlfiles records are over-written.
You need to catalog the archivelogs to make the backup run without errors.
Find the archivelog location and catalog the archivelogs using the below command :
For example if the archivelogs are stored in '/disk1/archive' then you need to do the below :
RMAN> catalog start with '/disk1/archive';
The above commands works in 10g but in previous releases of oracle we need to catalog the archivelog as below :-
catalog archivelog '/gsdprd01/oraarch01/ahdp/arch/ahdp_arch_19328.arc';
catalog archivelog '/gsdprd01/oraarch01/ahdp/arch/ahdp_arch_19329.arc';
catalog archivelog '/gsdprd01/oraarch01/ahdp/arch/ahdp_arch_19333.arc';
Perform. the below steps so that you will not hit this error again in future :
+ Increase the value of CONTROL_FILE_RECORD_KEEP_TIME or use recovery catalog
SQL> alter system set control_file_record_keep_time=14;
+ The backup and the deletion of the archive logs should be done only by RMAN
+ The archiving should be set to AUTO.
+ Always use a catalog database so that you will have the information in catalog even if the information is aged out from controlfile.