If the clone database is down as a result of using db2ed_vmclonedb -o umount or rebooting the system, you can restart it with the -o restartdb option.
To start the clone database
Use the db2ed_vmclonedb command as follows:
$ /opt/VRTS/bin/db2ed_vmclonedb -D DB2DATABASE -g snap_dg \ -o restartdb,new_db=db_name,server_name=svr_name -f SNAPPLAN \ [-r relocate_path]
In this example, the clone database is re-started on the same host as the primary database (a single-host configuration).
$ /opt/VRTS/bin/db2ed_vmclonedb -D PROD -g SNAP_PRODdg \ -o restartdb,new_db=NEWPROD,server_name=svr_name -f snap1 -r /clone
db2ed_vmclonedb started at 2006-03-10 14:47:36 Mounting /clone/PROD_HOME on /dev/vx/dsk/SNAP_PRODdg/SNAP_prodvol1. Mounting /clone/PROD_TBS on /dev/vx/dsk/SNAP_PRODdg/SNAP_prodvol2. Files and control structures were changed successfully. Database was catalogued successfully. DBT1000I The tool completed successfully. db2ed_vmclonedb ended at 2006-03-10 14:48:24
In this example, the clone database is re-started on the secondary host (a two-host configuration).
$ /opt/VRTS/bin/db2ed_vmclonedb -D PROD -g SNAP_PRODdg \ -o restartdb,new_db=NEWPROD,server_name=kagu -f snap1 -r /clone
db2ed_vmclonedb started at 2006-03-10 15:03:10 Mounting /clone/PROD_HOME on /dev/vx/dsk/SNAP_PRODdg/SNAP_prodvol1. Mounting /clone/PROD_TBS on /dev/vx/dsk/SNAP_PRODdg/SNAP_prodvol2. Files and control structures were changed successfully. Database was catalogued successfully. DBT1000I The tool completed successfully. db2ed_vmclonedb ended at 2006-03-10 15:03:51