Fixes are available
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Closed as program error.
CLI computes large time differences when it receives incorrect results for "get_current_clock_ticks" type calls to the underlying OS on some platforms / firmware versions. This APAR introduces compensating logic in CLI to correct for these errors, thus closely preserving the CLI application's declared timeout requirements on SQL_ATTR_LOGIN_TIMEOUT and SQL_ATTR_QUERY_TIMEOUT.
Set CONNECTTIMEOUT=0 in db2cli.ini. This will cause CLI to wait indefinitely for connections to complete, but will avoid the erroneous timeout described by this APAR.
User's affecter: All Windows, that use cli based applications and multiple CPUs Problem description: Cli connection is timing out before the LOGIN_TIMEOUT is actually elapsed
Problem was first fixed in Version 9.5 Fix Pack 5
Set ConnectTimeout=0 in the db2cli.ini file on the client side where application is running
Reported component name
DB2 CUE WINDOWS
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
DB2 CUE WINDOWS
Fixed component ID
Applicable component levels
21 December 2009