Fix #DB2 Communication protocol failed to start issue: SQL5043N

By | November 21, 2017

I moved my DB2 installation to a new server from a full back-up. After performing all the necessary steps:
1. Recreate the necessary users: db2inst1, db2fenc1, db2das1
2. Give ownership to their home directories

I tried to start the instance. I logged in to the db2inst1 user and started the database.
This was the result:

Looking at the reported issue with db2diag, the last entry looked like:

The fix is to add an entry in /etc/services for the db2 TCP service

Then just db2stop and try again:

Contribute to this site maintenance !

This is a self hosted site, on own hardware and Internet connection. The old, down to earth way 🙂. If you think that you found something useful here please contribute. Choose the form below (default 1 EUR) or donate using Bitcoin (default 0.0001 BTC) using the QR code. Thank you !



Leave a Reply

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