Troubleshooting › Warning AW53704: Unable to locate the Archived Log. It will not be backed up. (Archived Log=[archived log file name]).

Warning AW53704: Unable to locate the Archived Log. It will not be backed up. (Archived Log=[archived log file name]).

Symptom:

The Warning AW53704 Unable to locate the Archived Log. It will not be backed up. (Archived Log=[archived log file name]) occurs:

• if you delete the expected archived log files on the disk.
• 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 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 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.

Solution:

You can perform the following steps to resolve this error in the file-based mode:

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

  Note: For more information on network mapping and accessing the archived logs, see Unable to Access Archived Logs in Oracle Cluster Environment and for information on how to perform backup and restore, see Using RMAN command to Backup, Restore, and Recover Archived Logs in the Troubleshooting section of this guide.

• Perform the following steps:

To resolve Warning AW53704 in file-based mode

1. Log into the machine on which the Agent for Oracle Agent is installed.
2. Open the RMAN console.
3. Run the following command

   crosscheck archivelog all
   

4. Then run the 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.