Set the same password for SYS on
both the primary and standby databases.
The LOG_ARCHIVE-related parameters, listed next, will configure how the Log Transport
Services work.
LOG_ARCHIVE_CONFIG Within the DB_CONFIG parameter, list the primary and
standby databases.
LOG_ARCHIVE_DEST_1 The location of the primary database??™s archived redo log files.
LOG_ARCHIVE_DEST_2 The remote location used for the standby redo log files.
LOG_ARCHIVE_DEST_STATE_1 Set to ENABLE.
LOG_ARCHIVE_DEST_STATE_2 Set to ENABLE to enable log transport.
LOG_ARCHIVE_FORMAT Specify the format for the archive log file??™s name.
For this example, assume that the primary database has a DB_UNIQUE_NAME value of
???headqtr??™ and the physical standby database has a DB_UNIQUE_NAME value of ???salesofc??™. The
SERVICE_NAMES values can be the same as the DB_UNIQUE_NAME values, but this is not a
requirement. In fact, the SERVICE_NAMES value may be unique to a single node in a RAC
instance.
Chapter 13: Oracle Data Guard 481
The LOG_ARCHIVE_CONFIG parameter setting may resemble the following:
LOG_ARCHIVE_CONFIG='DG_CONFIG=(headqtr,salesofc)'
There are two LOG_ARCHIVE_DEST_n entries??”one for the local copy of the archived redo
log files, and a second for the remote copy that will be shipped to the physical standby database:
LOG_ARCHIVE_DEST_1=
'LOCATION=/arch/headqtr/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=headqtr'
LOG_ARCHIVE_DEST_2=
'SERVICE=salesofc
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=salesofc'
The LOG_ARCHIVE_DEST_1 parameter specifies the location of the archived redo log files for
the primary database (as specified via the DB_UNIQUE_NAME parameter).
Pages:
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729