|
Problem IC80623
|
Status: Closed |
IF THE CONNECTION IS DROPPED DUE TO INTERRUPT, IF ACR IS ENABL ED CLI SHOULD NOT TRY SEAMLESS AFTER FAIL-OVER TO NEW MEMBER |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
If the user sets the interrupt=2 in the CLI configuration file.
On a given statement timeout occurs and the connection is
dropped due to interrupt on disconnect processing and ACR is
enabled ACR should be triggered. The connection does not know
its socket was closed due to interrupt handling. In this case
CLI should not drive a seamless retry if the statement was
interrupted after re-route.
If seamalessACR is enabled, CLI should not try seamlessACR
instead throw SQL30108N error. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* CLI users with interrupt is set to 2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the user sets the interrupt=2 in the CLI configuration *
* file. *
* On a given statement timeout occurs, connection is *
* re-routing to another member seamlessly. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.07.6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.01.2012
24.10.2012
24.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.7.6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
