In addition,
enable forced logging in the primary database to ensure that all unlogged direct writes will be
propagated to the standby database by using the alter database force logging command.
Once the log-related parameters have been set, you can begin the process of creating the
standby database.
Step 1: Back Up the Primary Database??™s Datafiles
First, perform a physical backup of the primary database. Oracle recommends using the RMAN
utility to back up the database; you can use the duplicate command within RMAN to automate
the process of creating the standby database.
Step 2: Create a Controlfile for the Standby Database
In the primary database, issue the following command to generate a controlfile that will be used
for the standby database:
alter database create standby controlfile as '/tmp/salesofc.ctl';
Note that you specify the directory and filename where you want the controlfile to be created.
Also, do not use the same directory and controlfile name as you use for the primary database.
Step 3: Create an Initialization File for the Standby Database
In the primary database, create a parameter file from the server parameter file:
create pfile='/tmp/initsalesofc.ora' from spfile;
Edit this initialization file to set the proper values for the standby database. Set the standby
database??™s values for the DB_UNIQUE_NAME, SERVICE_NAMES, CONTROL_FILES, DB_FILE_
NAME_CONVERT, LOG_FILE_NAME_CONVERT, LOG_ARCHIVE_DEST_n, INSTANCE_NAME,
FAL_SERVER, and FAL_CLIENT.
Pages:
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731