Database Duplication Fails Missing Log RMAN-06053 RMAN-06025

Error Stuck:
--------------------
While running duplicating database the following error returns.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/13/2008 04:40:56
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 5 lowscn 977621 found to restore

Cause of The problem:
------------------------

The problem is that RMAN is not able to apply all the archived logs needed for complete recovery. For example, if you only backed up logs through sequence 4, but the most recent archived log is sequence 5, then DUPLICATE fails.

Solution of The Problem:
------------------------------
When creating the duplication script, use the SET UNTIL command to specify a log sequence number for incomplete recovery. For example, to terminate recovery after applying log sequence 5, enter:

RUN
{
SET UNTIL SEQUENCE 5 THREAD 1; # recovers up to but not including log 5
DUPLICATE TARGET DATABASE TO DUPBASE NOFILENAMECHECK;
}