Prev: I hope in Serge Rielau
Next: Weird message in db2diag.log
From: Steven on 26 Jun 2006 15:06
I have db2 EES installed on linux . db2level
DB21085I Instance "db2inst1" uses "32" bits and DB2 code release
"SQL08025"
with level identifier "03060106".
Informational tokens are "DB2 v8.1.2.112", "s060429", "MI00155", and
FixPak
"12".
Product is installed at "/opt/IBM/db2/V8.1".

I have db2inst1 instance database self2

service name for db2 get dbm cfg lists as db2c_db2inst1

The /etc/services file

DB2_db2inst2 60000/tcp
DB2_db2inst2_1 60001/tcp
DB2_db2inst2_2 60002/tcp
DB2_db2inst2_END 60003/tcp
db2c_db2inst2 50000/tcp
DB2_db2inst1 60004/tcp
DB2_db2inst1_1 60005/tcp
DB2_db2inst1_2 60006/tcp
DB2_db2inst1_END 60007/tcp
db2c_db2inst1 50001/tcp
db2c_db2inst1i 50002/tcp

The database is running fine on the box itself but I can not connect to
the database from any other machine.


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

I have tried to connect using ever port listed above and I always get
the same error. Any idea what could be the problem?

From: Larry on 26 Jun 2006 15:26
Steven wrote:
> I have db2 EES installed on linux . db2level
> DB21085I Instance "db2inst1" uses "32" bits and DB2 code release
> "SQL08025"
> with level identifier "03060106".
> Informational tokens are "DB2 v8.1.2.112", "s060429", "MI00155", and
> FixPak
> "12".
> Product is installed at "/opt/IBM/db2/V8.1".
>
> I have db2inst1 instance database self2
>
> service name for db2 get dbm cfg lists as db2c_db2inst1
>
> The /etc/services file
>
> DB2_db2inst2 60000/tcp
> DB2_db2inst2_1 60001/tcp
> DB2_db2inst2_2 60002/tcp
> DB2_db2inst2_END 60003/tcp
> db2c_db2inst2 50000/tcp
> DB2_db2inst1 60004/tcp
> DB2_db2inst1_1 60005/tcp
> DB2_db2inst1_2 60006/tcp
> DB2_db2inst1_END 60007/tcp
> db2c_db2inst1 50001/tcp
> db2c_db2inst1i 50002/tcp
>
> The database is running fine on the box itself but I can not connect to
> the database from any other machine.
>
>
> CLI connection failed.
> SQL30081N A communication error has been detected. Communication
> protocol being used: "TCP/IP". Communication API being used:
> "SOCKETS". Location where the error was detected: "63.100.30.56".
> Communication function detecting the error: "connect". Protocol
> specific error code(s): "10060", "*", "*". SQLSTATE=08001
>
> I have tried to connect using ever port listed above and I always get
> the same error. Any idea what could be the problem?
>
I assume that this is an attempt from the command line and not one of
the GUI tools? 10060 is a TCP/IP timeout.

Are the database and node cataloged on the client machine?
Are there any firewalls that need to be disabled (for port number that
you are trying to connect to)?
Is the DB2COMM variable in DB2SET set to TCPIP?

Larry Edelstein
 | 
Pages: 1
Prev: I hope in Serge Rielau
Next: Weird message in db2diag.log