Basis Errors and Solutions

Symptom

AFTER MIGRATING A DB2 INSTANCE IN MSCS THE DB2CLUSTERLIST WILL NOT INCLUDE BOTH NODES, WHICH CAUSES THE FAILOVER TO FAIL.
Other terms

v9.5 migration , MSCS instance
Reason and Prerequisites

DB2 V9.5 GA or any FixPak below FixPak 5 can hit this APAR in MSCS env under Windows O/S.
After migrating a DB2 Instance used within MSCS the failover will fail. This will occur when migrating from v8/v9.1 to v9.5 using the migration steps outlined in the DB2 9.5 Information Centre for Linux, UNIx, and Windows. During the migration the MSCS nodes in the cluster defined by the DB2 Registry Varialbe, DB2CLUSTERLIST, will not be correct. Due to this a failure occurs during the failover since the list does not include both nodes in the cluster.
Solution

APAR JR33479 will be fix in DB2 V9.5 FixPak 5.
LOCAL FIX:
After migrating the DB2 Instance manually include the missing MSCS node using the db2iclus.exe tool to update the DB2 Registry variable DB2CLUSTERLIST.
The command to ran is:
db2iclus add /m: