Before you migrate your DB2 Connect™ servers, you need to prepare them for migration to address any issues prior to migration in order to have a successful migration.

1. Review the Migration essentials for DB2 Connect to identify the changes or restrictions that can affect your migration and learn how to address any issues prior to migration.

2. Backing up DB2 server configuration and diagnostic information to have a record of your current configuration that you can compare with the configuration after the migration. You can also use this information to create new instances or databases using the same configuration that you had before migration.

3. Optional: If you enabled the Syncpoint Manager (SPM) functionality on your DB2 Connect server, ensure that the DRDA sync point managers do not contain any indoubt transactions by using the LIST DRDA INDOUBT TRANSACTIONS command to get a list of indoubt transactions and to interactively resolve any indoubt transactions.

4. Optional: If you have transaction manager databases, perform the following pre-migration tasks to prepare your databases for migration:

   1. Ensure that the database to be migrated does not contain any indoubt transactions by using the LIST INDOUBT TRANSACTIONS command to get a list of indoubt transactions and to interactively resolve any indoubt transactions.

   2. Verify that your databases are ready for migration to identify and resolve any problems before the actual migration.

   3. Backing up databases before migration to be able to migrate them to a new migrated system or restore them in the original pre-migration system.

   4. Review the disk space requirements to ensure that you have enough free disk space, temporary table space and log space for database migration and increase table space and log file sizes if necessary.

   5. Linux^® only: Changing raw devices to block devices (Linux)

5. Optional: If you have DB2 Connect federated databases, refer to preparing to migrate to federated systems for details on pre-migrations tasks for these databases.

6. Windows^® only: If you obtained customized code page conversion tables from the DB2 support service, you need to backup all of the files in the DB2OLD\conv directory where DB2OLD is the location of your existing DB2 Connect Version 9.1 or Version 8 copy. Migrating your DB2 Connect Version 9.1 or Version 8 copy removes these tables because standard code page tables are contained in a DB2 Connect Version 9.5 library. You do not need to backup standard code page conversion tables.

7. Optional: Migrate your DB2 Connect server in a test environment to identify migration issues and to verify that database applications and routines work as expected before migrating your production environment.

8. In DB2 Connect Version 9.5, all significant migration events are logged in the db2diag.log file when the diaglevel database manager configuration parameter is set to 3 (default value) or higher. If this parameter is set to 2 or less, set this parameter to 3 or higher before migration.

9. Take the DB2 Connect server offline for migration

Parent topic: Migration to DB2 Connect Version 9.5