When you are done using the clone database, you can shut it down and unmount all snapshot file systems with the db2ed_vmclonedb -o umount command.
Note: |
Any mounted Storage Checkpoints need to be unmounted before running db2ed_vmclonedb -o umount. |
In this example, the clone database is shut down and file systems are unmounted for a clone on the same host as the primary database (a single-host configuration).
$ /opt/VRTS/bin/db2ed_vmclonedb -D PROD -I inst01 \ -o umount,new_db=NEWPROD,server_name=kagu \ -f snap1 -r /clone
db2ed_vmclonedb started at 2006-03-10 14:44:42 DB20000I The FORCE APPLICATION command completed successfully. DB21024I This command is asynchronous and may not be effective immediately. Umounting /clone/PROD_TBS. Umounting /clone/PROD_HOME. db2ed_vmclonedb ended at 2006-03-10 14:44:48
In this example, the clone database is shut down, file systems are unmounted, and the snapshot disk group is deported for a clone on a secondary host (a two-host configuration).
$ /opt/VRTS/bin/db2ed_vmclonedb -D PROD -I inst01 \ -o umount,new_db=NEWPROD,server_name=kagu -f snap2 -r /clone
db2ed_vmclonedb started at 2006-03-10 15:02:33 DB20000I The FORCE APPLICATION command completed successfully. DB21024I This command is asynchronous and may not be effective immediately. Umounting /clone/PROD_TBS. Umounting /clone/PROD_HOME. db2ed_vmclonedb ended at 2006-03-10 15:02:39