physical standby (DATAGUARD)

8/7/2019 physical standby (DATAGUARD)

1/24

3.1 Preparing the Primary Database for StandbyDatabase Creation

Before you create a standby database you must first ensure

the primary database is properly configured.

Table 3-1 provides a checklist of the tasks that you performon the primary database to prepare for physical standbydatabase creation. There is also a reference to the sectionthat describes the task in more detail.

Table 3-1 Preparing the Primary Database forPhysical Standby Database Creation

Reference Task

Section 3.1.1 Enable Forced Logging

Section 3.1.2 Create a Password File

Section 3.1.3 Setting Primary Database InitializationParameters

Section 3.1.4 Enable Archiving

Note:

Perform these preparatory tasks only once. Afteryou complete these steps, the database isprepared to serve as the primary database forone or more standby databases.

3.1.1 Enable Forced Logging

Place the primary database in FORCE LOGGING mode afterdatabase creation using the following SQL statement:

SQL> ALTER DATABASE FORCE LOGGING;
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#67107http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#67107http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#67107http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70012http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70012http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70012http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69211http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69211http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69211http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69239http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69239http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69239http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#67107http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70012http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70012http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69211http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69211http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68627http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69239http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#69239


2/24

This statement can take a considerable amount of time tocomplete, because it waits for all unlogged direct write I/Oto finish.

3.1.2 Create a Password File

Create a password file if one does not already exist. Everydatabase in a Data Guard configuration must use a passwordfile, and the password for the SYS user must be identical onevery system for redo data transmission to succeed.See Oracle Database Administrator's Guide.

3.1.3 Setting Primary Database InitializationParameters

On the primary database, you define initializationparameters that control log transport services while thedatabase is in the primary role. There are additionalparameters you need to add that control the receipt of theredo data and log apply services when the primary databaseis transitioned to the standby role.

Example 3-1 shows the primary role initialization parameters

that you maintain on the primary database. This examplerepresents a Data Guard configuration with a primarydatabase located in Chicago and one physical standbydatabase located in Boston. The parameters shownin Example 3-1 are valid for the Chicago database when it isrunning in either the primary or the standby database role.The configuration examples use the names shown in thefollowing table:

Database DB_UNIQUE_NAMEOracle Net ServiceName

Primary chicago chicago

Physicalstandby

boston boston
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120


3/24


4/24

Example 3-2 Primary Database: Standby RoleInitialization Parameters

FAL_SERVER=boston

FAL_CLIENT=chicagoDB_FILE_NAME_CONVERT='/arch1/boston/','/arch1/chicago/','/arch2/boston/','/arch2/c

hicago/'LOG_FILE_NAME_CONVERT='/arch1/boston/','/arch1/chicago/','/arch2/boston/','/arch2/c

hicago/'STANDBY_FILE_MANAGEMENT=AUTO

Specifying the initialization parameters shown in Example 3-2 sets up the primary database to resolve gaps, convertsnew datafile and log file path names from a new primarydatabase, and archives the incoming redo data when thisdatabase is in the standby role. With the initializationparameters for both the primary and standby roles set asdescribed, none of the parameters need to change after arole transition.

The following table provides a brief explanation about eachparameter setting shown in Examples 3-1 and 3-2.

Parameter Recommended Setting

DB_NAME Specify an 8-character name. Use name for all standby databases.

DB_UNIQUE_NAME Specify a unique name for each daThis name stays with the database

does not change, even if the primastandby databases reverse roles.

SERVICE_NAMES Specify a service name for this stadatabase that is unique from the pdatabase service name. If you do nexplicitly specify unique service na
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams050.htm#REFRN10041http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams054.htm#REFRN10242http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams185.htm#REFRN10194http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams050.htm#REFRN10041http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams054.htm#REFRN10242http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams185.htm#REFRN10194


5/24


the primary and standby databaselocated on the same system, the sdefault global name (consists of thdatabase name, DB_NAME, and doname, DB_DOMAIN, parameters) weffect for both databases.

LOG_ARCHIVE_CONFIG Specify the DG_CONFIG attribute oparameter to list the DB_UNIQUE_the primary and standby databaseData Guard configuration; this enadynamic addition of a standby data

a Data Guard configuration that haApplication Clusters primary databrunning in either maximum protectmaximum availability mode. By dethe LOG_ARCHIVE_CONFIG paramenables the database to send and redo; after a role transition, you mto specify these settings again usinthe SEND, NOSEND, RECEIVE,

or NORECEIVE keywords.CONTROL_FILES Specify the path name for the cont

on the primary database. Example1 shows how to do this for two conIt is recommended that a second cthe control file is available so an incan be easily restarted after copyingood control file to the location of control file.

LOG_ARCHIVE_DEST_n Specify where the redo data is to barchived on the primary and standsystems. In Example 3-1 :

LOG_ARCHIVE_DEST_1 archivdata generated by the primar
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams099.htm#REFRN10237http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams028.htm#REFRN10021http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams101.htm#REFRN10086http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams099.htm#REFRN10237http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams028.htm#REFRN10021http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams101.htm#REFRN10086http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120


6/24


database from the local onlinefiles to the local archived redo

in /arch1/chicago/. LOG_ARCHIVE_DEST_2 is val

for the primary role. This desttransmits redo data to the remphysical standby destination b

Note: If a flash recovery area wasconfigured (withthe DB_RECOVERY_FILE_DEST init

parameter) and you have not expliconfigured a local archiving destinathe LOCATION attribute, Data Guaautomatically usesthe LOG_ARCHIVE_DEST_10 initiaparameter as the default destinatiolocal archiving. SeeSection 5.2.3 foinformation. Also, see Chapter 12 fcomplete the LOG_ARCHIVE_DEST

information.

LOG_ARCHIVE_DEST_STATE_n Specify ENABLE to allow log transpservices to transmit redo data to thspecified destination.

REMOTE_LOGIN_PASSWORDFILE Set the same password for SYS onprimary and standby databases. Threcommended setting iseither EXCLUSIVE or SHARED.

LOG_ARCHIVE_FORMAT Specify the format for the archivedfiles using a thread (%t), sequence(%s), and resetlogs ID (%r).See Section 5.7.1 for another exam

FAL_SERVER Specify the Oracle Net service nam
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1265346http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1265346http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1265346http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams102.htm#REFRN10087http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams176.htm#REFRN10184http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams104.htm#REFRN10089http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1235075http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1235075http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1235075http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams067.htm#REFRN10056http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1265346http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams102.htm#REFRN10087http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams176.htm#REFRN10184http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams104.htm#REFRN10089http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1235075http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams067.htm#REFRN10056


7/24


FAL server (typically this is the datrunning in the primary role). WhenChicago database is running in therole, it uses the Boston database aserver from which to fetch (requesmissing archived redo log files if Bounable to automatically send the mlog files. SeeSection 5.8 .

FAL_CLIENT Specify the Oracle Net service namChicago database. The FAL server copies missing archived redo log fi

Chicago standby database. SeeSecDB_FILE_NAME_CONVERT Specify the path name and filenam

location of the primary database dafollowed by the standby location. Tparameter converts the path nameprimary database datafiles to the sdatafile path names. If the standbydatabase is on the same system asprimary database or if the directorstructure where the datafiles are lothe standby site is different from tprimary site, then this parameter irequired. Note that this parameteronly to convert path names for phystandby databases.

LOG_FILE_NAME_CONVERT Specify the location of the primaryonline redo log files followed by the

location. This parameter converts tnames of the primary database logthe path names on the standby dathe standby database is on the samsystem as the primary database ordirectory structure where the log fi
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams066.htm#REFRN10055http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams046.htm#REFRN10038http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams113.htm#REFRN10098http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams066.htm#REFRN10055http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1268285http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams046.htm#REFRN10038http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams113.htm#REFRN10098


8/24


located on the standby system is dfrom the primary system, then thisparameter is required.

STANDBY_FILE_MANAGEMENT Set to AUTO so when datafiles are or dropped from the primary databcorresponding changes are madeautomatically to the standby datab

Caution:

Review the initialization parameter file for additionalparameters 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 databaseis different from those specified on the primary database. Inaddition, you may have to create directories on the standbysystem if they do not already exist.

3.1.4 Enable Archiving

If archiving is not enabled, issue the following statements toput the primary database in ARCHIVELOG mode and enableautomatic archiving:

SQL> SHUTDOWN IMMEDIATE;SQL> STARTUP MOUNT;SQL> ALTER DATABASE ARCHIVELOG;SQL> ALTER DATABASE OPEN;

See Oracle Database Administrator's Guide for informationabout archiving.

3.2 Creating a Physical Standby Database
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams206.htm#REFRN10212http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams017.htm#REFRN10008http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams029.htm#REFRN10022http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams206.htm#REFRN10212http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams017.htm#REFRN10008http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams029.htm#REFRN10022http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htm


9/24

This section describes the tasks you perform to create aphysical standby database.

Table 3-2 provides a checklist of the tasks that you perform

to create a physical standby database and the database ordatabases on which you perform each task. There is also areference to the section that describes the task in moredetail.

Table 3-2 Creating a Physical Standby Database

Reference Task Database

Section 3.2.1 Create a Backup Copy of the

Primary Database Datafiles

Primary

Section 3.2.2 Create a Control File for theStandby Database

Primary

Section 3.2.3 Prepare an Initialization ParameterFile for the Standby Database

Primary

Section 3.2.4 Copy Files from the Primary Systemto the Standby System

Primary

Section 3.2.5 Set Up the Environment to Supportthe Standby Database Standby

Section 3.2.6 Start the Physical StandbyDatabase

Standby

Section 3.2.7 Verify the Physical StandbyDatabase Is Performing Properly

Standby

3.2.1 Create a Backup Copy of the Primary Database

Datafiles

You can use any backup copy of the primary database tocreate the physical standby database, as long as you havethe necessary archived redo log files to completely recoverthe database. Oracle recommends that you use theRecovery Manager utility (RMAN).
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#62499http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#62499http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#62499http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#62499http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58004http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#77233


10/24

See Oracle High Availability Architecture and BestPractices for backup recommendations and Oracle DatabaseBackup and Recovery Advanced User's Guide to perform anRMAN backup operation.

3.2.2 Create a Control File for the Standby Database

If the backup procedure required you to shut down theprimary database, issue the following SQL*Plus statement tostart the primary database:

SQL> STARTUP MOUNT;

Then, create the control file for the standby database, andopen the primary database to user access, as shown in thefollowing example:

SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS'/tmp/boston.ctl';SQL> ALTER DATABASE OPEN;

Note:

You cannot use a single control file for both theprimary and standby databases.

3.2.3 Prepare an Initialization Parameter File for theStandby Database

Perform the following steps to create a standby initializationparameter file.

Step 1 Copy the primary database parameter file tothe standby database.

Create a text initialization parameter file (PFILE) from theserver parameter file (SPFILE) used by the primary
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10726/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htm


11/24

database; a text initialization parameter file can be copied tothe standby location and modified. For example:

SQL> CREATE PFILE='/tmp/initboston.ora' FROM SPFILE;

Later, in Section 3.2.5 , you will convert this file back to aserver parameter file after it is modified to contain theparameter values appropriate for use with the physicalstandby database.

Step 2 Set initialization parameters on the physicalstandby database.

Although most of the initialization parameter settings in thetext initialization parameter file that you copied from theprimary system are also appropriate for the physical standbydatabase, some modifications need to be made.

Example 3-3 shows the portion of the standby initializationparameter file where values were modified for the physicalstandby database. Parameter values that are differentfrom Example 3-1 and Example 3-2 are shown in bold

typeface. The parameters shown in Example 3-3 are validfor the Boston database when it is running in either theprimary or the standby database role.

Example 3-3 Modifying Initialization Parameters for aPhysical Standby Database

.

.

.DB_NAME=chicagoDB_UNIQUE_NAME=bostonSERVICE_NAMES=bostonLOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston)'CONTROL_FILES='/arch1/boston/control1.ctl','/arch2/boston/control2.ctl'
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#72106http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#76120http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68649http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560


12/24

DB_FILE_NAME_CONVERT='/arch1/chicago/','/arch1/boston/','/arch2/chicago/

','/arch2/boston/'LOG_FILE_NAME_CONVERT=

'/arch1/chicago/','/arch1/boston/','/arch2/chicago/','/arch2/boston/'LOG_ARCHIVE_FORMAT=log%t_%s_%r.arcLOG_ARCHIVE_DEST_1='LOCATION=/arch1/boston/VALID_FOR=(ALL_LOGFILES,ALL_ROLES)DB_UNIQUE_NAME=boston'LOG_ARCHIVE_DEST_2='SERVICE=chicago

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=chicago'LOG_ARCHIVE_DEST_STATE_1=ENABLELOG_ARCHIVE_DEST_STATE_2=ENABLEREMOTE_LOGIN_PASSWORDFILE=EXCLUSIVESTANDBY_FILE_MANAGEMENT=AUTOINSTANCE_NAME=bostonFAL_SERVER=chicagoFAL_CLIENT=boston

.

.

.

Note that the example assumes the use of theARCn processes (the default) to transmit redo data. If youspecify the LGWR process to transmit redo data to both thelocal and remote destinations, also includethe NET_TIMEOUT attribute (described in Chapter 12 ) on

the LOG_ARCHIVE_DEST_2 initialization parameter.

In addition, ensure the COMPATIBLE initialization parameteris set to the same value on both the primary and standbydatabases. If the values differ, log transport services may beunable to transmit redo data from the primary database tothe standby databases. In a Data Guard
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_arch_dest_param.htm#109587


13/24

configuration, COMPATIBLE must be set to a minimum of9.2.0.1.0. However, if you want to take advantage of newOracle Database 10gfeatures, setthe COMPATIBLE parameter to 10.1.0.0 or higher.

It is always a good practice to use the SHOWPARAMETERS command to verify no other parameters needto be changed.

The following table provides a brief explanation about theparameter settings shown in Example 3-3 that have differentsettings from the primary database.

Parameter Recommended SettingDB_UNIQUE_NAME Specify a unique name for this database

This name stays with the database anddoes not change even if the primary andstandby databases reverse roles.

SERVICE_NAMES Specify a service name for this standbydatabase that is unique from the primarydatabase service name. If you do notexplicitly specify unique service names athe primary and standby databases arelocated on the same system, the samedefault global name (comprised of thedatabase name, DB_NAME, and domainname, DB_DOMAIN, parameters) will beeffect for both databases.

CONTROL_FILES Specify the path name for the control fileon the standby database. Example 3-

3 shows how to do this for two control fiIt is recommended that a second copy othe control file is available so an instanccan be easily restarted after copying thegood control file to the location of the bacontrol file.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams054.htm#REFRN10242http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams185.htm#REFRN10194http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams028.htm#REFRN10021http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams054.htm#REFRN10242http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams185.htm#REFRN10194http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams028.htm#REFRN10021http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560


14/24


DB_FILE_NAME_CONVERT Specify the path name and filenamelocation of the primary database datafilefollowed by the standby location. Thisparameter converts the path names of tprimary database datafiles to the standbdatafile path names. If the standbydatabase is on the same system as theprimary database or if the directorystructure where the datafiles are locatedthe standby site is different from theprimary site, then this parameter isrequired.

LOG_FILE_NAME_CONVERT Specify the location of the primary databonline redo log files followed by the stanlocation. This parameter converts the panames of the primary database log files the path names on the standby databasethe standby database is on the samesystem as the primary database or if thedirectory structure where the log files ar

located on the standby system is differefrom the primary system, then thisparameter is required.

LOG_ARCHIVE_DEST_n Specify where the redo data is to bearchived. In Example 3-3 :

LOG_ARCHIVE_DEST_1 archives redata received from the primarydatabase to archived redo log files

in /arch1/boston/. LOG_ARCHIVE_DEST_2 is currently

ignored because this destination isvalid only for the primary role. If aswitchover occurs and this instancebecomes the primary database, the
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams046.htm#REFRN10038http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams113.htm#REFRN10098http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams101.htm#REFRN10086http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams046.htm#REFRN10038http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams113.htm#REFRN10098http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams101.htm#REFRN10086http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70560


15/24


16/24

Review the initialization parameter file for additionalparameters that may need to be modified. For example, youmay need to modify the dump destination parameters

(BACKGROUND_DUMP_DEST, CORE_DUMP_DEST, USER_DUMP_DEST) if the directory location on the standby databaseis different from those specified on the primary database. Inaddition, you may have to create directories on the standbysystem if they do not already exist.

3.2.4 Copy Files from the Primary System to theStandby System

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

Backup datafiles created in Section 3.2.1 Standby control file created in Section 3.2.2 Initialization parameter file created in Section 3.2.3

3.2.5 Set Up the Environment to Support the StandbyDatabase

Perform the following steps to create a Windows-basedservice, create a password file, set up the Oracle Netenvironment, and create a SPFILE.

Step 1 Create a Windows-based service.

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

WINNT> oradim -NEW -SID boston -INTPWD password-STARTMODE manual
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams017.htm#REFRN10008http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams029.htm#REFRN10022http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams017.htm#REFRN10008http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams029.htm#REFRN10022http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10755/initparams222.htm#REFRN10229http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#58180http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#68939http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70518


17/24


18/24

Step 5 Create Oracle Net service names.

On both the primary and standby systems, use Oracle NetManager to create a network service name for the primary

and standby databases that will be used by log transportservices.

The Oracle Net service name must resolve to a connectdescriptor that uses the same protocol, host address, port,and SID that you specified when you configured the listenersfor the primary and standby databases. The connectdescriptor must also specify that a dedicated server be used.

See the Oracle Net Services Administrator's Guide and

the Oracle Database Administrator's Guide.

Step 6 Create a server parameter file for the standbydatabase.

If you plan to immediately transition the physical standbydatabase to a logical standby database (as describedin Chapter 4, "Creating a Logical Standby Database" ), thenskip this step and proceed with the instructions

in Section 3.2.6 .

On an idle standby database, use theSQL CREATE statement to create a server parameter file forthe standby database from the text initialization parameterfile that was edited in Step 2. For example:

SQL> CREATE SPFILE FROM PFILE='initboston.ora';

3.2.6 Start the Physical Standby Database

Perform the following steps to start the physical standbydatabase and Redo Apply.

Step 1 Start the physical standby database.
http://www.stanford.edu/dept/itss/docs/oracle/10g/network.101/b10775/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htm#63563http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htm#63563http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htm#63563http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70551http://www.stanford.edu/dept/itss/docs/oracle/10g/network.101/b10775/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10739/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htm#63563http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#61076http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm#70551


19/24


20/24

9.1. Add new temporary files to the standby database.

For each tablespace identified in the previous query,

add a new temporary file to the standby database. Thefollowing example adds a new temporary filecalled TEMP1 with size and reuse characteristics thatmatch the primary database temporary files:

SQL> ALTER TABLESPACE TEMP1 ADD TEMPFILE2> '/arch1/boston/temp01.dbf'3> SIZE 40M REUSE;

Note:

To create temporary files on the physicalstandby database that match the temporary fileson the primary database, querythe V$TEMPFILE view on the primary databaseto obtain complete information about theprimary database temporary files.

Step 3 Start Redo Apply.

On the standby database, issue the following command tostart Redo Apply:

SQL> ALTER DATABASE RECOVER MANAGED STANDBYDATABASE DISCONNECT FROM SESSION;

This statement automatically mounts the database. Also, the

statement includes the DISCONNECT FROM SESSION optionso that Redo Apply runs in a background session.

See Section 6.3, "Applying Redo Data to Physical StandbyDatabases" for more information.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1020862


21/24

Step 4 Test archival operations to the physicalstandby database.

The transmission of redo data to the remote standby

location does not occur until after a log switch. A log switchoccurs, by default, when an online redo log file becomes full.To force a log switch so that redo data is transmittedimmediately, use the following ALTER SYSTEM statement onthe primary database. For example:

SQL> ALTER SYSTEM SWITCH LOGFILE;

3.2.7 Verify the Physical Standby Database IsPerforming Properly

Once you create the physical standby database and set uplog transport services, you may want to verify databasemodifications are being successfully transmitted from theprimary database to the standby database.

To see that redo data is being received on the standbydatabase, you should first identify the existing archived redolog files on the standby database, force a log switch and

archive a few online redo log files on the primary database,and then check the standby database again. The followingsteps show how to perform these tasks.

Step 1 Identify the existing archived redo log files.

On the standby database, query the V$ARCHIVED_LOG viewto identify existing files in the archived redo log. Forexample:

SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

SEQUENCE# FIRST_TIME NEXT_TIME---------- ------------------ ------------------

8 11-JUL-02 17:50:45 11-JUL-02 17:50:53


22/24


23/24

On the standby database, query the V$ARCHIVED_LOG viewto verify the archived redo log files were applied.

SQL> SELECT SEQUENCE#,APPLIED FROM

V$ARCHIVED_LOG2 ORDER BY SEQUENCE#;

SEQUENCE# APP--------- ---

8 YES9 YES10 YES11 YES

4 rows selected.

See Section 5.9.1, "Monitoring Log File ArchivalInformation" and Section 6.3.4, "Monitoring Log ApplyServices on Physical Standby Databases" to verify logtransport services and log apply services are workingcorrectly.

3.3 Further Preparations

At this point, the physical standby database is running andcan provide the maximum performance level of dataprotection. The following list describes additionalpreparations you can take on the physical standby database:

Upgrade the data protection mode

The Data Guard configuration is initially set up in themaximum performance mode (the default).See Section 5.6 for information about the dataprotection modes and how to upgrade or downgradethe current protection mode.

Configure standby redo logs
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1102241http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1102241http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1102241http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1267920http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_apply.htm#1035178http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1102241


24/24

Standby redo logs are required for standby databasesrunning in the maximum protection mode andmaximum availability mode. However, configuringstandby redo logs is recommended on all standby

databases, because during a failover Data Guard canrecover and apply more redo data from standby redolog files than from the archived redo log files alone. Thestandby redo logs should exist on both primary andstandby databases and have the same size and names.See Section 5.6.2 for more information.

Enable Flashback Database

Flashback Database removes the need to re-create theprimary database after a failover. Flashback Databaseis similar to conventional point-in-time recovery in itseffects, enabling you to return a database to its state ata time in the recent past. Flashback Database is fasterthan point-in-time recovery, because it does notrequire restoring datafiles from backup or the extensiveapplication of redo data. You can enable FlashbackDatabase on the primary database, the standbydatabase, or both. See Oracle Database Backup andRecovery Advanced User's Guide for more information.

Copyright 1999,

2003Oracle

CorporationAll Rights

Reserved.

HomeBookList

Contents Index

Master Index

FeedbPreviousNext
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1225705http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1225705http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1225705http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/nav/portal_3.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/nav/portal_3.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/feedback.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/standby.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/log_transport.htm#1225705http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10734/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/standby.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/standby.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ls.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/cpyr.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/nav/portal_3.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/nav/portal_3.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/nav/portal_3.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/index.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/mix.101/b12039/toc.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/feedback.htmhttp://www.stanford.edu/dept/itss/docs/oracle/10g/dcommon/html/feedback.htm

physical standby (DATAGUARD)

Documents

Transcript of physical standby (DATAGUARD)