DB2 FOR LUW / DB2FORLUW / A50 - DB2

In a pureScale environment, when we delete the resource model 
using the "db2cluster -cm -delete -resources" command, and then 
try to repair the resource model by running the "db2cluster -cm 
-repair -resources" command, it will attempt to create the 
cluster manager resources but fail because it does not find the 
HA registry metadata. Because of this, we end up having to 
manually edit the db2nodes.cfg file and re-creating the cluster 
manager resources manually. To avoid this problem the following 
modifications have been made: 
 
1) The "db2cluster -cm -delete -resources" command will now fail 
if there is a mismatch between the HA registry metadata and the 
contents of the db2nodes.cfg file. The "db2cluster -cm -delete 
-resources -force" command can be used to override this check 
and delete the HA resource model and the HA registry contents in 
this case. 
 
2) The "db2cluster -cm -repair -resources" command will now fail 
if the HA registry metadata does not exist. 
 
3) The "db2cluster -cm -create -resources" command will now fail 
if the HA registry metadata already exists.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Purescale users                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP4                                     * 
****************************************************************

N/A

Fixed in DB2 V10.5 FP4

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

10.04.2014
06.10.2014
16.07.2015