I am not sure whether the problem is on the server or the client side, so I'll give info on both:
I am running 2 virtual machines with centos linux on the same windows host, which can successfully ping each other.
when running [I]db2start[/I], I get the following message:
SQL5043N Support for one or more communications protocols failed to start successfully. However, core database manager functionality started successfully.
However, in the db2diag.log file (diag level 4) I see
MESSAGE : DIA3000I "TCPIP" protocol support was successfully started.
although, I see some "Error" and "Severe" entries there
TCP/IP Service name (SVCENAME) = 50000
SSL service name (SSL_SVCENAME) =
ibm-db2 523/tcp # IBM-DB2
ibm-db2 523/udp # IBM-DB2
questdb2-lnchr 5677/tcp # Quest Central DB2 Launchr
questdb2-lnchr 5677/udp # Quest Central DB2 Launchr
DB2_db2inst1 50000/tcp # This is for SVCENAME
I am using the free edition express-C v22.214.171.124
On the client side, I use unixODBC and libodbc++ which works ok locally.
When using the following connection string in C++ code:
const string connstring = "DSN=Navajo;Hostname=192.168.99.110;Port=50000;Protocol=TCPIP;Uid=db2inst1;Pwd=zzz;";
I get the error:
unixODBCIBMCLI Driver CLI0199E Invalid connection string attribute. SQLSTATE=08001
the Data Source is defined in the /etc/odbc.ini as follows:
Description = Navajo Systems DB
Driver = DB2
Database = NAVAJO
Hostname = 192.168.99.110
Port = 50000
Protocol = TCPIP
Uid = db2inst1
Pwd = zzz
Note that db2 is also installed on the client machine as they are a replica of one another, but it is stopped.
Is there a tool with can help me check whether the database is listening properly (perhaps from Windows)?
Sorry for the long post, thanks in advance!