Skip Headers
Oracle® Database Reference
11g Release 2 (11.2)

E40402-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

LOG_ARCHIVE_LOCAL_FIRST

Property Description
Parameter type Boolean
Default value true
Modifiable ALTER SYSTEM
Range of values true | false
Basic No

Note:

The LOG_ARCHIVE_LOCAL_FIRST parameter is deprecated. It is retained for backward compatibility only.

LOG_ARCHIVE_LOCAL_FIRST specifies when the archiver processes (ARCn) transmit redo data to remote standby database destinations.

Values:

If LOG_ARCHIVE_LOCAL_FIRST is set to true, then it is not used on a physical standby database and any database for which the following attributes have been specified in the LOG_ARCHIVE_DEST_n initialization parameter:

If LOG_ARCHIVE_LOCAL_FIRST is set to true, then it is ignored during certain operations, such as during a switchover, which requires synchronized archival operations. If the destination was explicitly configured to use the log writer process (by specifying the LGWR attribute in the LOG_ARCHIVE_DEST_n initialization parameter), but for some reason the log writer process becomes unable to archive to the destination, then Data Guard will revert to using the ARCn process to complete archival operations using the default behavior, even if LOG_ARCHIVE_LOCAL_FIRST is set to false.

For example, if a standby database problem or a network problem causes the LGWR process to fail, then the ARCn process will complete the archival. Data Guard minimizes the effect on the primary database as much as possible by archiving to the local destination first to ensure the online redo log files are available to the LGWR process as quickly as possible.

See Also:

Oracle Data Guard Concepts and Administration for more information about the LOG_ARCHIVE_LOCAL_FIRST initialization parameter and its effect on ARCn behavior