■LOG_ARCHIVE_DEST_1archives redo data generated by the primary

database from the local online redo log files to the local archived redo log

files in /arch1/chicago/.

■LOG_ARCHIVE_DEST_2is valid only for the primary role. This destination

transmits redo data to the remote physical standby destinationboston.

Note: If a flash recovery area was configured (with theDB_RECOVERY_FILE_

DEST initialization parameter) and you have not explicitly configured a local

archiving destination with the LOCATIONattribute, Data Guard automatically

uses the LOG_ARCHIVE_DEST_10initialization parameter as the default

destination for local archiving. See Section 5.2.3for more information. Also, see

Chapter 14 for completeLOG_ARCHIVE_DEST_ninformation.

LOG_ARCHIVE_DEST_STATE_n SpecifyENABLEto allow redo transport services to transmit redo data to the

specified destination.

REMOTE_LOGIN_PASSWORDFILE Set the same password forSYSon both the primary and standby databases. The

recommended setting is eitherEXCLUSIVEorSHARED.

LOG_ARCHIVE_FORMAT Specify the format for the archived redo log files using a thread (%t), sequence

number (%s), and resetlogs ID (%r). SeeSection 5.7.1for another example.

LOG_ARCHIVE_MAX_PROCESSES =integer

Specify the maximum number (from 1 to 30) of archiver (ARCn) processes youwant Oracle software to invoke initially. The default value is 4. SeeSection 5.3.1.2for more information aboutARCnprocessing.

FAL_SERVER Specify the Oracle Net service name of the FAL server (typically this is the

database running in the primary role). When the Chicago database is running in

the standby role, it uses the Boston database as the FAL server from which to

fetch (request) missing archived redo log files if Boston is unable to

automatically send the missing log files. See Section 5.8.

FAL_CLIENT Specify the Oracle Net service name of the Chicago database. The FAL server

(Boston) copies missing archived redo log files to the Chicago standby database.

See Section 5.8.

DB_FILE_NAME_CONVERT Specify the path name and filename location of the primary database datafiles

followed by the standby location. This parameter converts the path names of the

primary database datafiles to the standby datafile path names. If the standby

database is on the same system as the primary database or if the directory

structure where the datafiles are located on the standby site is different from the

primary site, then this parameter is required. Note that this parameter is used

only to convert path names for physical standby databases. Multiple pairs of

paths may be specified by this parameter.

LOG_FILE_NAME_CONVERT Specify the location of the primary database online redo log files followed by

the standby location. This parameter converts the path names of the primary

database log files to the path names on the standby database. If the standby

database is on the same system as the primary database or if the directory

structure where the log files are located on the standby system is different from

the primary system, then this parameter is required. Multiple pairs of paths may

be specified by this parameter.

STANDBY_FILE_MANAGEMENT Set toAUTOso when datafiles are added to or dropped from the primary

database, corresponding changes are made automatically to the standby database.