RMAN-03002, RMAN-06059, ORA-19625 and ORA-27037 When Running RMAN Backup of Archivelogs, rman-03002rman

RMAN-03002, RMAN-06059, ORA-19625 and ORA-27037 When Running RMAN Backup of Archivelogs, rman-03002rman

When RMAN backs up the database, the following error message is displayed:

Starting backup at 25-MAY-15

Current log archived

Allocated channel: ORA_DISK_1

Channel ORA_DISK_1: sid = 953 devtype = DISK

RMAN-00571: ========================================================== ==============================

RMAN-00569: ==================== error message stack follows ==========================

RMAN-00571: ========================================================== ==============================

RMAN-03002: failure of backup plus archivelog command at 05/25/2015 02:00:03

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

ORA-19625: error identifying file/u04/backup/archive/arch_1_40337_867612567.dbf

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

Verification found that the/u04/backup/archive/arch_201740337_867612567.dbf archiving log file does not exist. Because of this new server, it was just restored using RMAN cold backup. The old archived logs are not copied. The RMAN backup adopts the Nocatalog method, that is, the control file is used as the catalog, and the archive log file information is contained in the control file. During RMAN backup, these archive logs are backed up, these old archive logs do not exist, so this error occurs. You can run the following command to solve the problem:

1: RMAN> crosscheck archivelog all; -- check the difference between the control file and the actual physical file. If some archived logs have been deleted or lost, set them to expired

2: RMAN> delete expired archivelog all; -- synchronize Control File Information and actual physical file information (it will delete expired archivelog and updates your controlfile)

This error also occurs when you manually delete the archived logs or move the archived logs. You need to manually execute the crosscheck process before the RMAN backup can proceed normally.