Re: RMAN Duplication for Migration and Archived Logs

So, could I then:

1. Initiate the DUPLICATE FOR STANDBY at say 12:00 Noon on Saturday,
and let it process whatever backups and archived logs are available.
2. As more archived logs are backed up throughout the day and those
backup pieces rsynced, apply them manually.
3. At 10 PM (when the downtime window starts), "flip the switch" to
make the standby our live production database.

Do you know off-hand where I would need to do the recompile for the
word-size change?

I've just found the standby documention (Appendix F in the Data Guard
guide [1]), so I'll start reading up on that now.

[1] 
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377

On 8/1/07, Alex Gorbachev <ag@xxxxxxxxxxxx> wrote:
> We use DUPLICATE FOR STANDBY all the time.
> Works like a charm (don't forget to create standby controlfile with RMAN 
> first).
> Basically, DUPLICATE FOR STANDBY does the same and normal DUPLICATE
> but doesn't open database at the end and also restores standby
> controlfile instead of normal one.
>
> On 8/1/07, Don Seiler <don@xxxxxxxxx> wrote:
> > Alex, thanks for the tip.  I was going to ask about the possiblity of
> > creating the new production box as a standby first.  Can RMAN be used
> > to set up the new standby DB?  I haven't done anything in the standby
> > arena yet.  I'll look into the "duplicate for standby" command set.
>
>
> --
> Alex Gorbachev, Oracle DBA Brewer, The Pythian Group
> http://www.pythian.com/blogs/author/alex http://www.oracloid.com
> BAAG party - www.BattleAgainstAnyGuess.com
>


-- 
Don Seiler
oracle: http://ora.seiler.us
ultimate: http://www.mufc.us
--
http://www.freelists.org/webpage/oracle-l

Other related posts: