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

I’ve written about issues related to “SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing” before, but I thought I’d add a few short notes.

  1. Your machine needs to be able to ping itself. If it can’t ping itself, it can’t DB2 itself either.
  2. The output of hostname, db2set -all, and cat /home/db2inst1/sqllib/db2nodes.cfg needs to match.

If your machine can’t ping itself, cat /etc/hosts. Chances are, you need to add a line like the following:

127.0.0.1 myhostname.mydomain myhostname

If DB2SYSTEM is set to the wrong value, db2set -g DB2SYSTEM=`hostname` will fix it on Linux.

If db2nodes.cfg has the wrong value, overwrite it with the right one.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.