Recently a customer was facing problem while starting Tivoli Directory server. An error message was popping up while starting TDS ldap, where the database was not initializing.
I went to DB2 instance directory and could see the following message while starting the database manually,
"SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing".
As part of technotes, I cold see get some help to check the issue and this sorted out. Resolution to make the DB2 up and running and inturn make the TDS up is as below,
Navigate to <INSTANCE_HOME>/sqllib/ directory and check db2nodes.cfg file for hostname entry.
Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
The format of the entries in db2nodes.cfg is: 0 hostname 0
For example, for a system with hostname dw.ibm.com it would be: 0 dw.ibm.com 0
Technotes for reference here: