Facing problem while cataloging database

asish2a · #1 (**permalink**) 03-16-09, 11:52

Hi ,

I'm newbie in DB2 Administration, I'm trying to do database cataloging. I'm working with DB2 V8.2 on Linux V4.
These are the steps that I have followed to catalog :

1.db2 catalog tcpip node node1 remote xxx.xxx.xxx.xxx server <sname>

2. db2 catalog database <database> at node1

3. db2 connect to <database> user <user> using <password>

This the error that I'm facing on console

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

This is error that I get on db2diag.log

FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110
MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="111".

Can anyone tell me where I'm going wrong and What I have to do to fix it. Thank you.

ARWinner · #2 (**permalink**) 03-16-09, 16:41

On step 1, what did you supply for <sname>?

Andy

nick.ncs · #3 (**permalink**) 03-16-09, 22:52

Go to the remote computer and check whether the communication protocol is set to TCP/IP

Execute the following command

Code:

db2set -all

In the list check the value of

Code:

DB2COMM

and see whther it has been set to

Code:

TCPIP

.

asish2a · #4 (**permalink**) 03-17-09, 05:15

Hi Andy,
On step 1, In the <sname> I have supplied service_name of remote system.

Hi Nick,
I have gone to remote computer and checked the communication protocol, it is set to TCP/IP

First of thanks for your replies. But still I'm unable to catalog. Please send your valuable replies. Thankyou.

grofaty · #5 (**permalink**) 03-17-09, 05:45

Hi,
111 error means timeout. Did you check firewall settings on server and also on client?
Regards

n_i · #6 (**permalink**) 03-17-09, 07:16

Quote:

Originally Posted by asish2a

On step 1, In the <sname> I have supplied service_name of remote system.

So, how does the client know the contents of /etc/services on the remote system? Unless the same entry exists in /etc/services on the client, use the port number instead.

asish2a · #7 (**permalink**) 03-17-09, 08:06

Hi n_i,

I have checked by providing port number but still I face the same error.

asish2a · #8 (**permalink**) 03-17-09, 10:14

Hi grofaty,

I have checked firewall settings on server and client. I have gone through the command /usr/sbin/lokkit in my root and checked it. Its all fine. Do I need to have any changes on iptables ?