DB2 FOR LUW / DB2FORLUW / 970 - DB2

In a db2haicu HADR configuration containing 50 or more highly 
available HADR databases, various db2haicu operations may fail. 
The db2haicu operations that are affected by this issue are the 
following: 
 
1. Create/delete HADR database 
2. Create HADR Virtual IP address 
3. "db2haicu -disable" 
4. "db2haicu -delete" 
5. db2haicu move option in maintenance mode 
 
In the event that this issue is reproduced, the following two 
db2diag.log messages should be seen when having the DIAGLEVEL 
dbm cfg parameter set to 4: 
 
2014-01-29-11.48.48.882133-300 I88355E371          LEVEL: Info 
PID     : 7762                 TID  : 140737352730368PROC : 
db2haicu 
INSTANCE: db2inst2             NODE : 000 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaGetObjectNames, probe:300 
MESSAGE : Read number of HA resource objects for 
GetObjectNames() 
DATA #1 : unsigned integer, 4 bytes 
112 
 
2014-01-29-11.48.48.882278-300 E88727E358          LEVEL: Error 
PID     : 7762                 TID  : 140737352730368PROC : 
db2haicu 
INSTANCE: db2inst2             NODE : 000 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaListHADR, probe:90 
RETCODE : ECF=0x90000557=-1879046825=ECF_SQLHA_CLUSTER_ERROR 
          Error reported from Cluster 
 
If the value in the data field of the first db2diag.log message 
is greater than or equal to 100 than it confirms this issue. 
 
The following error prompt message is returned from db2haicu: 
 
There was an error with one of the issued cluster manager 
commands. 
Refer to db2diag.log and the DB2 Information Center for details.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HA(TSA) HADR users                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP10                                     * 
****************************************************************

N/A

Fixed in DB2 V9.7 FP10

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC99792 IC99809 
follow-up : 

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

30.01.2014
10.11.2014
10.11.2014

9.7.FP10