SEO

___________________________________________
ENVIRONMENT
___________________________________________

(1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
(2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.

___________________________________________
PROBLEM
___________________________________________
(1) 1st, 3rd, 5th....attempts to connect to server database
are successful.
(2) 2nd, 4th, 6th...attempts to connect to server database
return tcp/ip error. Error Message is as below:

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

_______________________________________________

I have done the basic checking - DB2COMM / SVCENAME etc
Also note that I do not have to do absolutely anything between
1st and 2nd attempt to get the failure message AND similarly
I do not have to do absolutely anything between
2nd and 3rd attempt to get connected !!


This problem has had me completely floored.
Any advice is urgently sought (YES, THIS IS PRODUCTION)

TiA.............Anurag

Anurag wrote:

> ___________________________________________
> ENVIRONMENT
> ___________________________________________
>
> (1) Server = DB2 UDB DPF, 8.2.3 on AIX, 64-bit instance.
> (2) Client = DB2 RTC 8.1 FP10 on AIX, 64-bit instance.
>
> ___________________________________________
> PROBLEM
> ___________________________________________
> (1) 1st, 3rd, 5th....attempts to connect to server database
> are successful.
> (2) 2nd, 4th, 6th...attempts to connect to server database
> return tcp/ip error. Error Message is as below:
>
> SQL30081N A communication error has been detected.
> Communication protocol being used: "TCP/IP".
> Communication API being used: "SOCKETS". Location
> where the error was detected: "<Correct IP Addr>".
> Communication function detecting the error: "connect".
> Protocol specific error code(s): "69", "*", "*".
> SQLSTATE=08001

After reading the documentation for SQL30081 I found that the "rc1"
represents the global error number returned by the network (socket)
operation. And errno 69 = ENETDOWN = "Network is down". It appears that
you have some connectivity issues at a lower level in your system.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

Hello Knut,
Wish you a very happy 2006 and Thanks for your suggestion!
I have escalated this to the Netowrk / Unix Admin.

Another thing I would be intersted in is - Where are all these
documents?
Are these IBM internal (I could not find errno=69) in DB2
documentation.

Thanks,
Anurag

__________________________________________________ ___________
Knut Stolze wrote:
>
> After reading the documentation for SQL30081 I found that the "rc1"
> represents the global error number returned by the network (socket)
> operation. And errno 69 = ENETDOWN = "Network is down". It appears that
> you have some connectivity issues at a lower level in your system.
>
> --
> Knut Stolze
> DB2 Information Integration Development
> IBM Germany

Anurag wrote:
> Hello Knut,
> Wish you a very happy 2006 and Thanks for your suggestion!
> I have escalated this to the Netowrk / Unix Admin.
>
> Another thing I would be intersted in is - Where are all these
> documents?
> Are these IBM internal (I could not find errno=69) in DB2
> documentation.
>
> Thanks,
> Anurag
>
> __________________________________________________ ___________
> Knut Stolze wrote:
>
>>After reading the documentation for SQL30081 I found that the "rc1"
>>represents the global error number returned by the network (socket)
>>operation. And errno 69 = ENETDOWN = "Network is down". It appears that
>>you have some connectivity issues at a lower level in your system.
>>
>>--
>>Knut Stolze
>>DB2 Information Integration Development
>>IBM Germany
>
>
If you install the DB2 Information Center, and search for "errno" and
"69", you'll find an entire section on Communications Errors.

Larry Edelstein

Anurag wrote:

> Another thing I would be intersted in is - Where are all these
> documents?
> Are these IBM internal (I could not find errno=69) in DB2
> documentation.

I guess Larry gave you the "official" pointer. Personally, I did look at
the error message using the normal:

$ db2 "? sql30081"

And for the errno, I had a look at /usr/include/errno.h. You might have to
follow to a few header files that are included (especially Linux is a bit
messy in this respect for architectural reasons).

--
Knut Stolze
DB2 Information Integration Development
IBM Germany