|
Problem IC67142
|
Status: Closed |
SQL6031N (REASON CODE 11) ERROR WHEN TRYING TO CREATE AN INSTANCE WITH DB2ICRT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* 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). *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 fix pack 3. *
**************************************************************** |
| 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.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 fixed on DB2 9.7 fix pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.03.2010
08.11.2010
20.08.2011 |
| 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
|
 |
| 9.7.0.3
|
|
