DB2 - Problem description
Problem IC87849 | Status: Closed |
HOSTNAME CONTAINING THE UNDERSCORE CHARACTER CAUSES SQL1517N DURING DB2START | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
A hostname containing the underscore character '_' causes DB2 to fail to start the instance with the following error code: "SQL1517N db2start failed because the cluster manager resource states are inconsistent." The following diag.log messages are also seen: 2012-04-03-10.37.53.434010+480 I48263A457 LEVEL: Error PID : 4718810 TID : 1 PROC : db2start INSTANCE: db2inst1 NODE : 000 HOSTNAME: xxxxxxxx EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaVerifyClusterObject, probe:16055 MESSAGE : CF parent group nodes does not match CF Control resource DATA #1 : String, 0 bytes Object not dumped: Address: 0x0000000110240810 Size: 0 Reason: Zero-length data 2012-04-03-10.37.53.434379+480 E48721A287 LEVEL: Error PID : 4718810 TID : 1 PROC : db2start INSTANCE: db2inst1 NODE : 000 HOSTNAME: xxxxxxxx EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaVerifyClusterResources, probe:15351 Issuing the "db2instance -list" command will also generate the following error: "The member, CF, or host information could not be obtained. Check the db2diag.log for more information." The following messages will be seen in the diag.log in this case: 2012-04-03-10.10.42.784883+480 I8638A356 LEVEL: Error PID : 5177514 TID : 1 PROC : db2instance INSTANCE: db2inst1 NODE : 000 EDUID : 1 FUNCTION: <0>, <0>, <0>, probe:100 RETCODE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt invalid size" DIA8563C An invalid memory size was requested. 2012-04-03-10.10.42.785260+480 I8995A575 LEVEL: Error PID : 5177514 TID : 1 PROC : db2instance INSTANCE: db2inst1 NODE : 000 EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaDB2HostClustered, probe:6138 RETCODE : ECF=0x9000052E=-1879046866=ECF_SQLHA_FAILED SQLHA API call error DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 0x820F0004 DATA #2 : String, 0 bytes Object not dumped: Address: 0x0FFFFFFFFFFFE3E0 Size: 0 Reason: Zero-length data DATA #3 : String, 8 bytes db2inst1 DATA #4 : unsigned integer, 8 bytes 0 2012-04-03-10.10.42.818217+480 I9571A538 LEVEL: Error PID : 5177514 TID : 1 PROC : db2instance INSTANCE: db2inst1 NODE : 000 EDUID : 1 FUNCTION: DB2 UDB, high avail services, sqlhaSysProcDB2Host, probe:6819 RETCODE : ECF=0x9000052E=-1879046866=ECF_SQLHA_FAILED SQLHA API call error DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 0x00000000 DATA #2 : String, 0 bytes Object not dumped: Address: 0x0FFFFFFFFFFFE3E0 Size: 0 Reason: Zero-length data DATA #3 : unsigned integer, 8 bytes 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of version 10 on Linux, Unix and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: * * A hostname containing the underscore character '_' causes * * DB2 to * * fail to start the instance with the following error code: * * "SQL1517N db2start failed because the cluster manager * * resource * * states are inconsistent." The following diag.log messages * * are * * also seen: * * * * 2012-04-03-10.37.53.434010+480 I48263A457 LEVEL: * * Error * * PID : 4718810 TID : 1 PROC : * * db2start * * INSTANCE: db2inst1 NODE : 000 * * HOSTNAME: xxxxxxxx * * EDUID : 1 * * FUNCTION: DB2 UDB, high avail services, * * sqlhaVerifyClusterObject, probe:16055 * * MESSAGE : CF parent group nodes does not match CF Control * * resource * * DATA #1 : String, 0 bytes * * Object not dumped: Address: 0x0000000110240810 Size: 0 * * Reason: * * Zero-length data * * * * 2012-04-03-10.37.53.434379+480 E48721A287 LEVEL: * * Error * * PID : 4718810 TID : 1 PROC : * * db2start * * INSTANCE: db2inst1 NODE : 000 * * HOSTNAME: xxxxxxxx * * EDUID : 1 * * FUNCTION: DB2 UDB, high avail services, * * sqlhaVerifyClusterResources, probe:15351 * * * * * * Issuing the "db2instance -list" command will also generate * * the * * following error: "The member, CF, or host information could * * not * * be obtained. Check the db2diag.log for more information." * * The * * following messages will be seen in the diag.log in this * * case: * * * * 2012-04-03-10.10.42.784883+480 I8638A356 LEVEL: * * Error * * PID : 5177514 TID : 1 PROC : * * db2instance * * INSTANCE: db2inst1 NODE : 000 * * EDUID : 1 * * FUNCTION: <0>, <0>, <0>, probe:100 * * RETCODE : ZRC=0x820F0004=-2112946172=SQLO_MEM_SIZE "Mem Mgt * * invalid size" * * DIA8563C An invalid memory size was requested. * * * * 2012-04-03-10.10.42.785260+480 I8995A575 LEVEL: * * Error * * PID : 5177514 TID : 1 PROC : * * db2instance * * INSTANCE: db2inst1 NODE : 000 * * EDUID : 1 * * FUNCTION: DB2 UDB, high avail services, * * sqlhaDB2HostClustered, * * probe:6138 * * RETCODE : ECF=0x9000052E=-1879046866=ECF_SQLHA_FAILED * * SQLHA API call error * * DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes * * 0x820F0004 * * DATA #2 : String, 0 bytes * * Object not dumped: Address: 0x0FFFFFFFFFFFE3E0 Size: 0 * * Reason: * * Zero-length data * * DATA #3 : String, 8 bytes * * db2inst1 * * DATA #4 : unsigned integer, 8 bytes * * 0 * * * * 2012-04-03-10.10.42.818217+480 I9571A538 LEVEL: * * Error * * PID : 5177514 TID : 1 PROC : * * db2instance * * INSTANCE: db2inst1 NODE : 000 * * EDUID : 1 * * FUNCTION: DB2 UDB, high avail services, sqlhaSysProcDB2Host, * * probe:6819 * * RETCODE : ECF=0x9000052E=-1879046866=ECF_SQLHA_FAILED * * SQLHA API call error * * DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes * * 0x00000000 * * DATA #2 : String, 0 bytes * * Object not dumped: Address: 0x0FFFFFFFFFFFE3E0 Size: 0 * * Reason: * * Zero-length data * * DATA #3 : unsigned integer, 8 bytes * * 0 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10 Fix Pack 1. * **************************************************************** | |
Local Fix: | |
If possible, change the hostname so that it does not contain the underscore character. Otherwise, contact IBM support. | |
Solution | |
Upgrade to DB2 Version 10 Fix Pack 1. | |
Workaround | |
If possible, change the hostname so that it does not contain the underscore character. Otherwise, contact IBM support. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2012 13.11.2012 13.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |