Discussion:
Error while Connecting to DB2 Database
(too old to reply)
s***@yahoo.co.in
2006-10-25 13:41:23 UTC
Permalink
s***@yahoo.co.in
2006-10-25 13:48:23 UTC
Permalink
I got following Error while connecting to the DB2 Database...

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

Could any one suggest what may be the problem...

thanks in Advance
Larry
2006-10-25 23:23:30 UTC
Permalink
Post by s***@yahoo.co.in
I got following Error while connecting to the DB2 Database...
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
"connect". Protocol specific error code(s): "10060", "*", "*".
SQLSTATE=08001
Could any one suggest what may be the problem...
thanks in Advance
TCP/IP 10060 (you can google this) indicates TCP/IP timeout. Probably
the server is not responding

Larry Edelstein
Ben Hull
2006-11-21 22:12:26 UTC
Permalink
Post by s***@yahoo.co.in
I got following Error while connecting to the DB2
Database...
SQL30081N A communication error has been detected.
. Communication protocol
"SOCKETS". Location
where the error was detected: "". Communication
"connect". Protocol specific error code(s): "10060",
"*", "*".
SQLSTATE=08001
Could any one suggest what may be the problem...
thanks in Advance
Yes, this is the classic "sockets" error. Basically it means the client trying to connect cannot see the database via TCP/IP. From the client start with the Client Configuration Assistant(CCA). If your test connecting fails from the client, then try to ping the database hostname. The server hostname is how the client finds the database. If the ping hostname resolves to the correct TCP/IP address try dropping and readding the database connection through the CCA. If the ping does not resolve the correct TCP/IP address you need to call your network admin on the carpet and check the DNS or local hosts file.

Ben Hull
Senior DBA
Comtrak Logistics, Inc.
***@comtrakinc.com

Loading...