suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT27680 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 / A50 - 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

This APAR is fixed in new release Db2 11.1 via IT25519.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 11 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       :
07.01.2019
25.02.2020
25.02.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)