-
Title
Sql Optimizer for DB2 got time out -
Description
We selected Batch Running from Quest SQL Optimizer for DB2.
It ran for a while then error : SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "10.1.3.31".
Communication function detecting the error
-
Cause
It looks like the batch was terminated because the connection to database was lost. There is no Time-Out setting in the product except for the ones showed in the Batch Run Criteria window. However, it may be the case that there is a time-out restriction on the database to allow query to run.
-
Resolution
WORKAROUND
It is a client configuration issue requiring changes to the below registry variable:
KeepAliveTime
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how frequently TCP tries to verify that an idle connection is still intact by sending a keepalive packet.
If the remote computer is still reachable and functioning, the remote computer acknowledges the keepalive transmission. By default, keepalive
packets are not sent. A program can turn on this feature on a connection.