Attempting to connect with client to remote DB2 instance

[Harlin]

Hi,

I installed the admin client on my WebSphere box. I am now attempting
to connect to my DB2 server (on another box). I have been able to find
the DB2 server, instance and needed databases. These auto-register
themselves in the admin client. However, when I try to connect to the
db's to look at the Table details I get the following errors:

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

Also, this is the command that is being sent:

UNCATALOG NODE DB2;
CATALOG TCPIP NODE DB2 REMOTE eb13.atlanta.ibm.com
SERVER db2 SECURITY SOCKS REMOTE_INSTANCE db2 SYSTEM
DYN9009045110 OSTYPE LINUX;
Is there anything I'm missing?

Thanks,

[Larry]

Need your platforms. But if you check the DB2 communication error codes,
"111" seems to be Connection Refused on Linux. "The connection has been
refused. If you are trying to connect to the database, check that the
database manager and TCP/IP protocol support at the server have been
started successfully. If using SOCKS protocol support, also ensure that
TCP/IP protocol support at the SOCKS server has been started successfully"

See

http://publib.boulder.ibm.com/infoce...e/rcommsec.htm

Larry Edelstein

Harlin wrote:

Hi,

I installed the admin client on my WebSphere box. I am now attempting
to connect to my DB2 server (on another box). I have been able to find
the DB2 server, instance and needed databases. These auto-register
themselves in the admin client. However, when I try to connect to the
db's to look at the Table details I get the following errors:

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

Also, this is the command that is being sent:

UNCATALOG NODE DB2;
CATALOG TCPIP NODE DB2 REMOTE eb13.atlanta.ibm.com
SERVER db2 SECURITY SOCKS REMOTE_INSTANCE db2 SYSTEM
DYN9009045110 OSTYPE LINUX;
Is there anything I'm missing?

Thanks,

[Harlin]

Hi Larry,

These are both running Suse 9 Enterprise with DB2 8.1 -- actually the
DB2 server was running on RedHat 4 Ent. but it will be changing to Suse
9 today some time (11/1/2005). We will try this again later in the day.
Thanks very much for the help!

Harlin Seritt

[Ian]

Harlin wrote:

Also, this is the command that is being sent:

UNCATALOG NODE DB2;
CATALOG TCPIP NODE DB2 REMOTE eb13.atlanta.ibm.com
SERVER db2 SECURITY SOCKS REMOTE_INSTANCE db2 SYSTEM
DYN9009045110 OSTYPE LINUX;

Make sure that 'db2' is defined in /etc/services on the client machine
and matches the port number that the DB2 server is listening on.