background image
<< Resuming the Database | Scripts Verification Checklist >>
<< Resuming the Database | Scripts Verification Checklist >>

Recovering the Database

Oracle on the Sun OS Configuration for Remote Volume Mirroring . . . . . . . . . . . . . . . . . . . . . . . . .
5-6
Remote Mirroring of an Oracle Database Using Data Replicator Software
Creating a Volume Copy on the Remote Mirroring
Site
After you have a stable snapshot of the replicated database volumes, 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 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
To recover the database on the secondary site, type the following command to invoke the
db_start
script.
db_start $CFG_FILE $TIME_STAMP
This command invokes the
db_start
script with the parameters shown in
Table 5-5
.
The
db_start
script determines the soft link directory on the primary database site.
The
db_start
script creates soft links on the remote database site.
The
db_start
script starts the remote database from a trace file of a backup control file
that has been altered.
The following text is an example of a trace file of a backup control file that has been
altered.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ESGDB" NORESETLOGS
ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/redo/esgdb/redo01.log' SIZE 50M,
Table 5-5
db_resume
Script Parameters
Parameter
Definition
$CFG_FILE
Filename and path to
.conf
file to use (
erm.conf
)
$TIME_STAMP
Time stamp suffix to append to trace files