The error message includes a protocol specific return code. I find this often useful in these scenarios. You received a 10061 - this is "The connection has been refused. Check that the database manager and TCP/IP protocol support at the server has been started successfully". (These error codes/messages are defined in Appendix A of the Message Reference Volume II manual.

This is usually a server, not a client issue. Typical reason is you are missing a critical DB2SET parameter. Run the command "db2set -all" and see if the output contains a line DB2COMM=TCPIP. If not, add it with the command "db2set DB2COMM=TCPIP" and you'll be fine.

Best,
Hal Steiner

-----Original Message-----
From: McClendon Rick <db2udbdba-ezmlmshield-x96149176.[Email address protected]
To: LazyDBA Discussion <[Email address protected]
Sent: Wed, 26 Oct 2005 09:16:24 -0400
Subject: RE: Connect Error - URGENT


What does your client-side "list db directory" return?

Try cataloging the database from the client?

Client CLP:
Db2 Catalog tcpip node sampnode remote 10.1.33.226 server <Port # here>;
Db2 Catalog db sample at node sampnode;
Db2 terminate;
Db2 connect to sample user <u userid> using <pswrd>;



-----Original Message-----
From: Iswariya Vasan
[mailto:db2udbdba-ezmlmshield-x6310768.[Email address protected]
Sent: Wednesday, October 26, 2005 9:04 AM
To: LazyDBA Discussion
Subject: Connect Error - URGENT


Hi All,

My production database environment details :-

IP:- 10.1.33.226
Database Name:- sample
OS :- Linux
DB2 Version:- DB2 UDB 8.2

My Client Machine:-

IP:- 10.58.0.68
OS:- Windows

Iam trying to connect the database sample from the production
environment to my local Configuration Assistant.

Ive added the IP address of both the machines in the "hosts" file also.
And Iam able to ping the server IP from my machine.

Through CA its identifying the Machine IP, the instance name and the
database name also. But when I try to connect Iam getting the following
error.

Can anybody suggest me what has to be done ??

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):
"10061", "*", "*". SQLSTATE=08001

Regards
Iswariya Vasan



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

DB2 & UDB email list listserv db2-l LazyDBA home page