RMAN Exits With Error Code AE53034 RMAN-06059

Symptom

The Error AE53034 RMAN-06059: Expected archived log not found, lost of archived log compromises recoverability error occurs:

if you are using Oracle 9i, Oracle 10g and Oracle 11g, in RAC environment, you use a local disk instead of shared disk to put archived logs or you do not use multiple archived logs destination and network mapping to make each machine access the archived logs on all other machines.
if you are using Oracle 11g, in RAC environment, you use shared disk to put archived logs, if FLASH_RECOVERY_AREA exceed the maximal size limit, the newly generated archived logs will be put into standby_archive_dest which is on the local disk.
if you are using Oracle 9i, Oracle 10g and Oracle 11g, in OFS environment, you use local disk, instead of shared disk to put archived logs or you do not use multiple archived logs destination and network mapping to make each machine access the achieved logs on all other machines or you have performed a failover.
if you are using Oracle 11g, in OFS environment, you use a shared disk to put the archived logs, if FLASH_RECOVERY_AREA exceed the maximal size limit, the newly generated archived logs will be put into standby_archive_dest which is on the local disk. This error still appears even after performing a failover.
if you delete the expected archived log files on the disk.

Solution

You can perform the following steps to resolve this error in RMAN Mode:

Ensure you put the archived logs on a shared disk or use multiple archived logs destination and network mapping to ensure that each machine can access the achieved logs on all other machines.
Perform the following steps:

To resolve Error AE53034 RMAN-06059 in RMAN Mode

Logon the machine which has Oracle Agent installed.
Open RMAN console.
Execute the following command:
```
crosscheck archivelog all
```
Then execute the following command:
```
delete expired archivelog all.
```
Note: The command delete expired archivelog all will delete the archivelog record information in the control file and catalog database. Contact your Oracle DBA before you execute these commands.

More information: