suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT25519 Status: Geschlossen

db2instance & db2haicu might fail with a SEGV in
sqlhaGetInfoForClusterObject if route or IPv4 IP is not assigned to NIC

Produkt:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problembeschreibung:
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-Zusammenfassung:
****************************************************************
* 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
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.06.2018
07.01.2019
07.01.2019
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version