Creating Volume Copy on Remote Mirroring Site
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating a Volume Copy on the Remote Mirroring Site
Remote Mirroring of an Oracle Database Using Data Replicator Software
4-3
Creating a Volume Copy on the Remote Mirroring
Site
After you have a stable snapshot of the replicated database logical drives, you can create a
read/write copy of these drives. This copy maps to the remote host. This action is done
with a function inside of the erm.ksh script. This function checks to see if the volume is
already associated as a drive copy target. If the volume is already associated, the script
recopies the data. If the volume is not associated, the script creates a new copy of the
snapshot volume.
Recovering the Database on the Remote Mirroring
Site
After the volume copy process is completed, import the volume groups back to the remote
host, and mount them as read/write. Restart the remote database with the
db_start
script.
Type the following command, and then press Enter.
db_start $CFG_FILE $TIME_STAMP
This command invokes the
db_start
script with the parameters shown in Table
Scripts Verification Checklist
When you run the
erm.ksh
script, all errors, warnings, and statuses are logged both to the
screen and to a time-stamped log file in the log directory. This output shows any errors
discovered in the script execution. Also, a trace file is created when you run the main
script. This trace file logs the
stdout
and
stderr
of most of the commands that are run
during the main process. You can use this trace file to determine specific OS issues within
the environment. The trace file also shows what command was run and the parameters
used to invoke that command. Between these two files (the log file and the trace file), you
can resolve issues within your environment. You also can zip up the
/opt/LSI_ERM
directory, and send it to a Customer and Technical Support representative for further
analysis.
Table 4-4
db_start
Script Parameters
Parameter
Definition
$CFG_FILE
The name and path to the
.conf
file to be used
$TIME_STAMP
The suffix to append to the trace files in date/time format
