Veritas Storage Foundation for Oracle 5.0 Administrator's Guide, HP-UX 11i v3, Second Edition, December 2008

Database NEW9 is being reconfigured
Starting automatic (full) database recovery
Shutting down clone database
Altering clone database archive log directory
Updating log_archive_dest in clone database init file
Found archive log destination at /testvol
Mounting clone database
Resetting logs on new database NEW9
Database instance NEW9 is up and running
To shut down the clone database and unmount the Storage Checkpoint
◆
Use the dbed_clonedb command as follows:
$ /opt/VRTS/bin/dbed_clonedb -S NEW9 -o umount
To mount a Storage Checkpoint file system and start the clone database
◆
Use the dbed_clonedb command as follows:
$ /opt/VRTS/bin/dbed_clonedb -S NEW9 -o restartdb
Database instance NEW9 is up and running.
To delete a clone database and the Storage Checkpoint used to create it
◆
Use the dbed_clonedb command as follows:
$ /opt/VRTS/bin/dbed_clonedb -S NEW9 -o umount -d
Guidelines for Oracle recovery
For optimal Oracle recovery, consider the following guidelines:
■ Back up all control files before Storage Rollback in case the subsequent Oracle
recovery is not successful. Oracle recommends that you keep at least two copies
of the control files for each Oracle database and that you store the copies on
different disks. It is also a good idea to back up the control files before and
after making structural changes to databases.
■ Make sure that the control files are not rolled back.
Using Storage Checkpoints and Storage Rollback
Guidelines for Oracle recovery
174