When you have finished using a clone database or want to refresh it, you can resynchronize it with the original database. This is also known as refreshing the snapshot volume or merging the split snapshot image back to the current database image. After resynchronizing, the snapshot can be retaken for backup or decision-support purposes.
There are two choices when resynchronizing the data in a volume:
dbed_vmclonedb -o umount
command. This command also deports the disk group if the primary and secondary hosts are different.
See Shutting Down the Clone Database and Unmounting File Systems.
dbed_vmsnap
command can only be executed on the primary host.
dbed_vmsnap
command imports the disk group that was deported from the secondary host and joins the disk group back to the original disk group. The snapshot volumes again become plexes of the original volumes. The snapshot is then resynchronized.
dbed_vmsnap
(1M) manual page for more information.
dbed_vmsnap,
(dbed_vmchecksnap,
and dbed_vmclonedb
) with the SFDB menu utility.
To resynchronize the snapshot image
dbed_vmsnap
command as follows:
$ /opt/VRTS/bin/
dbed_vmsnap
-S
ORACLE_SID -f
SNAPPLAN -o resync
In this example, the snapshot image is resynchronized with the primary database.
$ /opt/VRTS/bin/
dbed_vmsnap
-S PROD -f snap1 -o resync
dbed_vmsnap started at 2004-04-02 16:19:05
The option resync has been completed.
dbed_vmsnap ended at 2004-04-02 16:19:26
Now, you can again start creating snapshots.