DB2 10.5 for Linux, UNIX, and Windows

db2tdbmgr - Migrate tools catalog database command

The db2tdbmgr command migrates specific tools catalog database objects after running the UPGRADE DATABASE command on the tools catalog database.

Authorization


sysadm

Required connection

This command establishes a database connection.

Command syntax

Read syntax diagramSkip visual syntax diagram
>>-db2tdbmgr-- -d--db_name-- -s--schema_name-------------------->

>--+----------------+--+---------------+-----------------------><
   '- -u--user_name-'  '- -p--password-'   

Command parameters

-d db_name
Tools catalog database name.
-s schema_name
Tools catalog schema name.
-u user_name
User name used to connect the tools catalog database.
-p password
Password used to connect the tools catalog database.
-e enc
Upgrade the TOOLSDB encrypted passwords to new standards. To be used when, you upgrade to DB2® Cancun Release 10.5.0.4 or later.
Note: Back up the TOOLSDB before you use this option. This option must be used only one time.
-e dec
Set the TOOLSDB encrypted passwords to old standards. To be used when, you roll back to Fix Packs older than DB2 Cancun Release 10.5.0.4.
Note: Back up the TOOLSDB before you use this option. This option must be used only one time.

Examples

1. The following example migrates the tools catalog tables, under the database alias toolsdb and schema systools:
db2tdbmgr -d toolsdb -s systools -u db2inst1 -p *******
2. The following example migrates the tools catalog tables, under the database alias toolsdb and schema systools. The example specifies that the database encrypts passwords with new standards that are introduced in DB2 Cancun Release 10.5.0.4.
db2tdbmgr -d toolsdb -s systools -u db2inst1 -p ******* -e enc

Usage notes

This command will only migrate tools catalog tables to a newer version, and cannot be used to convert migrated tools catalog tables to its previous version.

The database must be cataloged before migration. Most of the time, a migration error message is self explanatory, clearly stating the location of the error. If the error message complains about any of the objects such as tables or column names, then the reported objects might be corrupted or missing under the database name submitted for migration.