RMAN Active Cloning fails with RMAN-06054: missing log file

Question

Version Details:
O.S Version     HP-UX B.11.31 U ia64
Oracle DB Version     11.2.0.3.0
     Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Scenario :
Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
Problem:
At the end of the cloning the below errors are reported;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 07:03:43
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 24751 and starting SCN of 89285945274
RMAN Script used for Active cloning:
#!/bin/ksh
. setdb entDBu
start_dt=`date +%Y%m%d_%H%M`
job=`basename $0 ".sh"`
rman  >> ${job}_${start_dt}.log  2>&1 <<eof
set echo on;
connect target sys/@DCC&(_O@entDBp1
connect auxiliary sys/@DCC&(_O@entDBuu
run {
allocate channel prmy1 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database
to entDBu
from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
show all;
exit
eof
end_dt=`date +%Y%m%d_%H%M`
mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
started: ${start_dt}
finish: ${end_dt}
eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.

Answer 1

Sivaprasad S wrote:
Version Details:
O.S Version     HP-UX B.11.31 U ia64
Oracle DB Version     11.2.0.3.0
     Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Scenario :
Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
Problem:
At the end of the cloning the below errors are reported;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 07:03:43
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 24751 and starting SCN of 89285945274RMAN Script used for Active cloning:
#!/bin/ksh
. setdb entDBu
start_dt=`date +%Y%m%d_%H%M`
job=`basename $0 ".sh"`
rman  >> ${job}_${start_dt}.log  2>&1 <<eof
set echo on;
connect target sys/@DCC&(_O@entDBp1
connect auxiliary sys/@DCC&(_O@entDBuu
run {
allocate channel prmy1 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database
to entDBu
from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
show all;
exit
eof
end_dt=`date +%Y%m%d_%H%M`
mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
started: ${start_dt}
finish: ${end_dt}
eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.Where UNTIL clause in your script I didn't saw.
Please try following RMAN script
DUPLICATE TARGET DATABASE FOR STANDBY
  FROM ACTIVE DATABASE
SPFILE
   SET "control_files"="/u01/app/oracle/oradata/stbdbcontrol01.ctl"
   SET "db_name"="prmdb"
   SET "db_unique_name"="stbdb"
   SET "db_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
   SET "log_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
   SET "db_recovery_file_dest"="/u01/app/oracle/fra"
   SET "diagnostic_dest"=/u01/app/oracle"
   SET "audit_file_dest"="/u01/app/oracle/admin/stbdb/adump"
PASSWORD FILE
NOFILENAMECHECK;
{code}
Please change parameters for your environment.
Regards
Mahir M. Quluzade