Installing offline fix pack updates to a Db2 pureScale instance (manual method)

You can install offline fix pack updates to a Db2 pureScale instance by using the manual method. This method was traditionally used for updating an existing Db2 pureScale instance to the latest fix pack level.

Important: This method is deprecated. Use the Installing offline fix pack updates to a Db2 pureScale instance (simplified method) instead.

Before you begin

Ensure that you meet all of the requirements before you install a fix pack. Refer to Preparing to install a fix pack.
Ensure that you are logged in as root.
The instance must be offline.

About this task

For Db2 pureScale instances, if you use the manual method with the installFixPack command, you must manually update the IBM® Tivoli® System Automation for Multiplatforms (SA MP) if it was not installed by Db2 installer. Also, if the cluster has user managed IBM Spectrum Scale software level you must manually update IBM Spectrum Scale in addition to the Db2 fix pack updates. The new capabilities in the installFixPack command include automatic updates of the SA MP and GPFS software levels. For more information, see Installing offline fix pack updates to a Db2 pureScale instance (simplified method).

Procedure

To update an existing Db2 pureScale instance to a new fix pack level, follow these instructions.

Determine the level of SA MP on your installation and on the installation media, to verify if both are at the same level.
1. Query the SA MP Base Component level that is already installed on your system, by issuing the following command:
```
<image_path>/db2/<platform>/tsamp/db2cktsa -v install
```
2. Query the SA MP Base Component level on the installation media, by issuing the following command:
```
<image_path>/db2/<platform>/tsamp/db2cktsa -v media
```
Determine the level of IBM Spectrum Scale installed, to verify if both are at the same level
1. Query the level of GPFS that is already installed on your system, by issuing the following command:
```
<image_path>/db2/<platform>/gpfs/db2ckgpfs -v install
```
2. Query the level of GPFS on the installation media, by issuing the following command:
```
<image_path>/db2/<platform>/gpfs/db2ckgpfs -v media
```
Disconnect all applications and users by issuing the following command:
```
db2 force application all
```
Stop the Db2 instance on all members and CFs by issuing the following command on a single host:
```
su - <InstName>
db2stop
exit
```
where InstName represents the instance owner name.
If the db2stop command is not successful and fails to stop the database manager instance, issue the following command:
```
 db2stop force
```
If either the level of SA MP Base Component or the level of GPFS software on the installation media is higher than the level already installed on your system, the Db2 cluster services administrator must place all members and CFs into maintenance mode. To stop the instance on each host, issue the following command:
```
db2stop instance on hostname
where hostname represents the host name for a member or CF.
```
To place the host into maintenance mode, enter the db2cluster command on one host in the Db2 pureScale environment:
```
DB2DIR/bin/db2cluster -cm -enter -maintenance -all
```
where DB2DIR represents the installation location of your Db2 copy.
If the level of GPFS on the installation media is higher than the level already installed on your system, the Db2 cluster services administrator must place the host into maintenance mode. To place the host into maintenance mode, enter the db2cluster command on one host in the Db2 pureScale environment:
```
DB2DIR/bin/db2cluster -cfs -enter -maintenance -all
```
where DB2DIR represents the installation location of your Db2 copy.
On each host, apply the fix pack to the new location by issuing the following command:
```
media-dir/installFixPack -p FP-install-path
```
where media-dir is the directory where you extracted the fix pack image, and FP-install-path is the new fix pack level installation location of your Db2 copy.
Note:
If you are applying the fix pack to a Db2 pureScale instance type, the path that is specified in the -p parameter must be different from the path that is specified in the -b parameter as shown in the following example:
```
media-dir/installFixPack -L -b /opt/IBM/db2/V10.5 -p /opt/IBM/db2/V10.5fp4 
```
If the Db2 cluster services administrator placed the SA MP Base Component host into maintenance mode, the Db2 cluster services administrator must remove the host from maintenance mode. To remove the SA MP Base Component host from maintenance mode, enter the db2cluster command on one host in the Db2 pureScale environment:
```
FP-install-path/bin/db2cluster -cm -exit -maintenance -all
```
where FP-install-path represents the new fix pack level installation location of your Db2 copy.
If the Db2 cluster services administrator placed the GPFS host into maintenance mode, the Db2 cluster services administrator must remove the host from maintenance mode. To remove the GPFS host from maintenance mode, enter the db2cluster command on one host in the Db2 pureScale environment:
```
FP-install-path/bin/db2cluster -cfs -exit -maintenance -all
```
where FP-install-path represents the new fix pack level installation location of your Db2 copy.
On each host, update the instance to the new installation path:
```
FP-install-path/instance/db2iupdt Instname
```
where FP-install-path represents the new fix pack level installation location of your Db2 copy and InstName specifies the name of the instance.
For example, /opt/IBM/db2/V10.5fp4/instance/db2iupdt db2inst1.
The Db2 cluster services administrator must commit the updates that are made to Db2 cluster services and make them available to the Db2 database system. On one host, run the db2cluster commands:
```
FP-install-path/bin/db2cluster -cfs -commit
FP-install-path/bin/db2cluster -cm -commit
```
where FP-install-path represents the new fix pack level installation location of your Db2 copy.
Commit the Db2 DBMS instance to the new level by issuing the installFixPack command on one host as follows:
```
media-dir/installFixPack  -commit_level -I Instname  -l /tmp/commit.log
```
where media-dir is the directory where you extracted the fix pack image.
To start the Db2 instance, run the db2start command on each host in the Db2 pureScale environment
```
su - Instname
db2start instance on host-name
```
where Instname represents the instance name, and host-name represents the host name for a member or CF. The db2start instance on hostname command is run for each host in the cluster.
The following steps are applicable if performing an offline fix pack update from V11 GA to V11.1 FP1:
1. Refresh the resource model as the instance owner:
```
db2cluster -cm -repair –resources
```
2. Ensure that the cluster manager resource states for the Db2 instance are in a consistent state:
```
db2cluster -cm -verify –resources
```
3. As a root user, rebuild the contents of the network resiliency condition and response resources in the cluster by issuing the db2cluster -cfs -repair -network_resiliency -all command. You can issue the command only once from any member or CF in the cluster:
```
FP-install-path/bin/db2cluster -cfs -repair -network_resiliency -all
```
  where FP-install-path is the Db2 Fix pack installation path.
To start the database manager, run the db2start command:
```
su - Instname
db2start
exit
```
where Instname represents the instance name.
To uninstall the previously installed Db2 copy, run the db2_deinstall command:
```
DB2DIR/install/db2_deinstall -a
```
where DB2DIR is the installation path of the previously installed Db2 copy.