Hi !

We are currently encountering error messages when we run heavy queries (those that run longer than 2 hours).


1. Query when run Via Squirrel Client

Error: com.ibm.db2.jcc.b.DisconnectException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: Connection reset. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: C0A8966D.A1E6.100921035228, SQL State: null, Error Code: -4499


2. Same query when run Via DB2 Cli

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.XX.XX.XX". Communication function detecting the error: "recv". Protocol specific error code(s): "10054", "*", "0". SQLSTATE=08001


Observation from the test performed:
-Query executed successfully and result was obtained when run within the Database.
-Query executed successfully and result was obtained when run from server (e.g Server A) in which DB is catalogued.
-Query was run from PC via Server A. KeepAlive parameter in PC was increased. Query completed successfully, no error message. However no data was in the log.

Based on our network or DB logs no issues were observed.

Please advice on the possible cause for the above issue. Appreciate your advice. Thanks.

Check QueryTimeoutInterval in cli.ini on the client machine.

Yes I had already set the Query Time Out interval to zero.