I have cataloged remote database into my DB2(V8.2) server. It was cataloged successfully but when I try to connect to that database (db2 "connect to mydb") I see this error,

SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "172.17.5.24". Communication function detecting
the error: "connect". Protocol specific error code(s): "111", "*", "*".
SQLSTATE=08001

Can any one please help me on this.

Can you post the catalog commands for the db and node?

Andy

Make sure the instance is running and the database server on the is accessible at the specified port (e.g. the firewall is not blocking traffic to that port).

Hi ARWinner

I have used the following catalog commands for node and db,

DB2 "catalog tcpip node remotenode remote 172.17.5.24 server 60000"

DB2 "catalog db mydb at node remotenode"

thanks,
Pradeep

Check if:
- you can telnet to the server using this port (telnet <host> <port>)
- db2comm and svcename is set

For more info, please check the following technote:
IBM - SQL30081N TCPIP communication errors

You have to catalog TCPIP node, DCS database and remote database.
Try these commands in order.

DB2 CATALOG TCPIP NODE nodename REMOTE xxx.xxx.xxx.xxx
DB2 CATALOG DCS DATABASE host name
DB2 CATALOG DATABASE AP3DDBM1
Terminate

List DCS directory,node directory and DCS directory to make sure that catalog is successful.

Thanks
Prasad Vankina

dcs db is only needed if connecting from luw to mainframe z/os or vm/vse
what is source and what is target as o/s