|
Problem IC98689
|
Status: Closed |
WHEN INTERRUPT IS NOT DUE TO QUERYTIMEOUT AND ACR IS ENABLED, CLI MAY GO FOR RETRY. |
| product: |
DB2 CONNECT / DB2CONNCT / A50 - DB2 |
| Problem description: |
When interrupt is driven by application or user, i.e. when CLI
gets SQL30108N with Connection failure code 4 and Underlying
error code 2; CLI is unable to identify that it is an interrupt
and CLI goes for retry. Currently, CLI can know if interrupt is
caused by QueryTimeout and it does not go for retry, but same is
not true when interrupt is caused by application or user. Hence,
for " SQL30108N with Connection failure code 4 and Underlying
error code 2", CLI still goes for retry which it should not. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CLI and .NET driver users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V105FP4 or later releases. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
DB2 V105FP4 (june release) contains the fix of this issue. After
fix, the issue is no longer exist. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.01.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
