IBM Support

"Cluster object does not exist" error on db2start in HADR environment

Troubleshooting


Problem

During db2start on either the primary or standby, SQL5043N is returned.

Symptom

The db2diag.log has a message similar to the one below:

2009-06-22-07.30.31.507790-300 E223695E270 LEVEL: Warning
PID : 20541 TID : 47933176933056PROC : db2star2
INSTANCE: myinst NODE : 000
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaOnlineDB2Partition, probe:71

2009-06-22-07.30.31.573562-300 E223966E377 LEVEL: Error
PID : 20541 TID : 47933176933056PROC : db2star2
INSTANCE: myinst NODE : 000
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaOnlineDB2Partition, probe:70
RETCODE : ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
Cluster object does not exist

Cause

This may be attributed to APAR LI74662.

However, if TSA and/or cluster environment is not currently used, this may be a leftover effect of an unclean removal of a cluster environment that was previously set up.

Environment

Contrary to what the db2diag.log suggests, TSA and/or cluster environment is not used.

Diagnosing The Problem

First, run lssam.

If it doesn't show any clusters defined, then the error message may be a false alarm.

It is possible that the following has happened:


1. A cluster was previously set up on the machines using db2haicu; db2haicu does 3 things:

- set CLUSTER_MGR to TSA in the dbm cfg
- create a db2ha.sys file
- create resources on TSA

2. The cluster was then removed by deleting cluster objects via TSA; lssam then shows no clusters defined, but the first 2 changes listed above were not reversed.

In other words, the cluster objects were not removed cleanly (i.e., did not use db2haicu -delete), and the CLUSTER_MGR=TSA change was left behind.

The only way sqlhaOnlineDB2Partition is invoked on db2start is when CLUSTER_MGR=TSA. It was trying to online cluster resouce, but none exist, so the error was returned.

Resolving The Problem

Check dbm cfg to see if CLUSTER_MGR=TSA. If so, reset this parameter and remove the other leftover cluster settings by running the db2haicu -delete command.

Related Information

SQL5043N

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Database Objects\/Config - Instance","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1","Edition":"Enterprise Server;Express;Personal;Personal Developer's;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21391346

Page Feedback