home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC62759 Status: Closed

DB2ICRT AND DB2IUPDT HANG UP ON THE MISCONFIGURED NAME RESOLUTIO N
ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If name resolution is misconfigured, db2icrt and db2iupdt 
commands can hang up. 
  We can see the following output with "-d" trace option and 
realize db2isrv command does not return if you go into this 
issue. 
  And you can stop this hung process by kill os command, e.g. 
kill -9 db2isrv_process_id. 
* output of db2iupdt with "-d" option 
... 
+ [ 1 -eq 1 -o 1 -eq 0 -a 1 -eq 1 ] 
+ cd /opt/IBM/db2/V9.7/lib64 
+ /opt/IBM/db2/V9.7/instance/db2isrv -addfcm -i tmpinst 
... hangs ...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* UNIX                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If name resolution is misconfigured, db2icrt and db2iupdt    * 
* commands can hang up.                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v9.7fp1                                       * 
****************************************************************
Local Fix:
Fix name resolution misconfigured situation in /etc/hosts, 
/etc/netsvc.conf or other network related configuration files 
and make sure the hostname can be resolved to a valid IP and 
that IP belongs to the machine you are installing DB2 on.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 FixPak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.08.2009
23.12.2009
23.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList