At home, I've installed DB2 Express on my Win7 notebook, as a part of the IBM WebSphere installation. At first it was working, but then I restarted Windows and moved to the office, and since then I am unable to connect to the db2 instance using TCP/IP. DB2 Control Center works with the db locally without problems, though.
It turns out that db2 now doesn't start the TCP/IP listener, as there's no process listening on port 50000. Upon start, db2start displays the following message:
SQL5043N Support for one or more communications protocols failed to start successfully. However, core database manager functionality started successfully.
When I try to connect to the DB using TCP/IP, I get the following error:
D:\Programs\IBM\WebSphere\AppServer\db2\BIN>db2 connect to QECMNDB SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "192.168.2.100". Communication function detecting the error: "connect". Protocol specific error code(s): "10061", "*", "*". SQLSTATE=08001
The IP address changes according to which network (home/none/office) I am connected to. When I am disconnected or at office, the IP is one of my virtual adapters (VMware or VirtualBox). (!?!)
The database is DB2 Express v9.7 in WebSphere 7.5.
>db2set -all [e] DB2PATH=D:\Programs\IBM\WebSphere\AppServer\db2 [i] DB2INSTPROF=C:\ProgramData\IBM\DB2\DB2COPY1 [i] DB2COMM=TCPIP [g] DB2_CREATE_DB_ON_PATH=YES [g] DB2_EXTSECURITY=YES [g] DB2_GRP_LOOKUP=LOCAL,TOKENLOCAL [g] DB2SYSTEM=MYNOTEBOOK1 [g] DB2PATH=D:\Programs\IBM\WebSphere\AppServer\db2 [g] DB2INSTDEF=BPMINST [g] DB2ADMINSERVER=DB2DAS00
The communication service name db2c_BPMINST corresponds to the following line in C:\Windows\system32\drivers\etc\services:
In db2diag.log, there is:
2013-10-10-23.49.14.054000+120 I1470074F426 LEVEL: Event PID : 7648 TID : 6648 PROC : db2syscs.exe INSTANCE: BPMINST NODE : 000 EDUID : 6648 EDUNAME: db2sysc FUNCTION: DB2 UDB, fast comm manager, sqlkf_init_allocate_shared, probe:500 START : FCM infrastructure started FCM running in non-shared mode; FCM parallelism degree: 1; comm protocol: TCP/IPv4 2013-10-10-184.108.40.206000+120 I1470502F365 LEVEL: Error PID : 7648 TID : 6648 PROC : db2syscs.exe INSTANCE: BPMINST NODE : 000 EDUID : 6648 EDUNAME: db2sysc FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr, probe:47 MESSAGE : DIA3202C The TCP/IP call "bind" returned an errno="10013".
So what is wrong, why cannot my DB2 Express start the TCP/IP listener?