Db2 doesn't start, CLP doesn't start. Error is SQL6031N Error in the db2nodes.cfg file at line number "0". Reason code "3".
There could be a problem with the db2nodes.cfg file. I had an entry like:
0 RAMSCOMP RAMSCOMP 0
and it was causing all the trouble. Issuing a
db2ncrt /n:0 /u:user,password
fixed the problem. It took out the last 0 from the db2nodes.cfg file. Don't know how the last 0 got in in the first place 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=swg21258834
http://www.thefillmoregroup.com/blog/?p=66
0 RAMSCOMP RAMSCOMP 0
and it was causing all the trouble. Issuing a
db2ncrt /n:0 /u:user,password
fixed the problem. It took out the last 0 from the db2nodes.cfg file. Don't know how the last 0 got in in the first place 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=swg21258834
http://www.thefillmoregroup.com/blog/?p=66
Labels: db2 clp db2nodes.cfg reason 3 SQL6031N change hostname

0 Comments:
Post a Comment
<< Home