|
Problem IC63040
|
Status: Closed |
CLI CONNECTIONS TIMEOUT BEFORE THE REQUESTED TIME HAS ACTUALLY ELAPSED (SQL30081N WITH FUNCTION SELECTFORRECVTIMEOUT) |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
User's affected: All |
| Local Fix: |
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. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in v9.7fp1 |
| Workaround |
set connecttimeout=0 explicitly in db2cli.ini file |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.09.2009
26.01.2010
11.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
