Upgrading your IBM Db2 client instance

For migrating Db2 connections, your Db2 client version must be 11.5.7.0. If you are on an earlier version, upgrade your Db2 client.

Prerequisite steps

Download the Db2 Server fix pack images for your operating system.
  1. On the Db2 Version 11.5 Mod 7 Fix Pack 0 for Linux, UNIX, and Windows support page, expand the section for your operating system and click DB2 Server Fix Pack. Then, look for DB2 11.5.7 Fix Pack 0.
  2. From IBM Passport Advantage, download Db2 Assembly part number G01LWML.

Upgrading your instance

To upgrade your Db2 instance, complete these steps:

  1. Log in to the InfoSphere Information Server repository tier as the root user.
  2. Stop the application server.
    WebSphere Application Server Liberty and stand-alone WebSphere Application Server Network Deployment
    Run the following command:
    <IIS_INSTALL_PATH>/ASBServer/bin/MetadataServer.sh stop
    Clustered WebSphere Application Server Network Deployment
    Stop the cluster as described in WebSphere Application Server Network Deployment: Stopping clusters.
  3. Check installation prerequisites by using the db2prereqcheck command. Run this command in the directory where the installation image is located.
    ./db2prereqcheck -v 11.5.7.0

    Make sure to install any missing prerequisites.

    For more information, see Checking installation prerequisites by using the db2prereqcheck command in the IBM Db2 version 11.5 documentation.

  4. Install the Db2 instance in a new directory by using a response file.
    1. Create response file named db2response.txt with the following content. Replace <New Db2 install path> with the path to the location where you want the new Db2 instance to be installed.
      ******START of Db2 Response file *****************
      LIC_AGREEMENT = ACCEPT
      PROD = DB2_SERVER_EDITION
      FILE  = <New Db2 install path>
      INSTALL_TYPE = TYPICAL
      *-----------------------------------------------
      *  Das properties
      *-----------------------------------------------
      DAS_CONTACT_LIST = LOCAL
      *-----------------------------------------------
      *  Installed Languages
      *-----------------------------------------------
      LANG = EN
      ********END of Db2 Response file *****************
    2. Install the Db2 instance by using the downloaded Db2 images. Run the following command:
       <Db2 download path>/server_dec/db2setup -r <Db2 response file path>db2response.txt -l <path to log file>
    3. Apply the license by running this command:
      <New Db2 install path>/adm/db2licm -a <New Db2 install path>/license/<license file>
      For example:
      /opt/Db2/adm/db2licm -a /opt/DB2/license/db2std_o.lic
  5. Stop and terminate the Db2 instance.
    1. Stop the Db2 instance:
      su - <db2instance> -c ". ./sqllib/db2profile; db2 force application all; db2stop force"
    2. Terminate the Db2 instance:
      su - <db2instance> -c ". ./sqllib/db2profile; db2 terminate"
  6. Change to the instance directory of the new Db2 installation:
    cd <New Db2 install path>/instance
  7. Upgrade the existing Db2 instance:
     ./db2iupdt <db2instance>
  8. To verify that the instance is successfully upgraded, check the Db2 level after the process is complete.
    su - <db2instance> -c ". sqllib/db2profile; db2level"
  9. Start the Db2 instance:
    su - <db2instance> -c ". sqllib/db2profile; db2start"
  10. Update the metadata repository database and the analysis database to latest Db2 version. Replace XMETA and IADB in the following commands with the database names in your deployment:
    su - <db2instance> -c ". sqllib/db2profile; cd <newdb2path>/bin ; db2updv115 -d XMETA"
    su - <db2instance> -c ". sqllib/db2profile; cd <newdb2path>/bin ; db2updv115 -d IADB"
  11. Update the db2path entry in the <IIS_INSTALL_PATH>/Version.xml file with new Db2 instance path.
  12. Start the application server.
    WebSphere Application Server Liberty and stand-alone WebSphere Application Server Network Deployment
    Run the following command:
    <IIS_INSTALL_PATH>/ASBServer/bin/MetadataServer.sh run
    Clustered WebSphere Application Server Network Deployment
    Start the cluster as described in WebSphere Application Server Network Deployment: Starting clusters.
  13. Verify that everything is working as expected.