The writes to the standby locations
are handled by the ARCH process by default.
Once you have decided the type of standby and the data protection mode for your
configuration, you can create your standby database.
LOG_ARCHIVE_DEST_n Parameter Attributes
As illustrated in the following sections, Oracle Data Guard configurations rely on a number of
attributes within the LOG_ARCHIVE_DEST_n parameter. Table 13-1 summarizes the attributes
available for this parameter. In almost all cases the attributes are paired; in some cases the second
member of the pair simply serves to nullify the setting.
?–
Attribute Description
AFFIRM and NOAFFIRM AFFIRM ensures all disk I/O to the archived redo log files or standby redo log
files at the standby destination is performed synchronously and completes
successfully before the log writer process (LGWR) can continue; therefore,
LGWR waits before writing to the local online redo log files on the primary
database. AFFIRM is required to achieve no data loss.
NOAFFIRM indicates all disk I/O to archived redo log files and standby
redo log files is to be performed asynchronously; online redo log files on the
primary database can be reused before the disk I/O on the standby destination
completes.
ALTERNATE and
NOALTERNATE
ALTERNATE specifies an alternate LOG_ARCHIVE_DEST_n destination to use
when the original archiving destination fails.
ARCH and LGWR ARCH, the default, specifies that the ARCH process is responsible for
transmitting redo data to archival destinations.
Pages:
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724