ter is used toenable or disable the corresponding redo destination. Table 6-1 shows the validvalues that can be assigned to this parameter.
SBYDB5028
Table 6-1 LOG_ARCHIVE_DEST_STATE_nInitialization Parameter Values
| Value |
Description |
| ENABLE |
Redo transport services can transmit redo data to this destination. This is the default. |
| DEFER |
Redo transport services will not transmit redo data to this destination. |
| ALTERNATE |
This destination will become enabled if communication to its associated destination fails. |
A redo transportdestination is configured by setting the LOG_ARCHIVE_DEST_n parameter to acharacter string that includes one or more attributes. This section brieflydescribes the most commonly used attributes. See Chapter 15 for a fulldescription of all LOG_ARCHIVE_DEST_n parameter attributes.
?
The SERVICE attribute, which is a mandatory attribute for a redo transportdestination, must be the first attribute specified in the attribute list. TheSERVICE attribute is used to specify the Oracle Net service name used toconnect to the redo transport destination. The service name must be resolvablethrough an Oracle Net naming method to an Oracle Net connect descriptor thatmatches the Oracle Net listener(s) at the redo transport destination. Theconnect descriptor must specify that a dedicated server connection be used,unless that is the default connection type for the redo transport destination.
See Also:
Oracle Database Net ServicesAdministrator's Guide forinformation about Oracle Net service names, connect descriptors, listeners, andnetwork security
The SYNC attribute is used to specify that thesynchronous redo transport mode be used to send redo data to a redo transportdestination.
The ASYNC attribute is used to specify that theasynchronous redo transport mode be used to send redo data to a redo transportdestination. The asynchronous redo transport mode will be used if neitherthe SYNC nor the ASYNC attribute is specified.
?
The NET_TIMEOUT attribute is used to specify how long the LGWR process will block waiting for anacknowledgement that redo data has been successfully received by a destinationthat uses the synchronous redo transport mode. If an acknowledgement is notreceived within NET_TIMEOUT seconds, the redo transportconnection is terminated and an error is logged.
Oracle recommends thatthe NET_TIMEOUT attribute bespecified whenever the synchronous redo transport mode is used, so that themaximum duration of a redo source database stall caused by a redo transportfault can be precisely controlled. See Section 6.4.2 for informationabout monitoring synchronous redo transport mode response time.
?
The AFFIRM attributeis used to specify that redo received from a redo source database is notacknowledged until it has been written to the standby redo log. The NOAFFIRM attribute is used to specify that received redois acknowledged without waiting for received redo to be written to the standbyredo log.
?
The DB_UNIQUE_NAME attribute is used to specify the DB_UNIQUE_NAME of a redo transportdestination. The DB_UNIQUE_NAME attribute must be specified iftheLOG_ARCHIVE_CONFIG database initializationparameter has been defined and its value includes a DG_CONFIG list.
If the DB_UNIQUE_NAME attribute is specified, itsvalue must match one of the DB_UNIQUE_NAME values in the DG_CONFIG list. It must also match the value of theDB_UNIQUE_NAME database initializationparameter at the redo transport destination. If eith