Connectivity Problem with DB2 V10.1 on Suse Linux

by Michael Urspringer - 23.04.2013

Today I tried to install IBM DB2 V10.1 on a Suse Enterprise Linux 10.1 SP2. However, although the installation went smoothly with no errors, I was unable to connect to the DB2 server via TCP/IP. The install program told me that the server is using port 50001 but there was no connect and a “netstat -an | grep LISTEN” showed that there was no process listening on port 50001.

I checked /etc/services and there was no entry for port 50001 as well.

Running the command “db2 get dbm cfg | grep “(SVCENAME)” showed that the service name did not seem to be correctly configured as the entry was empty.

So, to solve the problem I ran the following command: “db2 update dbm cfg using svcename db2c_db2inst1” to correctly configre the service name and also added the line “db2c_db2inst1  50001/tcp” to the file /etc/services.

Afterwards I stopped DB2 (“db2stop”) and restarted it again (“db2start”).

A quick check with netstat now shoed that there was a process listening on port 50001 now and I was also able to connect via TCP/IP to the database.

However I still have no glue what caused the problem as it should normally work without these steps.

Update:

Check also (with “db2set -all”) if the variable “DB2COMM=TCPIP” is set correctly. If not, set it with “db2set DB2COMM=TCPIP” and restart DB2 afterwards.

Tagged with:  

Leave a Reply

© 2000-2015 Michael Urspringer