Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

To commit reverse resynchronization changes
◆
Use the dbed_vmsnap command as follows:
Warning: Upon completion of reverse resynchronization, the content of the
original database is discarded. Storage Checkpoints taken on either the
original database or the clone database before or after the snapshot was
created are discarded. Storage Checkpoints taken before the snapshot was
created are preserved. The dbed_vmsnap -o
reverse_resync_commitcommand cannot be undone and should be used with
extreme caution.
$ /opt/VRTS/bin/dbed_vmsnap -S FLAS10r1 -f snaptst \
-o reverse_resync_commit
dbed_vmsnap started at 2009-07-30 14:14:47
Oracle instance FLAS10r1 successfully started.
The database is not running in archivelog mode.
SFORA dbed_vmsnap WARNING V-81-5725 After reverse_resync_commit is
performed, you need to recreate the Authentication Password
File using the ORAPWD utility.
The option reverse_resync_commit has been completed.
dbed_vmsnap ended at 2009-07-30 14:20:07
This option is only allowed after reverse_resync_begin has been run.
It is important to note that the procedure is not supported by Veritas Storage
Foundation for Oracle RAC.
Creating or shutting down a clone database using dbed_vmclonedb
You can use the dbed_vmclonedb command to create or shutdown a clone database
on either the primary or secondary host using snapshot volumes from the primary
host.
In an Oracle RAC environment, you can create or shutdown a clone database using
snapshot volumes on the CVM master or slave node.
Before creating or shutting down a clone database, the following conditions must
be met:
363Veritas Storage Foundation for Oracle Command Line Interface
About the command line interface