Menu
▾
▴
#2757 db2start returns SQL5043N Support for one or more communicat
During the setup of a ST machine (AIX) and Paul on (Linux), Running the db2sqlsetup script exited with an error on the db2start. The below messages and error code 6 came from DB2. The AIX machine 2.6.11 xCAT was fixed by reboot. The Linux machine 2.7 xCAT, still gets the error. Both are HA environments. Googling, I do find the error and have checked everything that is suggested so far and all seems correct. Need further investigation and if this a problem we are going to hit generally, the setup script needs to be tolerant of the warning. I expect a sev 6 return code is minor. I need to debug some more. In general, this error is a complaint about using the server port assigned to the database, in our case 50001, but I am wondering if the HA environment of using alias ip to address the server might be confusing DB2. We have definitely set this up before and it might just be the order in which we do things. Very few change have been made to DB2, but the one change to set Authentication Client instead of Authentication Server for LL, might also be a factor. Took that out yesterday on the Linux machine and it did not help.
db2start:
Starting the DB2 Server
SQL5043N Support for one or more communications protocols failed to start successfully. However, core database manager functionality started successfully.
Discussion
The problem here turns out that when db2 was installed and configured, the hostname of the EMS (DB2 server) was not resolvable. It did not have an entry in /etc/hosts. Also site.master was set to an ip address that was not resolvable to the hostname. I think for a good DB2 install, we need at the point of installation and configuration, site.master to be a resolvable ip address for the name that is returned by hostname. We set the name resolution correct, removed and reinstalled DB2 and ran db2sqlsetup and had no issues.