Unable to establish connection

Toad for IBM DB2
1

We are trying to establish connection to a database. While doing so, we get the following error.

ERROR [08001] [IBM] 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.26.151.31”. Communication function detecting the error: “selectForConnectTimeout”. Protocol specific error code(s): “0”, “", "”. SQLSTATE=08001

Where do we go from here?

2

Hi,

Try to connect to your database outside of Toad using the command line processor of the DB2 client installed with the Toad you’re using.

For instance, this is how you’d open the command line processor for Toad 4.7.

3

For instance, this is how you'd open the command line processor for Toad 4.7.

CLP_47.png
CLP_47.png797×166 10.9 KB

4

I get this message when I try to manually connect to database using CLP.

db2 => connect to XXXXX user XXXXX using XXXX
SQL30082N Security processing failed with reason “24” (“USERNAME AND/OR
PASSWORD INVALID”). SQLSTATE=08001
db2 =>

But when tried using the Toad front end, I get that original message which I posted earlier.

5

Hi,

The error in Toad may be a connection timeout problem. Please set Toad’s connection timeout setting to 0 in Tools -> Options -> Database -> Timeouts -> Connection timeout.

The error from the CLP may be a problem with the catalog entry, or your PC configuration, or an incorrect user/password. Please verify with your systems administrator that you are using the proper security and authentication settings for the catalog entry, that Windows is properly configured to connect to your server, and that you have the proper user/password.

6

I changed the connection timeout value to 0, and tried to connect to the database. I am still getting the same error:

ERROR [08001] [IBM] 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.26.151.31”. Communication function detecting the error: “connect”. Protocol specific error code(s): “10060”, “", "”. SQLSTATE=08001

7

Hi,

Will you please verify your server information, recatalog you database and try the connection again?

Thanks,
Adam

8

We are looking a possible firewall issue here. I will keep you posted if opening up the firewall for the port number we use, will resolve the issue or not.

Thanks and Regards,

subbu