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 IC61913 Status: Closed

DB2ICRT FAILS WITH DBI1703E ON A IPV6 ONLY MACHINE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
db2icrt fails with DBI1703E on a IPv6 only machine.  For 
example: 
 
db2icrt -a server -s ese -u db2fenc1 db2inst1 
 
ERROR:An error occurred while creating the instance "db2inst1". 
The return code is "1".  Create the instance manually using the 
command "db2icrt". 
 
ERROR:DBI1703E No valid service name or port number found.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on IPv6 only machine.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2icrt fails with DBI1703E on a IPv6 only machine.          * 
* Forexample:db2icrt -a server -s ese -u db2fenc1              * 
* db2inst1ERROR:An error occurred while creating the           * 
* instance"db2inst1".The return code is "1".  Create the       * 
* instance manually usingthecommand "db2icrt".ERROR:DBI1703E   * 
* No valid service name or port number found.                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 3                    * 
****************************************************************
Local Fix:
. install DB2 without creating instance 
 . as root, create instance user id and home directory with Unix 
command/utility 
 . as root, set DB2 global DB2FCMCOMM registry variable: 
  <db2 installation directory>/instance/db2iset 
DB2FCMCOMM=TCPIP6 -g 
 . run db2icrt to create instance
available fix packs:
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 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
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
. install DB2 without creating instance 
. as root, create instance user id and home directory with 
 
Unixc 
ommand/utility 
. as root, set DB2 global DB2FCMCOMM registry variable: 
 
<db2 installation directory>/instance/db2iset     D 
B2FCMCOMM=TCPIP6 -g 
. run db2icrt to create instance
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.07.2009
27.09.2010
27.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList