Hi Recently out servers moved to different location and ip address got changed. After editing db2nodes.cfg file I was able to connect to remote database from one unix server.

Today while connecting to database from one linux server (1) to other linux server (2 for database), it does not get connected and hangs. I can see following in db2dia.log:

==> db2diag.log <==
PID : 9316 TID : 3053667200 PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110
MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="110".

2007-04-03-18.14.15.454843-240 I7213855G304 LEVEL: Error
PID : 10720 TID : 3053667200 PROC : db2bp
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:110
MESSAGE : DIA3202C The TCP/IP call "connect" returned an errno="110"

Any idea what happens???

Thanks
Diwakar

I am using DB2 UDB v8.2:

DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08024"
with level identifier "03050106".
Informational tokens are "DB2 v8.1.0.104", "s060120", "MI00146", and FixPak
"11".
Product is installed at "/opt/IBM/db2/V8.1".

How have you cataloged the DB2 instance? What's the output of "db2 list node directory"? If you see an IP address in there, verify that it is the right one. If it is a hostname, verify that it resolves to the correct IP address.

Why have you modified the db2nodes.cfg file? And what exactly have you done to successfully connect after that? The db2nodes.cfg file is only used to let the DB2 server know which other database partitions are out there and where to find them. It has nothing whatsoever to do with client/server communication.

I have resolved it. I had to un-catalog and re-catalog the node as the node was old... Somehow the sysadm previleges were lost and I was not able to uncatalog and catalog the node and db..

Now it is done.. thanks a lot for your directions.

Cheers
Diwaker