db2pd -ha can output "Could not retrieve number of Resource
Groups in the cluster"
If you created the TSA cluster outside db2haicu and create
custom resource that include the instance name the db2pd -ha
command can return message reporting unable to retrieve number
of resource groups.
Db2 tries to query these resources because they contain the
instance name and since db2haicu did not set them up it hits an
error. Db2 should ignore these resources since they were set up
by the customer.
example:
$db2pd -ha
DB2 HA Status
Instance Information:
Instance Name = db2inst1
Number Of Domains = 1
Could not retrieve number of Resource Groups in the cluster
db2diag.log:
2018-06-07-15.41.57.754492+000 E1974A591 LEVEL: Error
PID : 6095628 TID : 1 PROC : db2pd
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host
EDUID : 1
FUNCTION: , , , probe:1838
RETCODE :
ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
Cluster object does not exist
DATA #1 : String, 71 bytes
libsqlha: sqlhaGetMemberResourceGroup() call error from wrapper
library
DATA #2 : String, 0 bytes
Object not dumped: Address: 0x000000011150F3FC Size: 0 Reason:
Zero-length data
DATA #3 : signed integer, 4 bytes
0
2018-06-07-15.41.57.755405+000 E2566A392 LEVEL: Error
PID : 6095628 TID : 1 PROC : db2pd
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2host
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaGetMemberResourceGroup, probe:50
RETCODE :
ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
Cluster object does not exist
The customer can work around this by renaming these resources
and removing the instance name. |
