Oracle Database Discussions

Hi All,

My database is in maximum availability mode at 9.2.0.8:

SQL> select protection_mode from v$database;

PROTECTION_MODE
--------------------
MAXIMUM AVAILABILITY

SQL> show parameter log_archive_dest_2

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_2 string SERVICE=XXX.world LGWR SYNC
AFFIRM,
SQL>

Oracle Documentation says:

Maximum availability mode provides the highest level of data protection that is possible without affecting the availability of the primary database. This protection mode is very similar to maximum protection where a transaction will not commit until the redo data needed to recover that transaction is written to both the local (online) redo log and to at least one remote standby redo log. Unlike maximum protection mode; however, the primary database will not shut down if a fault prevents it from writing its redo data to a remote standby redo log. Instead, the primary database will operate in maximum performance mode until the fault is corrected and all log gaps have been resolved. After all log gaps have been resolved, the primary database automatically resumes operating in maximum availability mode.

and it also says.....

The NET_TIMEOUT attribute of the LOG_ARCHIVE_DEST_n parameter specifies the number of seconds the log writer process on the primary system waits for status from the network server process before terminating the network connection. The NONET_TIMEOUT attribute reverses or undoes the timeout value that you previously specified with the NET_TIMEOUT attribute.

If you do not specify the NET_TIMEOUT attribute (or if you specify the NONET_TIMEOUT attribute, the primary database can potentially stall. To avoid this situation, specify a small, nonzero value for the NET_TIMEOUT attribute so the primary database can continue operation after the user-specified timeout interval expires when waiting for status from the network server.

If the log writer process detects a network disconnection, even one that was terminated due to a network timeout, the log writer process automatically tries to reconnect to the standby database. The log writer process does this to resolve network brownouts and false network terminations. In most cases, except when the network is physically broken, the log writer process is able to automatically reconnect to the network.

The log writer process continually attempts to reconnect to the standby database for a period of time that depends on the data protection mode currently set for the primary database. Use the following time estimates as a guideline for how long the log writer process will try to reconnect to the standby database:

In maximum protection mode, the log writer process tries to reconnect for approximately 5 minutes.
In maximum availability mode, the log writer process tries to reconnect for approximately 2 minutes.
In maximum performance mode, the log writer process tries to reconnect for approximately 30 seconds.

question is:

1>Does that mean if primary database is in maximum availability mode and if there is network issue and it cannot communicate with standby database, it will freeze or stall for 2 minutes and then operate in maximum performance mode.

That freeze for 2 minutes in production is pain :(

2>Does it also mean,

In maximum performance mode primary database will freeze fro 30 seconds and then move on.

3> To convert from maximum availability to maximum performance do I need to bounce the primary database at 9.2.0.8