Installing online fix pack updates to a higher code level on a Db2 pureScale instance

You can update a Db2 pureScale instance to a higher code level fix pack or special build without impacting availability. You do this by installing online fix pack updates on members and cluster caching facilities (CF) one at a time.

Before you begin

  • Ensure that you meet all of the requirements before you install a fix pack. For more information, 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 from the new fix pack or special build image location <new_fix_pack_image_location>/<product>/installFixPack. The following text displays the sample command output:
    Code level = Version:10 Release:5 Modification:0 Fixpack:1
Architecture level = Version:10 Release:5 Modification:0 Fixpack:1
Section level = Version:10 Release:5 Modification:0 Fixpack:1

Supports online update = Yes

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

The execution completed successfully.

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

About this task

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 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.

Procedure

To install an online fix pack update on a Db2 pureScale instance:

  1. Extract the fix pack or special build image to a directory that is accessible to all members and CF hosts.
  2. Apply the fix pack online to each of the members, one at a time.
    Note: If a CF is also located on the same host as the member, you can skip this step for the host, since it will be updated in Step 3 or 4.
    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. 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), 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, reissue the installFixPack command with the -f RSCT parameter: 
      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, later if you decide to move back to the previous version of the fix pack by canceling the online fix pack update, the Db2 installer is not able to revert the specified software (RSCT, SA MP or IBM Storage Scale) to the same earlier version.

      Ensure you apply the fix packs to each member before you continue with the next step.

  3. 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. 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.
  4. 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.
  5. If there is a tiebreaker host in the cluster, 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; DB2INSTANCE=<instanceName> <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:
      <FP-install-path>/bin/db2cluster -cm -exit -maintenance <FP-install-path>/bin/db2cluster -cfs -exit -maintenance
    4. 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/
    5. 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 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 by issuing the following command as an instance user: 
    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 that is called Instance1 from version 10.5 Fix Pack 3 to Db2 Cancun Release 10.5.0.4. 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.
  1. The administrator updates mbserver53:
    1. Log on to the Db2 database server with root user authority.
    2. Extract the fix pack or special build image in the /local/tmp/FP4image directory.
    3. Issue the installFixPack command as follows:
      /local/tmp/FP4image/installFixPack -p /opt/ibm/db2/V10.5FP4 -I Instance1
                                           -online -l /tmp/FP4log_mbserver53
    4. Issue the db2pd -ruStatus command to verify that code level changed. The following text displays the command output:
      ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type        = INSTANCE
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   State              = [NONE]
   Last updated       = 2013/04/18:02:58:58


   Record Type        = MEMBER
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:07:59:48

mbserver53.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = MEMBER
   ID                 = 1
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:05:12:20

mbserver55.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = CF
   ID                 = 128
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:31:14

   Record Type        = CF
   ID                 = 129
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:25:55
  2. The administrator updates the secondary CF cfserver56:
    1. Log on to the cfserver56 with root user authority.
    2. Extract the fix pack or special build image in the /local/tmp/FP4image directory.
    3. Issue the installFixPack command as follows:
      /local/tmp/FP4image/installFixPack -online -p /opt/ibm/db2/V10.5FP4 -I Instance1 -t trace-file-name
                                            -l /tmp/FP4log_cfserver56
    4. Issue the db2pd -ruStatus command to verify that the code level changed to Db2 Cancun Release 10.5.0.4. The following text displays the command output:
      ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type        = INSTANCE
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   State              = [NONE]
   Last updated       = 2013/04/18:02:58:58


   Record Type        = MEMBER
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:01:57:35

mbserver53.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = MEMBER
   ID                 = 1
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:05:12:20

mbserver55.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = CF
   ID                 = 128
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Last updated       = 2013/04/18:02:58:52

   Record Type        = CF
   ID                 = 129
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:25:55
  3. The administrator updates the primary CF server (cfserver54):
    1. The administrator verifies that the secondary CF server (cfserver56) is in PEER state by logging in as instance owner and issuing the following command:
      db2instance -list
      The command output shows that the cfserver56 is in PEER state:
      ID    TYPE STATE    HOME_HOST  CURRENT_HOST ALERT PARTITION_NUMBER LOGICAL_PORT NETNAME
--    ---- -----    ---------  ------------ ----- ---------------- ------------ -------
0   MEMBER  STARTED mbserver53 mbserver53      NO                0            0 mbserver53-ib0
1   MEMBER  STARTED mbserver55 mbserver55      NO                0            0 mbserver55-ib0
128 CF      PRIMARY cfserver54 cfserver54      NO                -            0 cfserver54-ib0
129 CF      PEER    cfserver56 cfserver56      NO                -            0 cfserver56-ib0

HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT
--------                   -----                ----------------        -----
cfserver56                ACTIVE                              NO           NO
cfserver54                ACTIVE                              NO           NO
mbserver55                ACTIVE                              NO           NO
mbserver53                ACTIVE                              NO           NO
    2. Log on to the Db2 database server with root user authority.
    3. Extract the fix pack or special build image in the /local/tmp/FP4image directory.
    4. Issue the installFixPack command as follows:
      /local/tmp/FP4image/installFixPack -p /opt/ibm/db2/V10.5FP4 -I Instance1
                                           -online -l /tmp/FP4log_cfserver54
    5. Issue the db2pd -ruStatus command to verify that the code level changed. The following text displays the command output:
      ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type        = INSTANCE
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   State              = [NONE]
   Last updated       = 2013/04/18:02:58:58


   Record Type        = MEMBER
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:01:57:35

mbserver53.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = MEMBER
   ID                 = 1
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:05:12:20

mbserver55.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = CF
   ID                 = 128
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:31:14

   Record Type        = CF
   ID                 = 129
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:25:55
  4. After all members 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 text displays the command output:
    ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type        = INSTANCE
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     Not Applicable
   State              = [NONE]
   Last updated       = 2013/04/18:02:58:58


   Record Type        = MEMBER
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:07:59:48

mbserver53.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = MEMBER
   ID                 = 1
   	Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CECL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CEAL               = V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)     V:10 R:5 M:0 F:3 I:0 SB:0 (0x0A05000300000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:09:24:18

mbserver55.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = CF
   ID                 = 128
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:31:14

   Record Type        = CF
   ID                 = 129
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:25:55
  5. The administrator determines that online fix pack update was successful in all members and CFs by issuing the following command:
    /local/tmp/FP4image/installFixPack -check_commit -I Instance1
                                            -l /tmp/checkcommit.log
    The following 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:10 Release:5 Modification:0 Fixpack:4

The execution completed successfully.

For more information see the Db2 installation log at "/tmp/FP4_checkcommit.log".
DBI1070I  Program installFixPack completed successfully.
  6. 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:
    /local/tmp/FP4image/installFixPack -commit_level -I Instance1
                                            -l /tmp/FP4_commit.log
    The following command output shows the commit was successful:
    DBI1446I  The installFixPack command is running.

The execution completed successfully.

For more information see the Db2 installation log at "/tmp/FP4_commit.log".
DBI1070I  Program installFixPack completed successfully.
  7. The administrator verifies that Instance1, members, and CFs show the same new committed code level and architecture level by issuing the db2pd -ruStatus command. The following text displays the command output:
    ROLLING UPDATE STATUS:  Disk Value                                         Memory Value

   Record Type        = INSTANCE
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   State              = [NONE]
   Last updated       = 2013/04/18:08:58:21


   Record Type        = MEMBER
   ID                 = 0
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CECL               = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CEAL               = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:07:59:48

mbserver53.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = MEMBER
   ID                 = 1
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CECL               = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   CEAL               = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)
   Section Level      = V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)     V:10 R:5 M:0 F:0 I:0 SB:0 (0x0A05000000000000)
   Last updated       = 2013/04/18:09:24:18

mbserver55.domain.com: db2pd -ruStatus -localhost ... completed ok

   Record Type        = CF
   ID                 = 128
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:31:14

   Record Type        = CF
   ID                 = 129
   Code Level         = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Architecture Level = V:10 R:5 M:0 F:4 I:0 SB:0 (0x0A05000400000000)     Not Applicable
   Last updated       = 2013/04/18:07:25:55