Migration to DB2 Connect Version 9.5

Upgrading to a new release of DB2 Connect™ might require migration of your environment components if you want them to run on the new release. These components are DB2 Connect servers, DB2^® servers, DB2 clients, and database applications.

For example, if you have an existing environment using DB2 Connect Version 8 and you want to install DB2 Connect Version 9.5, then you can migrate your DB2 Connect server and you might need to migrate other components in your environment.

DB2 Connect Version 9.5 servers supports the migration of DB2 Connect instances, and any existing transaction manager and DB2 Connect federated databases created on DB2 Connect Version 9.1 or Version 8 servers. For DB2 Connect releases prior to DB2 Connect Version 8, you need to migrate first to DB2 Connect Version 8, and then migrate toDB2 Connect Version 9.5. Refer to migrating from previous versions of DB2 Connect for details on how to migrate to DB2 Universal Database (UDB) Version 8.

The migration process consists of all the tasks that you need to perform to have your environment running successfully on a new release. The migration of each of the components in your environment to DB2 Connect Version 9.5 requires that you perform different tasks:

Migrating DB2 Connect servers involves migrating your existing instances, any existing DB2 Connect federated databases, and any existing transaction manager databases so that they can run in DB2 Connect Version 9.5.
Migrating DB2 servers involves migrating your existing instances and databases so that they can run in DB2 Version 9.5.
Migrating DB2 clients involves migrating your client instances to keep the configuration of your existing DB2 clients.
Migrating database applications involves testing them in DB2 Connect Version 9.5 and modifying them only when you need to support changes in DB2 Connect Version 9.5. Review changes in existing functionality and discontinued and deprecated functionality for DB2 Connect in the What's New to determine the changes that could impact your database applications. If your database applications connect to DB2 servers, review also migrating database applications.

The best approach to migration is to write a migration plan. A strategy defines how to approach the migration of your environment and gives you the outline for your migration plan. The characteristics of your environment and the information in migration essentials, especially the migration recommendations and restrictions, can help you determine your strategy. A migration plan should include the following migration details for each component:

Migration prerequisites that indicate all the requirements that you need to meet before migration.
Pre-migration tasks which describe all the preparation tasks that you need to perform before migration.
Migration tasks which describe step by step the basic migration process for a component and how to migrate environments with special characteristics.
Post-migration tasks which describe all the tasks that you need perform after migration to have your DB2 server running at the optimum level.

You will find that pre-migration tasks, migration tasks, and post-migration tasks for DB2 Connect servers reference pre-migration tasks, migration tasks, and post-migration tasks for DB2 servers because they are exactly the same tasks.