DB2 - Problem description
Problem IC75599 | Status: Closed |
Segmentation fault in db2gcf when the local host name does not resolve to an IPv4 address | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If the local host name does not resolve to at least one IPv4 address, the db2gcf command will fail. If you are using a High Availability solution that utilizes db2gcf tool, the solution fail to report the correct state of the DB2 resources. Running standalone db2gcf utility will result in segmentation fault. host1:/home/db2inst1> db2gcf -t 60 -u -p 0 -i db2inst1 -u Segmentation fault | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of High Availability solutions that utilize the db2gcf * * tool. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Apply DB2 V9.7.0.5 * **************************************************************** | |
Local Fix: | |
Ensure that the name of the system resolves to at least one IPv4 address. This can be accomplished by adding an entry to /etc/hosts for the loopback address: 127.0.0.1 localhost.localdomain localhost my-host-name.my-domain | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Apply DB2 V9.7.0.5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.04.2011 08.12.2011 08.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.0.5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |