Re: DataGuard Standby Database usage

It won't help you on 10g, but this is exactly what the new snapshot standby features in 11g are for. On 10g and before, the only effective (which is still pretty rare) approach I've seen is to use storage snapshots to take a (cold) snapshot of the standby database before activating it. When the testing is done, the activated standby is dumped and replaced with the snapshot copy made prior to activation.

YMMV, not all environments have storage snapshot capabilites. You can obviously make a backup of the standby prior to activation, but that requires disk space and time as well.

Dan

Howard Latham wrote:
We have the same problem our standby takes abour 12 hours to build and when opened for a test thats it - its not a standby any more
so sucessful test then destroy it to build another untested one. Flashback standby anyone?

 
 
2008/5/30 Joerg Jost <joerg.jost@xxxxxxxxxxxx>:
Am Freitag, den 30.05.2008, 06:51 -0400 schrieb Terrian, Thomas J Mr CTR
DLA J6DIB:
> Oracle 10g, HPUX, Physical DataGuard, RMAN backups of Primary and
> Standby.
>
> What would be the best way to test our DataGuarded copy if we want to
> start it up and applying changes to it?  We don't want those changes to
> come back to the primary.
>
> Can we start it up as a regular database but then when we are done use
> our RMAN backup of it to restore it to the point were it was still a
> standby database?  Will the primary database have any problems with
> this?
>
> Anyone done anything like this before?

Hi Tom,

if we open a standby database for writing, we build afterwards a
complete new standby database. Using rman we can do it anytime, even
during working hours, so we don't try anything spezial.

hth

Jörg



--
Howard A. Latham
-- http://www.freelists.org/webpage/oracle-l

Other related posts: