SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing

[elza]

Hi,

We have installed DB2 V9 on AIX with DPF enabled. But when we try to start the instance its giving this error.

SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing

We have made an entry in the .rhhosts file inside instance home directory. Also we have made changes in the db2nodes.cfg. We have a single server and multipartition should be enabled on that.

We have made all the changes as per the document.But still its not working.

Anybody know how to solve this issue....

[Knut Stolze]

Post by elza
Hi,
We have installed DB2 V9 on AIX with DPF enabled. But when we try to
start the instance its giving this error.
SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing
We have made an entry in the .rhhosts file inside instance home directory.
Also we have made changes in the db2nodes.cfg. We have a single server
and multipartition should be enabled on that.
We have made all the changes as per the document.But still its not working.
Anybody know how to solve this issue....

Did you have TCP/IP enabled before you changed db2nodes.cfg? If so, was it
working? If it is set up only partially, you may see this error.

What exactly did you change in db2nodes.cfg? And was there any particular
reason why you did not use the command:

db2 start dbm DBPARTITIONNUM ... ADD DBPARTITIONNUM ...

Also, does connecting work with "rhost" and without password?

[l***@cra-arc.gc.ca]

As the instance owner, try to do a db2_all "echo OK", it won't work...
then try to ssh to that same server where you are...
even if it is on the same server, the nodes are sshing to eachother...
by doing the ssh manually, you will get messages saying that this is a new server bla bla bla... say "yes" and try again... it should work after that.

[Knut Stolze]

Post by l***@cra-arc.gc.ca
As the instance owner, try to do a db2_all "echo OK", it won't work...
then try to ssh to that same server where you are...
even if it is on the same server, the nodes are sshing to eachother...
by doing the ssh manually, you will get messages saying that this is a new
server bla bla bla... say "yes" and try again... it should work after
that.

Use "ssh" only if you set the DB2 registry variable DB2RSHCMD to ssh. If
not, you will have to use "rsh" instead.