Cloning the DB2 database using db2ed_clonedb<a class="indexterm" name="id429057"></a><a class="indexterm" name="id429064"></a><a class="indexterm" name="id429068"></a>


Cloning the DB2 database using db2ed_clonedb
Prev	Using Storage Checkpoints and Storage Rollback	Next

Cloning the DB2 database using db2ed_clonedb

You can use the db2ed_clonedb command to clone a DB2 database using a Storage Checkpoint.

Cloning an existing database using a Storage Checkpoint must be done on the same host.

You have the option to manually or automatically recover the database when using the db2ed_clonedb command:

Manual (Interactive) recovery, which requires using the -i option, of the clone instance allows the user to control the degree of recovery by specifying which archive log files are to be replayed.
Automatic (non-interactive) recovery, which is the default usage of the command, recovers the entire database and replays all of the archive logs. You will not be prompted for any archive log names.

Before cloning the DB2 database, the following conditions must be met:

Prerequisites

You must first create a Storage Checkpoint.

See Creating Storage Checkpoints using db2ed_ckptcreate.
Before using db2ed_clonedb to clone a database either within the same instance or across instances, ensure that your locale is the same as the database locale and that the locale is the same across instances. If you do not know what locale to set, refer to the file /opt/VRTSdb2ed/lib/DB2CODPAGE.tbl for a mapping between the locale and the database Code page.
Make sure you have enough space and system resources to create a clone instance on your system.
A clone database takes up as much memory and machine resources as the primary database.

Usage notes

The db2ed_clonedb command is used to create a copy of a database, cloning all existing database files to new locations.
The db2ed_clonedb command only works when the instance is up.
It is assumed that the user has a basic understanding of the database recovery process.
When cloning a database using db2ed_clonedb, any database within the target instance that has the same name as the source database to be cloned will be temporarily uncataloged and therefore unavailable. If the source database is being cloned within the same instance, it will be temporarily uncataloged while db2ed_clonedb is running. The database will be recataloged on completion of db2ed_clonedb.
See the db2ed_clonedb(1M) manual page for more information.

Options for the db2ed_clonedb command are:

Table: db2ed_clonedb command options

Option	Description
-I SOURCE_INSTANCE	Specifies the source DB2 database. If the instance is not specified here, it is set as the current user.
-S SOURCE_DATABASE	Specifies the name of the source DB2 database.
-T TARGET_DATABASE	Specifies the name of the new DB2 database that will be created.
-c CKPT_NAME	Indicates the name of the Storage Checkpoint to use for creating the new database. The Storage Checkpoint is mounted automatically during the cloning process.
-m MOUNT_POINT	Indicates the location of the database containers to be mounted.
-l	Requires the argument TARGET_DATABASE_REDOLOG_DIRECTORY. Specifies the redo log directory of the target database.
-i	Runs the command in interactive mode where you must respond to prompts by the system. The default mode is non-interactive. (Optional)
-a	Requires the argument RECOVERY_LOG_LOCATION. If this option is specified, a minimal database recovery will occur automatically after the clone is created. (Optional)
-o umount	Shuts down the clone database and unmounts the Storage Checkpoint file system.
-o restartdb	Mounts the Storage Checkpoint file system and starts the clone database. The -o restartdb option will not attempt to recover the clone database.
-d	Used with the -o umount option. If the -d option is specified, the Storage Checkpoint used to create the clone database will be removed along with the clone database.

To clone a DB2 database with manual DB2 recovery

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -S source_db -T target_db1 \
-c Checkpoint_1049927758 -m /db2clone/target_db1

Clone database succeeded.

To clone a DB2 database with automatic DB2 recovery

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -S source_db -T target_db2 \
-c Checkpoint_1049927758 -m /db2clone/target_db2 -a \
/db2clone/db2inst1/NODE0000/SQL00002/SQLOGDIR/

Clone database succeeded.

The database will be rolled forward to 2003-04-09-22.36.02.0000.

/db2clone/db2inst1/NODE0000/SQL00002/SQLOGDIR/

will be used to be searched for archived logs during recovery.

Rollforward Status

Input database alias                                        = TARGET_DB2

Number of nodes have returned status = 1

Node number                                     = 0

Rollforward status                                      = DB  working

Next log file to be read                                        = S0000002.LOG

Log files processed                                     =  -

Last committed transaction                                      = 2003-04-08-20.32.53.000000

DB20000I  The ROLLFORWARD command completed successfully.

Rollforward Status

Input database alias                                        = TARGET_DB2

Number of nodes have returned status = 1

Node number                                     = 0

Rollforward status                                      = not pending

Next log file to be read                                        =

Log files processed                                     = S0000002.LOG - S0000002.LOG

Last committed transaction                                      = 2003-04-08-20.32.53.000000

DB20000I  The ROLLFORWARD command completed successfully.

To clone a DB2 database with interactive DB2 recovery

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -S source_db -T target_db3 \
-c Checkpoint_1049927758 -m /db2clone/target_db3 -i
/db2clone/db2inst1/NODE0000/SQL00002/SQLOGDIR/ will be used to
be searched for archived logs during recovery.

Press <Return> to continue
Or <r> to retry
Or <q> to quit:

The database will be rolled forward to 2003-04-09-22.36.02.0000.
The archived logs will be retrieved from
/db2clone/db2inst1/NODE0000/SQL00002/SQLOGDIR/.
The estimated minimum logs are S0000002.LOG-S0000002.LOG.

You can retrieve all log files by executing
cp /db2clone/db2inst1/NODE0000/SQL00002/SQLOGDIR/*.LOG
/db2clone/target_db3/REDOLOG
from another session and then

Press q to continue

Or Press Enter to retrieve the minimum logs.

The recovery process will stop if more logs is required.

Press <Return> to continue ...
            or <q> to skip ...

Rollforward Status

Input database alias                                        = TARGET_DB3
Number of nodes have returned status = 1
Node number                                     = 0
Rollforward status                                      = DB  working
Next log file to be read                                        = S0000002.LOG
Log files processed                                     =  -
Last committed transaction                                      = 2003-04-08-20.32.53.000000

DB20000I  The ROLLFORWARD command completed successfully.

Rollforward Status

Input database alias                                        = TARGET_DB3
Number of nodes have returned status = 1
Node number                                     = 0
Rollforward status                                      = not pending
Next log file to be read                                        =
Log files processed                                     = S0000002.LOG - S0000002.LOG
Last committed transaction                                      = 2003-04-08-20.32.53.000000

DB20000I  The ROLLFORWARD command completed successfully.

To shut down the clone database and unmount the Storage Checkpoint

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -T target_db3 -o umount

To mount a Storage Checkpoint file system and start the clone database

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -T target_db3 -o restartdb

To delete a clone database and the Storage Checkpoint used to create it

Use the db2ed_clonedb command as follows:

$ /opt/VRTS/bin/db2ed_clonedb -T target_db3 -o umount -d

Prev	Up	Next
Recovering a database using a Storage Checkpoint	Home	Guidelines for DB2 recovery