Cloning an Oracle/DB2/Sybase Database in a SAN Environment Using EVA Snapclone Technology (August 2007)

19
DB_NAME=oldName,newName
DB_PATH=oldPath,newPath
INSTANCE=oldInst,newInst
NODENUM=nodeNumber
LOG_DIR=oldDirPath,newDirPath
CONT_PATH=oldContPath1,newContPath1
CONT_PATH=oldContPath2,newContPath2
STORAGE_PATH= oldStoragePath1,newStoragePath1
STIRAGE_PATH= oldStoragePath2,newStoragePath2
The sample configuration file is similar to the following:
DB_NAME=prod,clone
DB_PATH=/mnt/proddata,/mnt/clonedata
INSTANCE=db2inst1,db2inst2
NODENUM=0
LOG_DIR=/mnt/prodlogs/NODE0000,/mnt/clonelogs/NODE0000
CONT_PATH=/mnt/proddata/*,/mnt/clonedata/
Note:
If the database is enabled for automatic storage, you must specify the changes to the
location of the database storage paths (using the STORAGE_PATH parameter), instead of
the tablespace containers (using the CONT_PATH parameter).
For example:
To initialize a DB2 database named clone, enter the following command on the database
server:
db2inidb clone as snapclone
To initialize a cloned DB2 database named mydbcl, and modify the database name, the
database instance name, and the tablespace header information using configuration file
named config.txt, enter the following command on the database server:
db2inidb mydbcl as snapclone relocate using config.txt