archivelog stuatus is X RMAN-06059

admin

[size=130%]RMAN-06059 DURING RMAN BACKUP OF ARCHIVELOG (Doc ID 415978.1)
CauseRMAN is attempting to backup this archivelog file but is not able to access the physical file on disk, because either the archivelog file is manually moved or deleted at the operating system level, and RMAN metadata is not updated.
SolutionThe steps required depends on if the archivelog file exists based on the name and location returned by the error.  Thus the first step is to check for the existence of the archivelog file.
1.  If the archivelog files have been moved to a different directory, then they can be moved back to their original directory.
Otherwise, starting in Oracle9i, you can make RMAN aware of their new location using the following RMAN "catalog" command for each archivelog:

RMAN> catalog archivelog '/temp/archive/zkpd/arch_1_44543_466886099.arc';

Starting in Oracle10g, if several archivelog files are effected, you may issue the RMAN command "catalog start with" as follows:

RMAN> catalog start with '<new_directory_of_archivelogs>';
2.  If the archivelogs are no longer physically available, then you can issue the RMAN command "crosscheck copy of archivelog all".  This command checks for the physical existence of the archivelog file and will change the V$ARCHIVED_LOG.STATUS of the affected archivelog from "A" for AVAILABLE to "X" for EXPIRED.   Once the archivelog file has a status of X, RMAN will no longer attempt to backup this archivelog file.
RMAN> crosscheck copy of archivelog all;
Expired logs that are no longer physically available should be removed from the RMAN repository:
RMAN>delete expired archivelog all;
IMPORTANT NOTE: If there is no RMAN backup of the missing archivelog file, it is essential to perform a full-database backup. Otherwise, you may not be able to recover the database beyond missing log sequence number.