RE: DataGuard - Maximum Availability mode vs sync detection

I don't see where is the real issue:

1. If you have a fixed setup, then it is in the init.ora or just do a string command on the spfile and save the spfile/init.ora outside the primary box on every spfile change.
2. Alternatively, if you have some scripts that changes the setup of the archive_log_det_(x) parameters on the fly with scope=memory, the information is volatile, in which case you need to save this information outside the primary box.

Bernard Polarski
Oracle DBA

-----Original Message-----

From: Laimutis Nedzinskas [mailto:Laimutis.Nedzinskas_at_landsbanki.is] Sent: vrijdag 19 januari 2007 12:05
To: oracle-l_at_freelists.org
Subject: DataGuard - Maximum Availability mode vs sync detection

Is it possible to know if standby is synchronized with primary when DG is configured in Maximum Availability mode?

As I understand - it is not possible.
If primary dies for sure(absolutely no access to any primary files) then there is no way of knowing if it was operating in Maximum Availability(meaning standby is in sync) or downgraded into Maximum Performance mode(meaning standby is not in sync.)

What are possible solutions to this problem?

I see just one: some data of the primary db must survive the primary crash.
For example, the fact that primary went into downgraded Maximum Performance mode is recorded into background alert log. If we have access to this log then we can find in what mode the primary database operated just before the death. Alternatively, control file is the most credible source.

The question is: what is the best way to preserve this critical primary db data so that it is readily available for the third party which decides the failover? I can think of some shared storage for both control files and background logs.

Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Fri Jan 19 2007 - 07:26:47 CST