DB2 - Problem description
Problem IC99792 | Status: Closed |
VARIOUS DB2HAICU OPERATIONS FAILING IN A CONFIGURATION CONTAINING 50 OR MORE HIGHLY AVAILABLE HADR DATABASES | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * db2haicu users with 50 or more HADR databases * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1.0.4. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 version 10.1.0.4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.03.2014 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |