Installing concurrent online fix pack updates on a Db2 pureScale instance (manual method)

You can update multiple hosts to a higher code level fix pack or special build, in parallel, on a Db2 pureScale instance. These updates can be applied to both members and cluster caching facilities, and are done without impacting availability.

Before you begin

Important: Db2 11.5.8 introduces new support for Db2 pureScale with RDMA on RHEL 8.6. This requires an offline update of the entire cluster to move to Db2 11.5.8 and RHEL 8.6. It is not possible to perform an online update from a lower Db2 12.1 version to Db2 11.5.8 when moving to RHEL 8.6 with RDMA. An existing cluster RDMA running Db2 12.1 on RHEL 7 can be upgraded to Db2 11.5.8 on RHEL 7, using online update.

Using this method, you can manually execute multiple installFixPack commands in parallel from multiple hosts.

Attention: This method is simplified in Db2 11.5.8 and later by using smarter concurrent fix pack update options.

Note: Concurrent online fix pack installation is available in Db2 version 11.5.5 and later.

Ensure that you meet all of the requirements before you install a fix pack. For more information refer to 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 from the new fix pack or special build image location <new_fix_pack_image_location>/<product>/installFixPack. The following is a sample output of that command:

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

Supports online update = Yes

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

The execution completed successfully.

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

About this task

You can update multiple members or multiple members with one cluster caching facilities (CFs) while the remaining members and CFs continue to process transactions. You must update ALL members and CFs 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.

Note: It is recommended to apply concurrent online fix pack updates for one CF and half of the members at a time. For example, if you have 4 members and 2 CFs, you can apply the online fix pack update using two options:

Option 1:

Apply online fix pack update on member 0, 1, and secondary CF at the same time.
Apply online fix pack update on member 2, 3, and primary CF at the same time.

Option 2:

Apply online fix pack update on member 0 and member 1 at the same time.
Apply online fix pack update on member 2 and secondary CF at the same time.
Apply online fix pack update on member 3 and primary CF at the same time.

Procedure

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 to the members or to both the members and CF:

Note: It is up to you how many hosts you want to update at the same time. However, the max number to apply the online fix pack update at the same time is NO more than HALF of the hosts.
1. Log on to the members and/or CFs server with root user authority.
2. When applying a fix pack online on CFs, ensure that you update the secondary CF before the primary CF. Ensure that the secondary CF of your Db2 pureScale instance is in the PEER state by issuing the following command as the instance owner:
```
db2instance -list
```
  The secondary CF must be in the 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.
3. Issue the installFixPack command as follows on the hosts that you want to update (members and/or CF) at the same time (no more than half of the hosts):
```
<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. In addition, the FP-install-path must be a different path than the currently installed Db2 version. The -online parameter is the default and can be omitted.
  If you receive an error message regarding the current version of IBM® Tivoli® System Automation for Multiplatforms (SA MP), IBM Storage Scale or IBM Reliable Scalable Cluster Technology (RSCT) peer domain, this error occurs because the current version of the specified software is different from the version that was previously installed by the Db2 installer. In this case, you can force the installFixPack command to continue the fix pack installation process and force the version update of the specified software. For example, if the error message indicates that the current version of RSCT is different from the RSCT version that was previously installed by the Db2 installer, re-issue the installFixPack command with the -f RSCT parameter. A sample output:
```
<media-dir>/installFixPack -p <FP-install-path> -I <instance-name> -online -l <log-file-name> -t <trace-file-name> -f RSCT
```
  However, when you use the -f parameter to force the fix pack installation to continue, and if you later decide to move back to the previous version of the fix pack by canceling the online fix pack update, the Db2 installer will not able to revert back to the earlier versions of the specified software (RSCT, SA MP or IBM Storage Scale).
4. Repeat Step 2a to Step 2c to apply the fix pack update online on the rest of the hosts (members and/or CFs).
5. If there is a tiebreaker host in the cluster, update the tiebreaker host.
  1. Enter cm maintenance mode from the old code level. For example:
```
export DB2INSTANE=<instance_name>; <OLD-FP-install-path>/bin/db2cluster -cm -enter -maintenance
```
  2. Enter cfs maintenance mode from the old code level. For example:
```
export DB2INSTANCE=<instance_name>; <OLD-FP-install-path>/bin/db2cluster -cfs -enter -maintenance
```
  3. To update the tiebreaker host, run the installFixPack command from the target fix pack image. For example:
```
<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.
    The <FP-install-path> must be the same on all hosts. For example:
    <media-dir>/installFixPack -b /opt/ibm/db2/V11.5 -p /opt/ibm/db2/V11.5M5FP0 -L
  4. Exit cm maintenance mode from the new code level. For example:
```
export DB2INSTANCE=<instance_name>; <FP-install-path>/bin/db2cluster -cm -exit -maintenance
```
  5. Exit cfs maintenance mode from the new code level. For example:
```
export DB2INSTANCE=<instance_name>;  <FP-install-path>/bin/db2cluster -cfs -exit -maintenance
```
  6. Update the IBM Global Security Kit (GSKit) path to the newer fix pack location. For example:
```
/var/db2/db2ssh/db2locssh set_gskit_path <FP-install-path>/lib64/gskit/Copy code
```
  7. Verify that db2locssh is functioning properly. For example, if your system's hostname is "hostT", you can run the hostname command via db2locssh as follows:
```
root@hostT>/var/db2/db2ssh/db2locssh root@hostT hostname
hostT
```
    If all the steps are successful, the fix pack update was successful on the tie-breaker host.
  Note: You can run your workloads for the new fix pack before committing to it, in order to validate its functionality. If this validation is not satisfactory, you can cancel the new fix pack update, and move back to the previous fix pack. For more information, see Canceling online fix pack updates.
6. 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>
```
7. Verify that your instance and databases show the new committed fix pack level. As an instance user, issuing the following command:
```
db2pd -ruStatus
```
8. 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 db2updv115 command as follows:
```
db2updv115 -d db-name
```

Example

The following example illustrates how to use online fix pack updates to update a Db2 pureScale instance (which is called Instance1 in the example) from Db2 version 12.1 GA to Db2 version 11.5.5.

Instance1 has two CFs called cfserver56 and cfserver54, and two members that are called mbserver53 and mbserver55. The command output text is formatted for better reading by removing blanks or adding lines.

The administrator updates mbserver53 and cfserver56 (the secondary CF) at the same time.

Log on to the Db2 database server with root user authority.
Extract the fix pack or special build image in the /local/tmp/M5FP0image directory.

Issue the installFixPack command as follows on mbserver53 and cfserver56 (secondary CF) at the same time:

/local/tmp/M5FP0image/installFixPack -p /opt/ibm/db2/V11.5M5FP0 -I Instance1 -online -l /tmp/V11.5M5FP0.log

Issue the db2pd -ruStatus command to verify that code level changed. The following is a sample of the command output:

ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type              = INSTANCE
   ID                                = 0
   Code Level                 = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   Architecture Level   = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   State                          = [UPDATE IN PROGRESS][ONLINE UPDATE INITIATED]
   Last updated            = 2020/04/14:14:52:36

   Record Type              = MEMBER
   ID                                = 0
   Code Level                = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                           = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                          = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level           = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:15:30:12

mbserver53.torolab.ibm.com: db2pd -ruStat -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type           = MEMBER
   ID                              = 1
   Code Level              = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   CECL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level  = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   CEAL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level          = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Target Code Level  = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   State                        = [NONE]
   Last updated          = 2020/04/14:14:52:24

mbserver54.torolab.ibm.com: db2pd -ruStat -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type            = CF
   ID                              = 128
   Code Level               = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   Architecture Level   = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   Target Code Level   = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:14:52:24

   Record Type            = CF
   ID                              = 129
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                        = [NONE]
   Last updated          = 2020/04/14:15:34:22

The administrator updates mbserver54 and cfserver55 (the primary CF) at the same time.

Log on to the mbserver54 and cfserver56 with root user authority.
Extract the fix pack or special build image in the /local/tmp/M5FP0image directory.

Issue the installFixPack command as follows:

/local/tmp/M5FP0image/installFixPack -online -p /opt/ibm/db2/V11.5M5FP0 -I Instance1 -t trace-file-name -l /tmp/V11.5M5FP0.log

Issue the db2pd -ruStatus command to verify that the code level changed to Db2 version 11.5.5. The following sample shows the command output:

ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type            = INSTANCE
   ID                              = 0
   Code Level               = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   Architecture Level  = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   State                         = [UPDATE IN PROGRESS][ONLINE UPDATE INITIATED]
   Last updated           = 2020/04/14:14:52:36

   Record Type            = MEMBER
   ID                              = 0
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:15:30:12

mbserver53.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type           = MEMBER
   ID                             = 1
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                        = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                          = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level           = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:16:14:12

mbserver54.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type            = CF
   ID                              = 128
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:16:20:44

   Record Type           = CF
   ID                             = 129
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                        = [NONE]
   Last updated          = 2020/04/14:15:34:22

After all members and CFs are updated, the administrator verifies that all members and CFs have the same architecture and code level by issuing the db2pd -ruStatus command. The following sample displays the command output:

ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type            = INSTANCE
   ID                              = 0
   Code Level               = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   Architecture Level  = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     Not Applicable
   State                         = [UPDATE IN PROGRESS][ONLINE UPDATE INITIATED]
   Last updated           = 2020/04/14:14:52:36

   Record Type            = MEMBER
   ID                              = 0
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                         = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:15:30:12

mbserver53.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type           = MEMBER
   ID                             = 1
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                        = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                          = V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)     V:11 R:5 M:0 F:0 I:0 SB:0 (0x0B05000000000000)
   Section Level           = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:16:14:12

mbserver54.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05000000000000,0x0B05000000000000 completed ok

   Record Type            = CF
   ID                              = 128
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:16:20:44

   Record Type           = CF
   ID                             = 129
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                        = [NONE]
   Last updated          = 2020/04/14:15:34:22

The administrator determines that the online fix pack update was successful in all members and CFs by issuing the following command on any host:

/local/tmp/M5FP0image/installFixPack -check_commit -I Instance1 -l /tmp/checkcommit.log

The following sample command output shows that online update was successful and that all members and CF are ready for issuing the commit of the fix pack update:

DBI1446I  The installFixPack command is running.

The pre-commit verification process for an online fix pack update has started....
The checks for the pre-commit verification process have been completed successfully.

If you perform a commit, the new level will be =
   Version:11 Release:5 Modification:5 Fixpack:0

The execution completed successfully.

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

The administrator then commits the online fix pack updates so that Instance1 is updated to the new fix pack level by issuing the following command on any hosts:

/local/tmp/M5FP0image/installFixPack -commit_level -I Instance1 -l /tmp/M5FP0_commit.log

The following command output shows that the commit was successful:

DBI1446I  The installFixPack command is running.

The execution completed successfully.

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

The administrator verifies that Instance1, all members and all CFs show the same new committed code level and architecture level by issuing the db2pd -ruStatus command. The following displays the command output:

ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type           = INSTANCE
   ID                             = 0
   Code Level              = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level  = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                        = [NONE]
   Last updated          = 2020/04/14:16:34:56


   Record Type            = MEMBER
   ID                              = 0
   Code Level               = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Section Level            = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level    = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                          = [NONE]
   Last updated            = 2020/04/14:15:30:12

mbserver53.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05040000000000,0x0B05040000000000 completed ok

   Record Type            = MEMBER
   ID                              = 1
   Code Level                = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CECL                          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   CEAL                          = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Section Level            = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)
   Target Code Level    = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                          = [NONE]
   Last updated            = 2020/04/14:16:14:12

mbserver54.torolab.ibm.com: db2pd -ruStatus -localhost -runremotely -level 0x0B05040000000000,0x0B05040000000000,0x0B05040000000000,0x0B05040000000000 completed ok

   Record Type            = CF
   ID                               = 128
   Code Level               = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                         = [NONE]
   Last updated           = 2020/04/14:16:20:44

   Record Type             = CF
   ID                               = 129
   Code Level                = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Architecture Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   Target Code Level   = V:11 R:5 M:5 F:0 I:0 SB:0 (0x0B05040000000000)     Not Applicable
   State                          = [NONE]
   Last updated            = 2020/04/14:15:34:22

If you want to use capabilities specific to the fix pack, update the system catalog objects in your databases.

Log on as the instance owner.

For each database in the instance, issue the db2updv115 command as follows:

db2updv115 -d testdb


                    _____   DB2 Service Tools   _____

                            I      B      M

                               db2updv115

   This tool is a service utility designed to update a DB2 Version 11.5
   database to the current fix pack level.

________________________________________________________________________


DB2 Universal Database Version 11.5, 5622-044 (c) Copyright IBM Corp. 2017
Licensed Material - Program Property of IBM
IBM DATABASE 2 Database update to current fix pack tool

db2updv115 completed successfully for database 'testdb'.