Duplicating by RMAN

Question

Hi,
when duplicating by RMAN with this script :
run {
allocate auxiliary channel ch1 type disk;
duplicate target database to w3k8b;
exites with following errors :
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 1452 scn 252730 found to restore
I have found this :
RMAN-06053 unable to perform media recovery because of missing log
Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.
Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.
I prefer :
If not, then a point in time recovery up to the missing log is the only alternative.
But I do not know how ?
Thanks for help.
Message was edited by:
user522961

Answer 1

When you say "same error" do you refer to the one previously posted:
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover(4)
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 1452 scn 252730 found to restore
I have found this :
RMAN-06053 unable to perform media recovery because of missing logIt is because rman is trying to locate a missing log. You attempt to perform a complete recover and rman just goes ahead.
You can verify the latest archivelog from the source database by issuing:
SQL>
  1  select max(sequence#), max(to_char(first_time,'RRMMDD:HH24MI')) TIMESTAMP
  2* FROM V$ARCHIVED_LOG
SQL> /
MAX(SEQUENCE#) TIMESTAMP
         30957 070627:0027If you issue:
ALTER SYSTEM ARCHIVE LOG CURRENT;From the source database and ensure you have transfered all archivelog files, up to this last one generated to the auxiliary (clone) database. And issue:
recover database until logseq 30958 thread 1;This will perform the incomplete recover on the auxiliary database with the logsequence defined as the recovery goal.
Once the process is finished you must open your database with resetlogs and make sure, as a post-clone procedure to add the temporary datafiles as required, since rman doesn't backup nor restores temporary datafiles.
~ Madrid