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

SQL6031N (REASON CODE 11) ERROR WHEN TRYING TO CREATE AN INSTANCE
WITH DB2ICRT.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
User's may face the SQL6031N (reason code 11) error message when 
running db2icrt. Here is the description of this error: 
 
SQL6031N 
Error in the db2nodes.cfg file at line number line. Reason code 
reason-code. 
 
Explanation 
The statement cannot be processed because of a problem with the 
db2nodes.cfg file, as indicated by the following reason codes: 
 
(11) 
    The port value at line line of the db2nodes.cfg file in the 
sqllib directory is not defined for your DB2 instance id in the 
services file (/etc/services on UNIX-based systems).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Unknown                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* User's may face the SQL6031N (reason code 11) error          * 
* messagewhenrunning db2icrt. Here is the description of this  * 
* error:SQL6031NError in the db2nodes.cfg file at line number  * 
* line. Reasoncodereason-code.ExplanationThe statement cannot  * 
* be processed because of a problem withthedb2nodes.cfg file,  * 
* as indicated by the following reasoncodes:(11)The port value * 
* at line line of the db2nodes.cfg file inthesqllib directory  * 
* is not defined for your DB2 instance id intheservices file   * 
* (/etc/services on UNIX-based systems).                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 6 or use one of          * 
* thefollowing Local Fixes:1) Manually insert entries on       * 
* /etc/services file and re-rundb2icrt2) Please check and      * 
* correct /etc/hosts file as per thefollowingarticle:db2icrt   * 
* failed due to a mis-configured /etc/hosts file               * 
* onAIXhttp://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21 
* correcting /etc/hosts, re-issue the db2icrt command.         * 
****************************************************************
Local Fix:
There are two Local Fixes for this issue: 
 
1) Manually insert entries on /etc/services file and re-run 
db2icrt 
 
2) Please check and correct /etc/hosts file as per the following 
article: 
 
db2icrt failed due to a mis-configured /etc/hosts file on AIX 
http://www-01.ibm.com/support/docview.wss?rs=71&uid=swg21306113 
 
After correcting /etc/hosts, re-issue the db2icrt command.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67142 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2010
30.06.2010
30.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)