Installing a fix pack in a Microsoft Cluster Server environment (Windows)

Follow these instructions to install a fix pack on top of an existing Db2® installation in a Microsoft Cluster Server (MSCS) environment.

Before you begin

  • Ensure that you meet all of the necessary tasks before installing a fix pack. Refer to Preparing to install a fix pack.
  • Ensure that you have the appropriate installation user accounts. In general, the user account must belong to the Administrators group on the machine where you will perform the installation.

About this task

To illustrate how to install a fix pack in an MSCS environment, a simple example configuration must be understood. In this example, the initial configuration is a Db2 instance that is composed of two database partitions. In addition, there are two Cluster Groups:
  • Db2 Group 0: contains Partition 0 active on Machine A. The Db2 Administration Server (DAS) is also located here.
  • Db2 Group 1: contains Partition 1 active on Machine B.
This is the initial configuration.

Procedure

To install a fix pack on top of an existing Db2 installation in an MSCS environment, you must do the following steps while offline:

  1. Decluster the MSCS to place the instance back to the local host with the following command:
    db2mscs -u <instance_name>

    Run db2ilist to make sure that the instance no longer points to a shared location.

  2. Stop the Db2 instance on the host that originally has the Db2 instance created.

    For example, on Machine A, use the db2stop command to stop the Db2 instance.

  3. Db2 on both Machine A and Machine B can now be updated.

    If there are multiple Db2 database products installed at the same location (in the same Db2 copy) on Machine B, install the fix pack for multiple database products. Otherwise, install the fix pack for a single database product.

    Refer to Installing a fix pack for multiple database products (Windows) or Installing a fix pack for a single database product (Windows), as appropriate.

    Note:
    • As part of the installation process, you might have to restart your computer.
    • The silent mode installation process can optionally be used to install the fix pack using a response file. Refer to Installing a fix pack using a response file (Windows).
    • If db2systray.exe attempts to access an offline instance, then you might receive error message SQL5005C near the end of installation. This does not indicate an installation failure.
  4. Recluster the MSCS cluster with the following command:
    db2mscs -f <path_to_mscs.cfg>

    Refer to db2mscs - Set up Windows failover utility command

What to do next

To complete the installation, perform the necessary post-installation tasks for fix packs. Refer to Post-installation tasks for fix packs (Windows).