DB2 Version 9.7 for Linux, UNIX, and Windows

Upgrading to Data Server Client (Windows)

Upgrading an existing client copy to DB2® Version 9.7 requires that you install a Version 9.7 Data Server Client copy and then upgrade your client instance to retain your client configuration and to connect to all your previously cataloged databases.

About this task

When you install a Version 9.7 Data Server Client, you can choose to automatically upgrade an existing pre-Version 9.7 client copy. Your existing client instances are upgraded to a new Version 9.7 Data Server Client copy and the existing pre-Version 9.7 client copy is removed. You can also choose to install a new copy of Version 9.7 Data Server Client and then manually upgrade your existing client instance after installation.

Restrictions

Before you begin

Procedure

To upgrade from an existing client copy to a Version 9.7 Data Server Client on Windows:

  1. Install Version 9.7 Data Server Client by running the setup command to launch the DB2 Setup wizard. You have three choices:

    • Select the Work with Existing option on the Install a Product panel. Then in the Work with an existing DB2 copy window, select a client copy name with action upgrade. The selected DB2 copy is removed and your client instance is upgraded. You can choose this option, if you have an existing copy of Version 8 Administration Client, Version 8 Application Development Client, Version 9.1 Client, or Version 9.5 Data Server Client.

    • Select the Install New option in the Install a Product panel. You should choose this option to create a new copy of Version 9.7 Data Server Client and keep your existing client copy. After installation, you must manually upgrade the client instance to run on the Version 9.7 Data Server Client copy:
      • Log on to the system as a user with Local Administrator authority.
      • Run the db2iupgrade command:
           "%DB2PATH%"\bin\db2iupgrade InstName
        where DB2PATH is set to the location that you specified during the Version 9.7 Data Server Client installation and InstName is the name of the instance.
    • Select the Work with Existing option on the Install a Product panel. Then in the Work with Existing window, choose the client copy name with the upgrade action. Finally, in the Select the installation, response file creation, or both window, select the Save my installation setting in a response file option to create a response file for a response file installation. The response file has the required UPGRADE_PRIOR_VERSIONS keyword, the client copy name to upgrade, and the installation path.

      The result of the response file installation will be the same as in the first choice, all your client instances running on the selected client copy are automatically upgraded to the Version 9.7 Data Server Client copy. Using a response file installation to upgrade your clients can help you automate the upgrade process when you have a large number of clients.

  2. If you want your applications to use the Version 9.7 Data Server Client copy through the default interface or if you upgraded your existing Version 8 client copy, set the Version 9.7 Data Server Client copy as the DB2 default copy.
  3. Optional: You can create a new Version 9.7 client instance instead of upgrading the existing client instance. You only need to create a new Version 9.7 client instance when you want to keep multiple client copies running on the same machine, or create a testing environment. To create a new Version 9.7 client instance, run the db2icrt command with the option -s:
       "%DB2PATH%"\bin\db2icrt -s client InstName
    To create the same client connectivity environment you had, including the database manager configuration parameter and DB2 profile registry settings, run the db2cfimp command with the configuration profile that you save in the pre-upgrade tasks.
  4. Compare the upgraded database manager configuration parameter values with the pre-upgrade values to ensure the changed values are compatible with your database applications.

What to do next

After upgrading your client, perform the recommended post-upgrade tasks for DB2 clients, especially verifying upgrade for clients to ensure that your client upgrade was successful.