Resuming an aborted RMAN database duplication

  • From: "Don Seiler" <don@xxxxxxxxx>
  • To: oracle_l <oracle-l@xxxxxxxxxxxxx>
  • Date: Sun, 15 Apr 2007 18:02:09 -0500

This weekend I was running an RMAN database duplication to migrate our
development instances from 32-bit server with file-based storage to
64-bit server using ASM.  I've done this once already and it went
virtually fine.

However this time we got errors while RMAN was restoring the archived
logs.  I presume that archived logs would be towards the end of the
process, and this was already after 6+ hours.  We believe the error to
be due to a bug in the failover logic in the qlogic drivers, and have
disabled it for now.  Reissuing my command basically started the
process over from scratch.

I'm wondering if there is a method available to have the DUPLICATE
DATABASE or maybe just manually, restore the remaining archived logs
and then move on to recovery and database opening.  It seems silly to
have to do another 6 hour datafile restore.

I could swear that RMAN did know when files didn't need to be restored
and would skip over them.  Perhaps that was for a "restore database"
command.

--
Don Seiler
oracle: http://seilerwerks.blogspot.com
ultimate: http://www.mufc.us
--
//www.freelists.org/webpage/oracle-l


Other related posts: