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.

Since DB2 Connect server products are host database connectivity servers, the only databases that can exist within a DB2 Connect server instance are transaction manager databases and DB2 Connect federated databases. The DB2 Connect transaction manager database stores transaction state information for DB2^® coordinated transactions. The sole purpose of DB2 Connect federated databases is to contain information about data sources.

On Linux^® and UNIX^® platforms, you should manually migrate your DB2 Connect instances after installing DB2 Connect Version 9.5. All the remote nodes and databases that you cataloged on the DB2 clients refer to these instances. If you create a new instance, again you will have to catalog nodes, DCS databases, and databases on the DB2 clients that existed in the Version 9.1 or Version 8 instance.

On Windows^® operating systems, you have an option to automatically migrate an existing DB2 Connect Version 9.1 or Version 8 copy during installation. Your DB2 Connect instances are automatically migrated. Alternatively, you can install a new copy of DB2 Connect Version 9.5 and then manually migrate your DB2 Connect instances.

This procedure describes how to migrate by installing a new copy of DB2 Connect Version 9.5 and then migrate instances and any existing databases. To automatically migrate an existing DB2 Connect Version 9.1 or Version 8 copy on Windows, follow the same steps specified in Migrating a DB2 server (Windows) .

Prerequisites

• Ensure that you have the proper operating system access:

  • Root access on UNIX

  • Local Administrator on Windows

• Ensure that you have SYSADM authority.

• Ensure that you meet the installation requirements for DB2 database products . The requirements for Linux and UNIX operating systems have changed.

• Review the migration recommendations .

• Review the disk space requirements .

• Perform the pre-migration tasks, especially backup your databases.

Restrictions

• The bit size of the client instance is determined by the operating system where you install DB2 Connect. Refer to DB2 Version 9.5 32-bit and 64-bit support for details.

• Additional migration restrictions for DB2 servers also apply to DB2 Connect servers.

For DB2 Connect Version 7, migrate to DB2 Connect Version 8 first. Refer to the following topic for details: http://publib.boulder.ibm.com/infocenter/db2luw/v8/topic/com.ibm.db2.udb.doc/conn/t0008566.htm

1. Export your connectivity configuration information for your DB2 Connect Version 9.1 or Version 8 server to an export profile. Use the db2cfexp tool to create a configuration profile:

      $ db2cfexp cfg_profile backup

   This profile contains all of the instance configuration information, including the database manager configuration and registry profile because the option backup is specified. You can use this profile to recreate your connectivity configuration if necessary.

2. Install DB2 Connect Version 9.5 by running the DB2 Setup wizard and select the option Install New on the Install a Product panel.

3. Migrate your DB2 Connect instances using the db2imigr command.

4. Migrate any existing transaction manager and DB2 Connect federated databases . You can also migrate your databases by restoring a DB2 Connect Version 9.1 or Version 8 backup.

Parent topic: Migration to DB2 Connect Version 9.5

Related concepts
Migration essentials for DB2 servers

Related tasks
Creating links for DB2 files Migrating a DB2 server (Windows) Migrating a DB2 server ( Linux and UNIX )

Related reference
MIGRATE DATABASE command db2imigr - Migrate instance command