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.

To install a fix pack on top of an existing DB2 installation in an MSCS environment:

1. Set automatic failback to off.

   During the installation process you might have to restart your machine. When this happens the cluster service restarts automatically. Therefore the automatic failback must be set off so none of the groups automatically failback.

   For example, to disable automatic failback in DB2 Group 0:

   1. From the Cluster Administrator window, right-click DB2 Group 0.
   2. Select Properties. The DB2 Group 0 Properties window opens.
   3. On the Failback tab, select the Prevent failback radio button.
   4. Click OK.

   Repeat these steps to disable automatic failback in DB2 Group 1.

2. Decide which machine you will install the fix pack on first.

   In this example, Machine B will be upgraded first.

3. Move the DB2 Group off Machine B.

   For example, to move DB2 Group 1 from Machine B to Machine A:

   1. From the Cluster Administrator window, click DB2 Group 1.
   2. Right-click, select Move Group. The Owner column changes to Machine A.
4. Stop the cluster server on Machine B.

   For example:

   1. From the Component Services window, right-click Cluster Service.
   2. Click Stop.
5. 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:

   • DB2 is still running and available on Machine A.
   • 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.
6. Take the DB2 resources offline.

   In the example, Partition 0, Partition 1, and the DAS are on Machine A at this point. These must be taken offline one at a time. For example:

   1. From the Cluster Administrator window, in the left window panel, select Groups.
   2. Select DB2 Group 0. The resources for the group display in the right window panel.

      For DB2 Group 0, the DB2 resources include Partition 0 and the DAS.

   3. In the right window panel, right-click one of the resources. Select Take Offline.

      Repeat this step for each of the DB2 resources in DB2 Group 0.

   4. Select DB2 Group 1. The resources for the group display in the right window panel.

      For DB2 Group 1, the DB2 resources include Partition 1.

   5. In the right window panel, right-click the resource (Partition 1). Select Take Offline.
7. (Optional) Restart the cluster service on Machine B.

   If the fix pack installation required that you restart your computer, and if the Restart Type for the cluster service is set to automatic, skip this step because the cluster service is already started.

   To start the cluster service:

   1. From the Component Services window, right-click Cluster Service.
   2. Click Start.
8. Move the DB2 Groups to Machine B.

   For example, to move DB2 Group 0 and DB2 Group 1 to Machine B:

   1. From the Cluster Administrator window, click DB2 Group 0.
   2. Right-click, select Move Group. The Owner column changes to Machine B.
   3. Click on DB2 Group 1.
   4. Right-click, select Move Group. The Owner column changes to Machine B.
9. Bring the DB2 resources online.

   In the example, Partition 0, Partition 1, and the DAS are on Machine B at this point. These must be brought back online one at a time. For example:

   1. From the Cluster Administrator window, in the left window panel, select Groups.
   2. Select DB2 Group 0. The resources for the group display in the right window panel.

      For DB2 Group 0, the DB2 resources include Partition 0 and the DAS.

   3. In the right window panel, right-click one of the resources. Select Bring Online.

      Repeat this step for each of the DB2 resources in DB2 Group 0.

   4. Select DB2 Group 1. The resources for the group display in the right window panel.

      For DB2 Group 1, the DB2 resources include Partition 1.

   5. In the right window panel, right-click the resource (Partition 1). Select Bring Online.
10. Stop the cluster service on Machine A.

    For example:

    1. From the Component Services window, right-click Cluster Service.
    2. Click Stop.
11. If there are multiple DB2 database products installed at the same location (in the same DB2 copy) on Machine A, 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:

    • DB2 is still running and available on Machine B.
    • 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.
12. (Optional) Restart the cluster service on Machine A.

    If the fix pack installation required that you restart your computer, and if the Restart Type for the cluster service is set to automatic, skip this step because the cluster service is already started.

    To start the cluster service:

    1. From the Component Services window, right-click Cluster Service.
    2. Click Start.
13. Move the DB2 Groups back to the appropriate machines.

    For example, to move DB2 Group 0 back to Machine A:

    1. From the Cluster Administrator window, click DB2 Group 0.
    2. Right-click, select Move Group. The Owners column changes to Machine A.
    This brings the MSCS environment back to the initial configuration.
14. If automatic failback was turned off in Step 1, turn it back on.

    For example, to start automatic failback in DB2 Group 0:

    1. From the Cluster Administrator window, right-click DB2 Group 0.
    2. Select Properties. The DB2 Group 0 Properties window opens.
    3. On the Failback tab, select the Allow failback radio button.
    4. Click OK.

    Repeat these steps to start automatic failback in DB2 Group 1.