Migration step 18: Tailor DB2 10 catalog: DSNTIJTC
Job DSNTIJTC invokes the CATMAINT utility to migrate the catalog of the DB2® 9 to the DB2 10 catalog.
Before you begin
You must have appropriate authority to complete this task. For details, see .
Starting in DB2 10, data sets for the DB2 catalog and directory are managed by DB2 and must be SMS-managed. The SMS environment that you use for DB2 catalog and directory data sets must be established before you begin installation or migration to DB2 10. The SMS environment must include a data class for allocating the data sets in extended format and using extended addressability. You are not required to convert existing DB2 catalog and directory data sets to the SMS environment before migrating to DB2 10. These data sets will be converted the next time the related table space is reorganized.
In a data sharing environment, do not run DSNTIJTC after installing non-originating members.
About this task
DSNTIJTC contains one step that creates new catalog and directory objects, adds columns to existing catalog tables, and creates and updates indexes on the catalog tables to accommodate new DB2 10 objects. All IBM-supplied indexes are created or updated sequentially during the execution of DSNTIJTC.
Procedure
To complete the tailoring of the DB2 catalog:
Results
When you start DB2 10 for the first time, you might receive message DSNT501I with reason code 00C900A6. You can ignore this message. Running job DSNTIJTC corrects the cause of this message.
After CATMAINT has run successfully and module DSNICUBC issues message DSNT501I, you can restart your real-time statistics collection by stopping and starting the DSNRTSDB database. In a data sharing group, migrate all members to DB2 10 before stopping and starting the DSNRTSDB database.