DB2 FOR LUW / DB2FORLUW / A50 - DB2

If the db2haicu process was killed during resource creation or
if it failed midway through resource creation, it may have left
Db2 resources in an incompletely created state. Subsequently
running the "db2haicu -delete" command to rollback partial
resource creation fails with the following error reported in the
db2diag.log:

2017-11-19-04.11.35.755062+000 E36065817E852         LEVEL:
Error
PID     : 52940                TID : 139737789855520 PROC :
db2haicu
INSTANCE: db2inst1             NODE : 000
HOSTNAME: host01
FUNCTION: DB2 UDB, high avail services,
sqlhaGetParentResourceGroup2, probe:300
MESSAGE :
ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
          Cluster object does not exist
DATA #1 : String, 35 bytes
Error during vendor call invocation
DATA #2 : unsigned integer, 4 bytes
18
DATA #3 : String, 17 bytes
db2_db2inst1_6-rs
DATA #4 : SQLHA Cluster Session Handle,
PD_TYPE_SQLHA_CLUSTER_HANDLE, 4120 bytes
sqlhaClusterHandle->clusterHandle: 1
sqlhaClusterHandle->clusterFlags: 0
sqlhaClusterHandle->clusterErrorNum: 262152
sqlhaClusterHandle->errorMessage: Line # : 17918---2610-407 No
resources found.

sqlhaClusterHandle->clusterCommand:

The db2haicu utility should not fail in this case. It should
proceed to delete partially created resources.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 10 or higher                    *
****************************************************************

If there is only one instance configured for HA, then the
cluster domain can be manually deleted as follows with root
authority:
rmrpdomain -f 

After having manually deleted the cluster domain, the "db2haicu
-delete" command will then successfully complete processing.

not known / see Local fix

forerunner  : IT23400 
follow-up : 

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

15.03.2018
19.07.2018
19.07.2018