RMAN-06059: expected archived log not found
Hi All,
Many a times when taking the rman backup you can face the following error reported in the rman log as shown below
allocated channel: ch00
channel ch00: sid=110 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 5.0GA (2003103006)
allocated channel: ch01
channel ch01: sid=106 devtype=SBT_TAPE
channel ch01: VERITAS NetBackup for Oracle - Release 5.0GA (2003103006)
Starting backup at 19-SEP-07
current log archived
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/19/2007 21:32:32
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /ExtSD11/oracle/oradata/TMMBFMPR/arch_1_4323.arc
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
RMAN>
Recovery Manager complete.
The above error is mainly due to the specified archivelog could not be found by the rman at the desired location. It can be due to archive log backed up at the OS level and deleted from the location to reclaim some free space Or it may be due accidential deleteion of archive logs.
Hence the ramn backup archive log command will give the above error unless you remove the reference of that archive logs which were deleted at the OS level from the catalog repository of RMAN.
So the solution for above error is make sure the archivelog is avaliable at the desired location. Or try to copy the archive log to that location.
However if the archive log is already backed up you can use the crosscheck command at RMAN prompt so that the missing archive logs will be marked as EXPIRED and then you can delete EXPIRED archivelog reference from the catalog as shown
RMAN> crosscheck archivelog all;
RMAN> delete expired;
Now you can rerun the backup script and the problem must get solved