Error In The Db2nodes Cfg File At Line
AN INSTANCE WITH DB2ICRT. z/os Fixes are available DB2 Version 9.5 Fix Pack 6afor Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 7for Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 8for Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 9for Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 10for Linux, UNIX, and Windows Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error 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). 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. 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 dir
AN INSTANCE WITH DB2ICRT. z/os Fixes are available 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, http://www.ibm.com/support/docview.wss?uid=swg1IC67141 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 Subscribe You can track all active APARs for this component. http://www.ibm.com/support/docview.wss?uid=swg1IC67142 APAR status Closed as program error. Error 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). 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. Problem summary **************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * Error in the db2nodes.cfg file at line
Post your question and get tips & solutions from a community of 418,513 IT Pros & Developers. It's quick & easy. SQL6031N after /etc/services was changed. https://bytes.com/topic/db2/answers/185353-sql6031n-after-etc-services-changed P: n/a RickC I am getting the following error when I run a https://github.com/bigfix/boxes/issues/1 db2 clp command. $ db2 list applications SQL6031N Error in the db2nodes.cfg file at line number "0". Reason code "11". $ db2level DB21085I Instance "db2inst7" uses DB2 code release "SQL07029" with level identifier "030A0105" and informational tokens "DB2 v7.1.0.111", "s050516" and "U803327". I believe the /etc/services file was overwritten with a file error in that did not have the entries for the db2 instance. I have added the appropriate entries but I am still unable to run a clp command. db2stop also errors out with the same message. I am able to connect to db2 from a remote server but I cannot connect from the database server. Any suggestions on how to work through this? Rick Nov 12 '05 error in the #1 Post Reply Share this Question 3 Replies P: n/a Phil Sherman Make sure the service name in /etc/services matches the SVCENAME in the DBM config. This is a dbm parameter and will probably require stopping and restarting the instance to fix it. If you specify the numeric port for SVCENAME then the /etc/services file isn't used. I'd still put the entry there for documentation when using the numeric port number. Phil Sherman RickC wrote: I am getting the following error when I run a db2 clp command. $ db2 list applications SQL6031N Error in the db2nodes.cfg file at line number "0". Reason code "11". $ db2level DB21085I Instance "db2inst7" uses DB2 code release "SQL07029" with level identifier "030A0105" and informational tokens "DB2 v7.1.0.111", "s050516" and "U803327". I believe the /etc/services file was overwritten with a file that did not have the entries for the db2 instance. I have added the appropriate entries but I am still unable to run a clp command. db2stop also errors out with the same message. I am able to connect to db2 from a remote server but I cannot connect from the database server. Any suggestions on how
Sign in Pricing Blog Support Search GitHub This repository Watch 5 Star 4 Fork 2 bigfix/boxes Code Issues 13 Pull requests 0 Projects 0 Pulse Graphs New issue db2 does not autostart on reboot #1 Open gnawhleinad opened this Issue Oct 14, 2014 · 2 comments Projects None yet Labels bug Milestone No milestone Assignees No one assigned 1 participant gnawhleinad commented Oct 14, 2014 I suspect db2iauto -on db2inst1 is not working... gnawhleinad added the bug label Oct 14, 2014 gnawhleinad commented Oct 23, 2014 I suspect db2iauto -on db2inst1 is not working... It's not working. As a hack, I'm going to at a init.d script... gnawhleinad added a commit that closed this issue Oct 23, 2014 gnawhleinad #1 5622df4 gnawhleinad closed this in 5622df4 Oct 23, 2014 gnawhleinad commented Nov 1, 2014 5622df4 didn't work. Startup fails with: SQL6031N Error in the db2nodes.cfg file at line number "0". Reason code "16". This is likely due to changing the hostname. I'm going to try http://www-01.ibm.com/support/docview.wss?uid=swg21258834... gnawhleinad reopened this Nov 1, 2014 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.