This knowledge article is in no way a replacement for the Installation and Configuration Guide for upgrading your cluster to a new level. Its just meant to quickly highlight the steps necessary to perform an upgrade to a newer fixpack level. Any user that is not already familiar with this process is recommended to read the pertinent chapter in the IBM Knowledge Center for TSAMP and the IBM Knowledge Center for DB2.

Please note that this procedure does not cover migrating between DB2 versions, please refer to the DB2 Knowledge Center if you need a procedure to accomplish that task.

TSAMP Support always recommends keeping a backup of you existing policy, please use the 'sampolicy -s' command to backup your current (active) policy before making any changes.

1) In all shells where you will be issuing the commands listed below, export the following environment variable first:

 export CT_MANAGEMENT_SCOPE=2

2) Download the installation media to all nodes in the cluster: DB2 Fix Packs by version of DB2 for Linux, UNIX and Windows

Extract the installation media onto all nodes in the cluster.

3) Stop the cluster/domain with the stoprpdomain command. Use -f if the applications/resources must remain online during the TSAMP upgrade process:

 chrsrc -c IBM.PeerNode CritRsrcProtMethod=5
 stoprpdomain -f <domain_name>

If you do not know the domain name please issue the following command to find the domain name:

 lsrpdomain

4) Install the new DB2 fixpack on all nodes in the cluster and perform any DB2 Upgrade steps required.

5) Start the domain :

 startrpdomain <domain_name>

6) Once the domain is online, verify that MixedVersions=Yes before going further (it may take a few minutes for MixedVersions to switch to Yes so please be patient):

 [root@NC106149 /]# lsrpdomain
 Name       OpState RSCTActiveVersion MixedVersions TSPort GSPort
 hadr_dom   Online  3.2.0.9           Yes           12347  12348

Then complete the migration of RSCT with the following command:

 runact -c IBM.PeerDomain CompleteMigration Options=0

Verify migration complete with 'lsrpdomain' command by ensuring that MixedVersions=No, ensure the version of RSCT shown in the "lsrpdomain" output matches the version of RSCT that is shown on each node in the "lsrpnode" output.

7) Complete the TSAMP migration:

 samctrl -m

Verify migration complete with the following command comparing IVN and AVN:

 lssrc -ls IBM.RecoveryRM | grep -i VN 

8) If you changed the value of CritRsrcProtMethod in the earlier steps, then you should change it back now:

 chrsrc -c IBM.PeerNode CritRsrcProtMethod=3