2246630 - SQL30081N TCP/IP error

The SQL30081N can have many reasons.  Most are connected to Network issues.

Scenario 1.

The system log and the developer traces show error:

ERROR in DB6Fetch[/bas/741_REL/src/dbs/db6/dbdb6.c, 4132] CON = 0 (BEGIN)
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: "IP ADDRESS".  Communication function detecting the error: "recv".  Protocol specific error code(s): "238", "*", "*"

The  error will always be SQL30081N , however the actual error is the protocol specific error, which in this example is  "238", "*", "0".

For other Operating systems this protocol error value will be returned as follows - Windows (10060)、linux (110)、SUN (145) HP (238)

*************************************************************************************************************

Scenario 2.

A short dump may occur when accessing a table.  
The text returned in both the short dump and corresponding developer trace file is 

SQL30081N  A communication error has been detected. Communication protocol being used: "TCP/IP".  Communication API being used: "SOCKETS".  Location where the error was detected: "IP ADDRESS".  Communication function detecting the error: "recv".  
Protocol specific error code(s): "*", "*", "0".

Db2 LUW IBM

QueryTimeoutInterval, db2cli.ini, Network, TCP/IP layer, EPIPE, EADDRINUSE, ECONNRESET, detected, interface, location, client, application, SQL30081N, selectForRecvTimeout, "recv", NUM_LOG_SPAN, diagnostics, TCP/IP, Client termination, CLI, 9999, detected, interface, location, client, application, severe DB error -99999; work process in reconnect status, CLI0108E  Communication link failure. , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem