Db2 Error 6031
Technote (FAQ) Question While installing DB2, a message might appear if the limit is hit for the number of services.xx files located under C:\WINDOWS\system32\drivers\etc directory. If DB2 has been installed several times, DB2 backs up the services file several times during an install. If there are too many of these services file, this message might occur: SQL6031N - Error in the db2nodes.cfg file at line number "". Reason code "". Cause Too many services.xx files (where xx represents a number like 01 for example) located under C:\WINDOWS\system32\drivers\etc directory. Answer Remove all of the services.xx files and update the file called services by adding the 60000-60003 ports for DB2 and reboot the machine. Here's what the entry into the services file should look like: DB2_DB2 60000/tcp DB2_DB2_1 60001/tcp DB2_DB2_2 60002/tcp DB2_DB2_END 60003/tcp Document information More support for: InfoSphere Warehouse DWE - Integrated Installer Software version: 9.1 Operating system(s): Windows Software edition: Base, Enterprise Reference #: 1232488 Modified date: 2006-03-15 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
RAMSCOMP 0and it was causing all the trouble. Issuing adb2ncrt /n:0 /u:user,passwordfixed the problem. It took out https://bytes.com/topic/db2/answers/185353-sql6031n-after-etc-services-changed the last 0 from the db2nodes.cfg file. Don't know how the last 0 got in in the first place db2 error but I guess it had something to do with my trying to edit the services file and change the db2 port numbers as everything was working fine until then.Detailed list of things to do to change hostname:http://www-01.ibm.com/support/docview.wss?uid=swg21258834http://www.thefillmoregroup.com/blog/?p=66Labels: db2 db2 error 6031 clp db2nodes.cfg reason 3 SQL6031N change hostname
posted by Ram at 2:47 PM 0 Comments: Post a Comment << Home About A blog to share stuff that I find interesting, mostly in the database area and about software in general. Comments are always welcome! About Me Name: Ram View my complete profile Previous nawk 'c-->0;$0~s{if(b)for(c=b+1;c>1;c--)print r[(N... Shell script: To check network and perform some ac... DB2 Import Unix script with validation DB2 Import Considerations Glossary model thoughts DB2 High Availability Options Article Connecting from DB2 z/OS to DB2 LUW Unmerge cells in Excel and copy value into all cel... Synchronized scrolling in Excel HIPAA Standard Transaction - Claims Status Inquiry...Post your question and get tips & solutions from a community of 418,478 IT Pros & Developers. It's quick & easy. SQL6031N after /etc/services was changed. P: n/a RickC 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 to work through this? Rick Nov 12 '05 #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 to work through this? Rick Nov 12 '05 #2 P: n/a Artur Rick, as you can connect to the database remotely this means that SVCENAME is set correctly. Set