After migrating your DB2 Connect™ servers, you should perform several post-migration tasks to ensure that your DB2 Connect servers perform as expected and run at their optimum level.

1. If you set the diaglevel database manager configuration parameter to 4 as recommended in the pre-migration tasks for DB2 Connect servers, reset this parameter to the value set before the migration.

2. Manage changes in DB2 server behavior . There are new registry variables, new configuration parameters, and new default values for registry variables and configuration parameters introduced in DB2 Version 9.5 that can impact the behavior of DB2 server. There are also changes in physical design characteristics of databases and changes to security that also have an impact.

3. If you obtained customized code page conversion tables from the DB2 support service for Version 9.1 or Version 8, copy all of the files for those tables from the DB2OLD/conv to DB2DIR/conv, where DB2OLD is the location of your DB2 Connect Version 9.1 or Version 8 copy and DB2DIR is the location of your DB2 Connect Version 9.5 copy. You do not need to copy standard code page conversion tables.

   If you migrated your existing DB2 Connect Version 9.1 or Version 8 copy on Windows^® operating systems, you can restore the customized code page conversion tables that you backed up as part of the pre-migration tasks for DB2 Connect servers to the DB2PATH\conv directory, where DB2PATH is the location of your DB2 Connect Version 9.5 copy.

4. Optional: If you migrated any databases in your DB2 Connect server and changed the log space setting as recommended in the pre-migration tasks for DB2 Connect servers, adjust the log space size . Ensure that the amount of log space that you allocate is adequate for your DB2 Connect server.

5. Optional: Back up your databases after the migration is complete.

6. Optional: If you have DB2 Connect federated databases, review configuring federated systems after migration to determine if you need to perform any tasks after you migrate your federated databases.

7. Verify that your DB2 Connect server migration was successful. Test connections to all your cataloged databases. The following example shows how to test a connection from the Command Line Processor (CLP):

      db2 CONNECT TO DATABASE sample user mickey using mouse

   You need to specify a user and password when connecting to a remote database. Ensure all connections are successful.

   Also, test your applications and tools to ensure that the DB2 Connect server is working as expected.

At this point, you should resume all of your maintenance activities. You should also remove any DB2 Connect Version 9.1 or Version 8 copies that you no longer need.

Parent topic: Migration to DB2 Connect Version 9.5