Re: Standby database question

It's highly available, it may be wrong, but it's available ;)

There are degrees of loss - as you point out, the standby is only up to date as far as the last archived redo log that has arrived. However if the primary discs are still viable, you could copy the on-line redo logs across and recover through them as well.

How big is your 'smoking hole' ? All you have to do is mirror your redo logs to a SAN and the problem disappears. This is all that the Veritas Volume Replicator and the EMC SRDF systems are doing anyway.

But you still have a window of opportunity - what do you do if Oracle scrambles the active redo log as it goes down ? Nothing protects you from that.

--

Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

kal121_at_my-deja.com wrote in message <8r0b2p$nah$1_at_nnrp1.deja.com>...


>True or false:

>

>With a standby database you have to be willing to tolerate some data

>loss. Since you are only copying over arch files to the standby box, if

>your primary database goes down in a smoking hole, you will lose the

>data in the online redo logs that never got archived, and therefore,

>never made it to the standby.

>

>What kind of "HA" solution is this???

>

>

>Sent via Deja.com http://www.deja.com/

>Before you buy.