Oracle RMAN-06059 expected archived log not found, loss of archived log compromises recoverability (4046818)

Oracle RMAN-06059 expected archived log not found, loss of archived log compromises recoverability

When running an RMAN backup the following errors are generated in the Netvault Logs:

Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 RMAN-00571: ===========================================================
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 RMAN-00571: ===========================================================
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 RMAN-03002: failure of backup command at 10/01/2008 19:12:07
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 RMAN-06059: RMAN-06059 expected archived log not found, lost of archived log compromises recoverability.
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 ORA-19625: error identifying file D:\XXX\A1XXXARC00419_0644367819.00...
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 ORA-27041: unable to open file
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 OSD-04002: unable to open file
Information 2008/10/01 18:12:07 72 Data Plugin ORACLE1 O/S-Error: (OS 2) The system cannot find the file specified.

This error can occur when RMAN attempts to backup an archive log file, but cannot find it.
This can happen for a variety of reasons:
- The file has been manually moved or deleted
- The archive log destination has recently been changed
- The file has been compressed

When an archive log crosscheck is performed, RMAN checks each archive log in turn to make sure that it exists on disk. Those that are missing are marked as unavailable. If there are missing archive logs, the crosscheck operation won't bring them back. It will allow you to get past this error and back-up the database.

To resolve this open the RMAN prompt and run:
RMAN catalog=user/password@CATALOG_SID target=user/password@TARGET_SID
RMAN> change archivelog all crosscheck;

If RMAN has been implemented without a catalog then perform the following :
RMAN nocatalog target=user/password@TARGET_SID
RMAN> change archivelog all crosscheck;

You should then be able to successfully backup the database.

Best practice is to allow RMAN to manage the archived redo logs, rather than manual user management.

One way of achieving RMAN management of the archived redo logs is to utilize the following Oracle plugin configuration items:

• Delete Archive Logs After Successful Backup

• Force Additional Log Switch Before Archive Logs Backup

Refer to the Application Plugin Module for Oracle User's Guide of further detail about these backup option.

BakBone SFDC Solution Number: 00004099