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

82 VERITAS FlashSnap Point-In-Time Copy Solutions Administrator’s Guide
4. Create the mount points that are to be used to mount the new database. For example, create
/rep/dbase_vol for the snapshot of the tablespace volume, /rep/dbase_logs for the
redo logs, and /rep/dbase_arch for the archived logs:
# mkdir -p /rep/dbase_vol
# mkdir -p /rep/dbase_logs
# mkdir -p /rep/dbase_arch
5. Mount the redo log and archive log volumes on their respective mount points using the
following command:
# mount -F vxfs /dev/vx/dsk/diskgroup/volume mount_point
In this example, the commands would be:
# mount -F vxfs /dev/vx/dsk/localdg/rep_dbase_logs \
/rep/dbase_logs
# mount -F vxfs /dev/vx/dsk/localdg/rep_dbase_arch \
/rep/dbase_arch
6. As the Oracle database administrator on the primary host, obtain an ASCII version of the
current Oracle control file using the following SQL command:
alter database backup controlfile to trace;
This command writes a text version of the control file to the directory
$ORACLE_HOME/admin/dbase/udump. See “Text Control File for Original Production
Database” on page 84 for an example.
7. Modify the text version of the control file created in the previous step as described below to
create a new SQL script to set up the replica database:
a. If required, change the locations defined under LOGFILE for the log files. For example,
change lines of the form:
GROUP N ’/dbase_vol/logN’ SIZE 52428288,
so that they read:
GROUP N ’/rep/dbase_vol/logN’ SIZE 52428288,
b. If required, change the locations defined under DATAFILE for the tablespaces. For
example, change lines of the form:
’/dbase_vol/table’,
so that they read:
’/rep/dbase_vol/table’,