Installing online fix pack updates to a higher code level in a GDPC environment

In a geographically dispersed Db2® pureScale® cluster (GDPC) environment, install online fix pack updates on members and cluster caching facilities (CFs) one at a time to update a Db2 pureScale instance to a fix pack or special build with a higher code level while the instance remains available.

Before you begin

Ensure that you meet all of the requirements before you install a fix pack. For more details, see Preparing to install a fix pack.
Ensure that you have root user authority and instance owner authority.

Ensure that online fix pack updates are supported between the Db2 version that is installed on your Db2 pureScale instance and the Db2 version of the fix pack or special build by issuing the installFixPack -show_level_info command. The following text displays the command output:

Code level         =  Version:10 Release:5 Modification:0 Fixpack:4
Architecture level =  Version:10 Release:5 Modification:0 Fixpack:4
Section level      =  Version:10 Release:5 Modification:0 Fixpack:4

Supports online update = Yes

Minimum committed code level required for online install =
   Version:10 Release:5 Modification:0 Fixpack:1

The execution completed successfully.

For more information see the Db2 installation log at "/tmp/installFixPack.log.8541".
DBI1070I  Program installFixPack completed successfully.

Note: IBM support for a geographically dispersed Db2 pureScale cluster (GDPC) implementation requires the engagement of IBM Lab Services for separately charged initial installation services. Contact your IBM sales representative for details.

About this task

In a GDPC environment, you can update one or more members or cluster caching facilities (CFs) while the remaining members and CFs continue to process transactions. You must update all members and CFs, and the tiebreaker host, before you can commit the changes and update the Db2 pureScale instance. If the members and CFs are located on the same host, you must apply the fix pack update only once per host.

Restrictions

Procedure

To install an online fix pack update in a GDPC environment:

Extract the fix pack or special build image to a directory that is accessible to all members and CF hosts.
Apply the fix pack online on each of the members one at a time:
1. Log on to the member server with root user authority.
2. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-install-path is the directory where you want to install the fix pack and media-dir is the directory where you extracted the fix pack image. FP-install-path must be the same on all hosts. The -online parameter is the default and can be omitted.
Apply the fix pack online on the secondary CF:
1. Log on to the secondary CF server with root user authority.
2. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-install-path is the directory where you want to install the fix pack and media-dir is the directory where you extracted the fix pack image. FP-install-path must be the same on all hosts. The -online parameter is the default and can be omitted.
Apply the fix pack online on the primary CF:
1. Ensure that the secondary CF of your Db2 pureScale instance is in PEER state by issuing the following command as the instance owner:
```
db2instance -list
```
  The secondary CF must be in PEER state before updating the primary CF.
  If running db2instance -list shows that the secondary CF is in CATCHUP state, you can check the catch up progress percent by querying the DB2_CF administrative view. For example:
```
db2 "SELECT ID as CF_ID, varchar(CURRENT_HOST,21) AS HOST, varchar(STATE,14) AS CF_STATE FROM SYSIBMADM.DB2_CF" 

CF_ID  HOST             CF_STATE 
------ ---------------  -------------- 
   128 cfserver56       CATCHUP(79%) 
   129 cfserver54       PRIMARY 

  2 record(s) selected. 
```
  The CATCHUP percentage value represents the amount to which the secondary CF is caught up to the current state of the primary CF.
2. Log on to the primary CF server with root user authority.
3. Issue the installFixPack command as follows:
```
media-dir/installFixPack -p FP-install-path -I instance-name -online -l log-file-name -t trace-file-name
```
  Where FP-install-path is the directory where you want to install the fix pack and media-dir is the directory where you extracted the fix pack image. FP-install-path must be the same on all hosts. The -online parameter is the default and can be omitted.
Update the tiebreaker host:
1. Enter maintenance mode from the old code level.
  For example:
```
DB2INSTANCE=<instanceName> <OLD-FP-install-path>/bin/db2cluster -cm -enter -maintenance
<OLD-FP-install-path>/bin/db2cluster -cfs -enter -maintenance
```
2. To update the tiebreaker host, run installFixPack command from the target fix pack image.
```
media-dir/installFixPack -b <OLD-FP-install-path> -p <FP-install-path> -L
```
  Where FP-install-path is the directory where you want to install the fix pack and media-dir is the directory where you extracted the fix pack image. FP-install-path must be the same on all hosts.
  For example:
```
media-dir/installFixPack -b /opt/ibm/db2/V10.5/ -p /opt/ibm/db2/V10.5fp4 -L 
```
3. Exit maintenance mode from the new code level:
  For example:
```
DB2INSTANCE=<instanceName> <FP-install-path>/bin/db2cluster -cm -exit -maintenance
<FP-install-path>/bin/db2cluster -cfs -exit -maintenance
```
  Note: The path in the db2locssh config must be manually updated when a fixpack is installed on the tiebreaker. Otherwise, issues may arise in the future when previous install images are being removed from the system.
Determine whether the online fix pack update was successful on all members and CFs by issuing the following command:
```
media-dir/installFixPack -check_commit -I instance-name 
```
If the command is successful, you can continue with the next step.

Note: If you decide to move back to the previous version of fix pack, you can cancel the online fix pack update. For more information, see Canceling online fix pack updates.
Commit the online fix pack update so that your Db2 pureScale instance is updated to the new fix pack level by issuing the following command:
```
media-dir/installFixPack -commit_level -I instance-name -l log-file-name -t trace-file-name
```
Verify that your instance and databases show the new committed fix pack level by issuing the following command as an instance user:
```
db2pd -ruStatus
```
If you want to use capabilities specific to the fix pack, update the system catalog objects in your databases:
1. Log on as the instance owner.
2. For each database in the instance, issue the db2updv111 command as follows:
```
db2updv111 -d db-name
```