An attempt to add a new resource to the existing TSA cluster
using db2haicu might fail with ECF_SQLHA_OBJECT_DOES_NOT_EXIST
and following message will logged to db2diag.log:
2016-07-29-12.41.43.877283+060 E41188A718 LEVEL: Error
PID : 12845078 TID : 1 PROC :
db2haicu
INSTANCE: db2depr1 NODE : 000
HOSTNAME: fully.qualified.hostname
EDUID : 1
FUNCTION: DB2 UDB, high avail services, sqlhaAddResourceGroup2,
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
30
DATA #3 : String, 29 bytes
db2___0-rg
DATA #4 : unsigned integer, 4 bytes
1
DATA #5 : unsigned integer, 8 bytes
1
DATA #6 : signed integer, 4 bytes
0
DATA #7 : String, 16 bytes
Line # : 6836---
This might happen when upgrading DB2 from DB2 v10.1 FP3 or older
to DB2 v10.1 FP4 or higher.
Reason: Starting from DB2 v10.1 FP4, the resource names are
defined using the short hostnames (without the domain) instead
of the fully qualified host names. Therefore, after the fix pack
upgrade, DB2 fails to find the new resource names defined using
the short hostnames and returns the
ECF_SQLHA_OBJECT_DOES_NOT_EXIST error.
The existing resource names can be checked by issuing the
following commands:
$ export CT_MANAGEMENT_SCOPE=2
$ lsrsrc IBM.PeerNode Name |
