Data Guard Rapid Protection Mode Tips Oracle Tips by Burleson Consulting December 9, 2011

Oracle Data Guard - Rapid Protection Mode

In this mode, the primary database does not wait for the acknowledgements of the redo data transfer to any standby database. This offers a high level of performance and availability of the primary database. This constitutes a ‘minimal-data-loss’ Data Guard environment. A sample setting for the log transport service for rapid protection is shown in the following example:

LOG_ARCHIVE_DEST_3=’SERVICE=appsstdby1 LGWR ASYNC=2048 NOAFFIRM’;

Standby redo logs are required at the standby site because the log writer transfers redo data from the primary database. The failure resolution policy should be set to unprotected.

Delayed Protection Mode

This offers another ‘minimal-data-loss’ Data Guard configuration. The archiver process transmits archived redo logs from the primary database to the standby database. The log_archive_dest_n setting is very simple and is shown below:

LOG_ARCHIVE_DEST_3=’SERVICE=appsstdby1’.

Standby redo logs are not needed on the standby site. The failure resolution policy should be set to unprotected.

Protection Modes in Oracle9i Release 2  to 11g

Although the types of data protection mode have been reduced in number from four to three in Release 2 of Oracle9i, there has been no significant conceptual change in the protection modes. It supports the same two important ‘no-data-loss’ and ‘minimum-data-loss’ protection levels.