Example 3–5 shows the portion of the standby initialization parameter file where values were modified for the physical standby database. Parameter values that are different fromExample 3–3 andExample 3–4are shown in bold typeface. The parameters shown inExample 3–5are valid for the Boston database when it is running in either the primary or the standby database role.

Example 3–5 Modifying Initialization Parameters for a Physical Standby Database

.

.

.

DB_NAME=chicago

DB_UNIQUE_NAME=boston

LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston)'

CONTROL_FILES='/arch1/boston/control1.ctl', '/arch2/boston/control2.ctl'

DB_FILE_NAME_CONVERT='chicago','boston'

LOG_FILE_NAME_CONVERT=

'/arch1/chicago/','/arch1/boston/','/arch2/chicago/','/arch2/boston/'

LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc

LOG_ARCHIVE_DEST_1=

'LOCATION=/arch1/boston/

VALID_FOR=(ALL_LOGFILES,ALL_ROLES)

DB_UNIQUE_NAME=boston'

LOG_ARCHIVE_DEST_2=

'SERVICE=chicago LGWR ASYNC

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)

DB_UNIQUE_NAME=chicago'

LOG_ARCHIVE_DEST_STATE_1=ENABLE

LOG_ARCHIVE_DEST_STATE_2=ENABLE

REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE

STANDBY_FILE_MANAGEMENT=AUTO

FAL_SERVER=chicago

FAL_CLIENT=boston

.

.

.

Note that the example assumes the use of the LGWR process to transmit redo data to both the local and remote destinations on theLOG_ARCHIVE_DEST_2initialization parameter. In addition, ensure theCOMPATIBLEinitialization parameter is set to the same value on both the primary and standby databases. If the values differ, redo transport services may be unable to transmit redo data from the primary database to the standby databases. In a Data Guard configuration,COMPATIBLE must be set to a minimum of 9.2.0.1.0. However, if you want to take advantage of new Oracle Database 10gfeatures, set theCOMPATIBLEparameter to 10.2.0.0 or higher.

It is always a good practice to use the SHOW PARAMETERScommand to verify no other parameters need to be changed. The following table provides a brief explanation about the parameter settings shown inExample 3–5that have different settings from the primary database.

?

Parameter Recommended Setting

DB_UNIQUE_NAME Specify a unique name for this database. This name stays with the database and

does not change even if the primary and standby databases reverse roles.

CONTROL_FILES Specify the path name for the control files on the standby database.Example 3–5

shows how to do this for two control files. It is recommended that a second

copy of the control file is available so an instance can be easily restarted after

copying the good control file to the location of the bad control file.

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.

(DB_FILE_NAME_CONVERT=’主库路径’,’备库路经’)

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