This is a discussion on Multi-nodes in one instance in linux within the DB2 forums, part of the Database Server Software category; --> Hi, I am trying to setup 2 logical nodes in a same instance. I changed the db2nodes.cfg file as ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I am trying to setup 2 logical nodes in a same instance. I changed the db2nodes.cfg file as 0 db2 0 1 db2 1 i also added db2 an entry db2 in my hosts.allow file when i give db2start i get following errir SQL6048N A communication error occured during START or STOP. The only information i read on the web is for AIX and actually found one that shows how to do for AIX. This is how some one did it.. but it is for AIX. ----------------------------------------------------------- i found the reason of this problem was i exec "securetcpip" command before. securetcpip command forbidden rsh, rlogin, rcp etc. i solve the problem with the following steps. ================================================ root: chmod 555 /usr/sbin/rshd chmod u+s /usr/sbin/rshd chmod 555 /usr/bin/rlogin stopsrc -s inetd startsrc -s inetd echo "+" >/.rhosts chmod 600 /.rhosts db2inst1: echo "+" >/.rhosts chmod 600 /.rhosts =============================================== then i can "db2start" the db2 server. --------------------------------------------------------------- Does any one know how to make this work in linux. Or even if someone is aware how these /usr/sbin/rshd and .rhosts files managed in linux. I am using redhat 7.2. Does any one have any idea. -Bimal |
| ||||
| Bimal wrote: > Hi, > I am trying to setup 2 logical nodes in a same instance. > I changed the db2nodes.cfg file as > 0 db2 0 > 1 db2 1 > > i also added db2 an entry > db2 > in my hosts.allow file > > when i give db2start i get following errir > SQL6048N A communication error occured during START or STOP. Start by trying to use rsh yourself between the "nodes". As your instance owner, run "rsh db2". You should get your command prompt back without password. If not, solve that problem first, independantly of DB2. If that works, but DB2 still doesn't work, the next best place to look is in your db2diag.log (normally found in sqllib/db2dump). Usually I find the text there to be more than sufficient to see what the problem is, and the solution is often self-evident. If you can't solve the rsh problem, I'm sure there are many great places to find help for that (other newsgroups), although I'm sure some in here will be able to help, too. |
| Thread Tools | |
| Display Modes | |
|
|