DB2 - Problem description
Problem IT25519 | Status: Closed |
db2instance & db2haicu might fail with a SEGV in sqlhaGetInfoForClusterObject if route or IPv4 IP is not assigned to NIC | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Db2 tools accessing network interface (NIC) information, db2haicu and db2instance, might fail with a segmentation fault (memory fault/SEGV), if: - there is a NIC, which doesn't have an IPv4 address assigned or: - there is no routes associated with one of the interfaces For db2haicu, tool will fail on network configuration stage (e.g. network tiebreaker setup), for db2instance, "db2instance -list" will be affected. If system is configured to dump a core (ulimit -c unlimited), the core dump will show the following functions on the top of the stack: db2haicu: sqlhaGetInfoForClusterObject sqlhaUIListAllNICsInClus db2instance: sqlhaGetInfoForClusterObject sqlhaCheckNetworkAdapterOnHost Db2 V11.1 Mod3 Fix Pack 3 and both iFix001 and iFix002 are the only V11.1 Fix Packs affected. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * PureScale and TSA-controlled environments * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 11.1 Mod 4 Fix Pack 4 or higher. * **************************************************************** | |
Local Fix: | |
Assign IPv4 address or associate a route to each NIC | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.06.2018 07.01.2019 07.01.2019 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |