This content has been marked as final. Show 3 replies
You may not have an issue, this is a common error.
An 06054 can be thown after the lastest archivelog is applied because the oracle will try to request an archive log that does not exist.
You should check this first.
Here's a test I did last summer :
Notice the same error at the end. In this case it is expected since the next archive log does not exist.
Find the scn from current and active redolog files of your source. Try the scn which is missing in recover command with the scn from c/a redolog files. But you should how to get the scn from current/active redolog file at OS level.
In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
Edited by: user11989003 on May 29, 2013 10:17 AM