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.

LOG_ARCHIVE_DEST_n Specify where the redo data is to be archived. InExample 3–5:

■ LOG_ARCHIVE_DEST_1archives redo data received from the primary

database to archived redo log files in /arch1/boston/.

■ LOG_ARCHIVE_DEST_2is currently ignored because this destination is

valid only for the primary role. If a switchover occurs and this instance

becomes the primary database, then it will transmit redo data to the remote

Chicago destination.

Note: If a flash recovery area was configured (with theDB_RECOVERY_FILE_DESTinitialization parameter) and you have not explicitly configured a localarchiving destination with theLOCATIONattribute, Data Guard automaticallyuses theLOG_ARCHIVE_DEST_10initialization parameter as the defaultdestination for local archiving. SeeSection 5.2.3for more information. Also, seeChapter 14for complete information aboutLOG_ARCHIVE_DEST_n.

?

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

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

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

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

automatically send the missing log files. See Section 5.8.

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

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

See Section 5.8.

Caution: Review the initialization parameter file for additional parameters that may need to be modified. For example, you may need to modify the dump destination parameters (BACKGROUND_DUMP_DEST, CORE_DUMP_DEST, USER_DUMP_DEST) if the directory location on the standby database is different from those

specified on the primary database. In addition, you may have to create directories on the standby system if they do not already exist.

3.2.4 Copy Files from the Primary System to the Standby System

Use an operating system copy utility to copy the following binary files from the primary system to the standby system:

■ Backup datafiles created inSection 3.2.1

■ Standby control file created inSection 3.2.2

■ Initialization parameter file created inSection 3.2.3

3.2.5 Set Up the Environment to Support the Standby Database

Perform the following steps to create a Windows-based service, create a password file, set up the Oracle Net environment, and create a SPFILE.

Step 1 Create a Windows-based service.

If the standby system is running on a Windows-based system, use the ORADIM utility to create a Windows Service and password file. For example:

WINNT> oradim -NEW -SID boston -INTPWD password-STARTMODE manual

See Oracle Database Platform Guide for Microsoft Windows (32-Bit)for more information about using the ORADIM utility.

Step 2 Create a password file.

On platforms other than Windows, create a password file, and set the password for theSYSuser to the same password used by theSYSuser on the primary database. The password for theSYSuser on every database in a Data Guard configuration must be identical for redo transmission to succeed. SeeOracle Database Administrator's Guide.

Step 3 Configure listeners for the primary and standby databases.