Data Guard Rebuild
- From: Kenny Payton <k3nnyp@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 12 Jun 2014 10:44:07 -0400
I create/rebuild standby databases from time to time and when they are large
and going across our WAN they can take more than a day to complete, sometimes
multiple days. These databases also have a high churn rate and generate a
large amount of redo. Our normal backup processes delete the archived logs on
the primary prior to completion of the standby and require restoring them on
the primary after the managed recovery begins so that they can ship to the
standby. We do not reserve enough space to keep multiple days of archived logs
around.
I’m curious if anyone has another work around to this.
I have one that requires creating the shell of the database by restoring the
control files and offline dropping all data files and configuring transport to
ship logs to it. Once managed recover starts I just register the log files
that have shipped so far and switch the transport service on the primary. This
is a little clunky and fairly manual at this point and I would love an easier
approach.
Thanks,
Kenny--
//www.freelists.org/webpage/oracle-l
Other related posts:
