http://www.dbatodba.com These are the search results for the query, showing results 1 to 1. http://www.dbatodba.com/Forums/db2/863798580/166694233 Hello everyone ! I just wanted to share a recent experience I have had with starting / stopping a DB2 instance. Every time I tried to do it I got the errors SQL6030N or SQL6031N, RC=11 or RC=13. These error codes generally mean that you have a db2nodes.cfg problem or a TCP/IP port error (that one set on SVCENAME parameter). It turns out that, after almost 5 hours struggling with this problem, I discovered that the problem was in fact in a simple file: "/etc/nsswitch.conf". This files is part of the NIS+ subsystem, which allows centralized authentication to UNIX/LINUX operating systems. The system administrator had just enabled this feature on the UNIX machine I was working in and created that nsswitch.conf with incorrect parameters and, to make it worse, the only message I got in db2diag.log was a severe message on process "db2fm". So, here goes my advice: if you start getting the error messages SQL6030N or SQL6031N check immediately if the file above has been updated/created recently. Check your db2nodes.cfg and /etc/services to make sure that your configurations are correct, and if your are nothing is wrong check the NIS+ configuration. Another hint: when this problem occurs no db2 commands respond accordingly, not even db2pd nor "db2 get dbm cfg". All these commands end up by throwing a message about "incorrect db2nodes.cfg configuration".   See you another time, RMUNHOZ No publisher rmunhoz 2009-07-08T15:01:48Z Comment