LGWR specifies that the LGWR
process performs the log transport operations.
DB_UNIQUE_NAME and
NODB_UNIQUE_NAME
DB_UNIQUE_NAME specifies the unique database name for the destination.
DELAY and NODELAY DELAY specifies a time lag between archiving redo data on the standby site and
applying the archived redo log file to the standby database; DELAY may be used
to protect the standby database from corrupted or erroneous primary data. If
neither DELAY nor NODELAY is specified, NODELAY is the default.
DEPENDENCY and
NODEPENDENCY
DEPENDENCY allows you to transmit redo data to a destination that then shares
its archived redo log files among multiple standby databases. You must use the
REGISTER and SERVICE attributes when you create a DEPENDENCY.
LOCATION and SERVICE Each destination must specify either the LOCATION or the SERVICE attribute
to identify either a local disk directory (via LOCATION) or a remote database
destination where Log Transport Services can transmit redo data (via SERVICE).
MANDATORY and
OPTIONAL
If a destination is OPTIONAL, archiving to that destination may fail, yet the
online redo log file is available for reuse and may be overwritten eventually. If
the archival operation of a MANDATORY destination fails, online redo log files
cannot be overwritten.
TABLE 13-1 LOG_ARCHIVE_DEST_n Parameter Attributes
Chapter 13: Oracle Data Guard 479
Creating the Standby Database Configuration
You can use SQL*Plus, Oracle Enterprise Manager (OEM), or Data Guard??“specific tools to configure
and administer Data Guard configurations.
Pages:
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725