Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

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 a control file” on page 530.

Copy the Oracle initialization file for the original database to a new

initialization file for the replica database.

For example, the Oracle initialization file for the original database is shown

as initdbase.ora.

See “Initialization file for original production database” on page 531.

For example, the initialization file for the replica database is shown as

initREP1.ora.

See “Initialization file for replica Oracle database” on page 532.

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.

Copy the Oracle remote password file (for example, orapwdbase) in

$ORACLE_HOME/dbs to a new file (for example, orapwREP1).

Preparing a replica Oracle database

About preparing a replica Oracle database

528