RMAN-06053, RMAN-06025

Database Duplication Fails with error: RMAN-06053, RMAN-06025

 

When I try to duplicate database first time using RMAN the duplicate command is failed with following error:

 

RMAN-03002: failure of Duplicate Db command at 07/28/2010 23:11:44

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 12 lowscn 487272 found to restore
 

Cause:

RMAN unable to start archive log restore to default destination. The problem is that rman is not able to apply the entire archive log needed for complete recovery. For example, if you only backed up logs through sequence 15, but the most recent archived log is sequence 16, then DUPLICATE fails.

 

Solution:

When creating the duplication script either, use the SET UNTIL command to specify a log sequence number for incomplete recovery or include NOFILENAMECHECK with the duplicate command. For example, to terminate recovery after applying log sequence 15, enter:

RUN

{

  SET UNTIL SEQUENCE 16 THREAD 1; #recovers up to but not including log 16

  DUPLICATE TARGET DATABASE TO 'dupdb';

}

 

-or- add NOFILENAMECHECK with duplicate database command:

DUPLICATE TARGET DATABASE TO "clone" NOFILENAMECHECK;

 

For Example:

RMAN> DUPLICATE TARGET DATABASE TO "clone";

When NOFILENAMECHECK is used with the DUPLICATE command, RMAN does not validate the filenames during restoration.

 
Note: If the primary database and the standby database are on the same host, The DUPLICATE NOFILENAMECHECK option should not be used.