Re:Help: Standby database config.

A friend of mine suggested me to config our standby database withoutusing managed recovery because of the following reason: If you have corruption or bad data get into the online db you have no way to easily spot and stop that data from automatically migrating into the standby db. If you keep everything the same but only apply the recovery on the failover side every 2 hours or so you then have 2 hours  to catch and stop the recovery. like recover to a point in time just  before the corruption. The way you are doing it now with managed recovery I don't think it buys you much failover capability.

Is this really a good idea?  

>Not in my book. A stand-by database that can't be brought up in a
>minute or two isn't a stand-by database. Exactly what form of
>corruption is your friend thinking is going to occur in the redo logs?
>Daniel A. Morgan

What he means is that if somebody drop a table mistakenly or something. If we just let oracle write all the logfiles to the standby destination, but only apply 2 hour behind of them, when we need to bring up the standby database, we can apply the rest of it. Otherwise, we can use it for recover until time.

thanks  

-- 
Sent by  dbadba62 from hotmail subdomain  of com
This is a spam protected message. Please answer with reference header.
Posted via http://www.usenet-replayer.com/cgi/content/new