RMAN-06055: could not find archived log with sequence

Problem:
Recently I has this issue while performing database cloning for Oracle Database 11gR2. I was cloning database for one of our test EBS environment with the option of RMAN duplicate command.

The RMAN duplicate failed with the below errors as per the log file generated:
RMAN-00571:======================================
RMAN-00569:==== ERROR MESSAGE STACK FOLLOWS ====
RMAN-00571: ======================================
RMAN-03002: failure of Duplicate Db command at 03/07/2014 20:05:38
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06055: could not find archived log with sequence 13624 for thread 1

You can find the complete log file below.
<a href=http://www.filedropper.com/duptrctst0307141040><img src=http://www.filedropper.com/download_button.png width=127 height=145 border=0/></a><br /><div style=font-size:9px;font-family:Arial, Helvetica, sans-serif;width:127px;font-color:#44a854;> <a href=http://www.filedropper.com >upload files free</a></div>

Cause:

• A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.

Action:

• Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support.   

SQL> select THREAD#,SEQUENCE#,applied,status from v$archived_log where sequence#=13623
   THREAD#  SEQUENCE# APPLIED   STATUS
   ----------      ----------           ---------        --------------
         1        13623             NO            D

SQL>  select THREAD#,SEQUENCE#,applied,status from v$archived_log where sequence#=13624;

   THREAD#  SEQUENCE# APPLIED   STATUS
---------- ---------- --------- --------------------
         1      13624 NO        D

Solution:

• Actually there was a cronjob running to backup all archivelogs of the source  database and  after backup is done it removes the extracted archives. After disabling the job everything works fine...
• Use a SET UNTIL clause for the DUPLICATE command. (set to atime / scn / sequence )