If you use a
different directory structure for the database files, you will need to define the values for the DB_
FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the standby database.
In physical standby databases, all the redo comes from the primary database. When physical
standby databases are opened in read-only mode, no redo is generated. Oracle Data Guard does,
however, use archived redo log files to support the replication of the data and SQL commands
used to update the standby databases.
NOTE
For each standby database, you should create a standby redo log file
to store redo data received from the primary database.
Preparing the Primary Database
On the primary database, make sure you have set values for the following parameters, which
impact the transfer of the redo log data. The first five parameters, listed next, are standard for
most databases; set REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE to support remote access
by SYSDBA-privileged users.
DB_NAME The database name. Use the same name for all standby databases
and the primary database.
DB_UNIQUE_NAME The unique name for the database. This value must be different for
each standby database and must differ from the primary database.
SERVICE_NAMES Service names for the databases; set separate service names for the
primary and standby databases.
CONTROL_FILES The location of the controlfiles.
REMOTE_LOGIN_
PASSWORDFILE
Set to EXCLUSIVE or SHARED.
Pages:
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728