VERITAS FlashSnap Point-In-Time-Copy Solutions Administrator's Guide

Appendix B, Preparing a Replica Oracle Database 83
c. If required, change the following line:
CREATE CONTROLFILE REUSE DATABASE "odb" NORESETLOGS ARCHIVELOG
so that it reads:
CREATE CONTROLFILE SET DATABASE "ndb" RESETLOGS NOARCHIVELOG
where odb is the name of the original database and ndb is the name of the replica database
(DBASE and REP1 in the example). Note that to reduce unnecessary overhead, the new
database is not run in archive log mode.
See “SQL Script to Create Control File” on page 85 for an example.
8. Copy the Oracle initialization file (for example, initdbase.ora; see “Initialization File for
Original Production Database” on page 86) for the original database to a new initialization file
for the replica database (for example, initREP1.ora; see “Initialization File for Replica
Oracle Database” on page 87).
Edit the copied file and change the definitions of the following parameters:
background_dump_dest Background dump location.
core_dump_dest Core dump location.
db_name Database name to the name of the replica database.
log_archive_dest Archive log location, set equal to the path created in step 4 (for
example, /rep/dbase_arch).
log_archive_start Archive log mode, log_archive_start, to FALSE.
user_dump_dest User dump location.
You may also wish to reduce the resource usage of the new database by adjusting the values of
parameters such as db_block_buffers. See the Oracle Database Administrator’s Guide
for more information.
9. Copy the Oracle remote password file (for example, orapwdbase) in
$ORACLE_HOME/dbs to a new file (for example, orapwREP1).