|
Problem IC71778
|
Status: Closed |
DB2ICRT HANGS WHEN HOSTNAME MAPS TO AN INCORRECT IP ADDRESS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the hostname resolves to an invalid IP address in /etc/hosts,
db2icrt hangs because it tries to bind on each port.
e.g. Compare the IP address specified in /etc/hosts with the
adapter
# hostname
machineA
# cat /etc/hosts | grep machineA
1.2.3.4 machineA.yourdomain.com
# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:E0:81:5A:3F:AF
inet addr:9.26.118.54 Bcast:9.26.119.255
Mask:255.255.254.0
...
After applying the fix, you will see the following error message
when the ip address associated with the hostname is invalid:
DBI1922N The host name is not valid.
Explanation:
The TCP/IP host name parameter is not valid or does not exist.
User response:
Ensure that TCP/IP is operational on the system. If a domain
name server
is used, ensure that the domain name server machine is active.
Issue the
command again using the correct TCP/IP host name. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the hostname resolves to an invalid IP address in *
* /etc/hosts, *
* *
* *
* db2icrt hangs because it tries to bind on each port. *
* *
* *
* *
* e.g. Compare the IP address specified in /etc/hosts with the *
* *
* adapter *
* *
* # hostname *
* *
* machineA *
* *
* # cat /etc/hosts | grep machineA *
* *
* 1.2.3.4 machineA.yourdomain.com *
* *
* # ifconfig eth1 *
* *
* eth1 Link encap:Ethernet HWaddr 00:E0:81:5A:3F:AF *
* *
* inet addr:9.26.118.54 Bcast:9.26.119.255 *
* *
* Mask:255.255.254.0 *
* *
* ... *
****************************************************************
* RECOMMENDATION: *
* Upgrade to IBM DB2 V9.7 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
Ensure that the ip address that is associated with the hostname
in /etc/hosts is correct and it matches the network adapter's ip
address. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to IBM DB2 V9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2010
29.04.2011
29.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
