Upgrading to the latest version of Db2 Connect

Upgrading to a new version or release of Db2 Connect might require upgrading your environment components if you want them to run on the new release. These components are Db2 Connect Server, Db2® servers, Db2 clients, and database applications.

For example, if you have an existing environment using an earlier version or release of Db2 Connect and you want to install the latest version or release of Db2 Connect, then you can upgrade your Db2 Connect Server and you might need to upgrade other components in your environment.

Db2 Connect servers supports the upgrading of Db2 Connect instances, and any existing transaction manager and Db2 Connect federated databases created on previous versions of Db2 Connect Server.

The upgrade process consists of all the tasks that you need to perform to have your environment running successfully on a new release. The upgrading of each of the components in your environment to the latest version or release of Db2 Connect requires that you perform different tasks:
  • Upgrading Db2 Connect servers involves upgrading your existing instances, any existing Db2 Connect federated databases, and any existing transaction manager databases so that they can run in the latest version or release of Db2 Connect.
  • Upgrading IBM® Data Server client packages involves upgrading your client instances to keep the configuration of your existing IBM Data Server client packages.
  • Upgrading database applications involves testing them in the latest version or release of Db2 Connect and modifying them only when you need to support changes available in the latest version or release of Db2 Connect.

    Review changes in existing functionality and discontinued and deprecated functionality for Db2 Connect in Db2 enhancements and changes that affect Db2 Connect(tm) to determine the changes that could impact your database applications. If your database applications connect to Db2 servers, you might need to upgrade your database applications.

  • Consideration toward Db2 Connect client, instead of Db2 Connect Server, to receive equivalent or superior function. You can reduce complexity, improve performance, and deploy application solutions with smaller footprints. For details, see the topic about client/server connection options.
The best approach to upgrading is to write an upgrade plan. A strategy defines how to approach the upgrading of your environment and gives you the outline for your upgrade plan. The characteristics of your environment and the information in upgrade essentials, especially the upgrade recommendations and restrictions, can help you determine your strategy. An upgrade plan should include the following upgrade details for each component:
  • Upgrade prerequisites that indicate all the requirements that you need to meet before upgrading.
  • Pre-upgrade tasks which describe all the preparation tasks that you need to perform before upgrading.
  • Upgrade tasks which describe step by step the basic upgrade process for a component and how to upgrade environments with special characteristics.
  • Post-upgrade tasks which describe all the tasks that you need perform after upgrading to have your Db2 server running at the optimum level.
  • Review the need to opt for Db2 Connect client, instead of Db2 Connect Server, to receive equivalent or superior function.
You will find that pre-upgrade tasks, upgrading tasks, and post-upgrade tasks for Db2 Connect Server reference pre-upgrade tasks, upgrading tasks, and post-upgrade tasks for Db2 servers because they are exactly the same tasks.