469,929 Members | 1,409 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,929 developers. It's quick & easy.

How to identify the cause of an SQL30081N


From SAS, we're getting the following error message once in a while:
ERROR: CLI error trying to establish connection: [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: "xxx.xxx.xxx.xxx". Communication function detecting the
error: "connect". Protocol specific error code(s): "73", "*", "*".

As far as I can see from googling, the error corresponds to a "connection
reset by peer" situation.

How would you proceed in debugging? Is it most likely the OS which is
overwhelmed, or DB2 being overwhelmed, or an infrastructure thing?

Troels Arvin <tr****@arvin.dk>
Feb 7 '07 #1
0 1950

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by alederer | last post: by
7 posts views Thread by Ina Schmitz | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.