|
Problem IC87547
|
Status: Closed |
-30108 NON-SEAMLESS BEHAVIOUR WHEN SHOULD BE SEAMLESS |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
In the testing, it see that QueryTimeout is 2 &
InterruptProcessingMode is 2.
It is the timing of the sequence of events that can cause this
issue.
When the workload is running, CLI has sent the SQL request to
DRDA. Even before the request has reached the server, the member
has been stopped.
Parallelly, the querytimeout has happened & with interrupt mode
set to 2, the SQLCancel request is triggered. Here some changes
were done in Galileo FP1 to set a interrupt flag. Now since no
request has been sent to the server yet, the interrupt request
gets the message "NO pending request need to be interrupted"
If the interrupt flag is set to TRUE internally, the behaviour
will be treated as non-seamless in CLI & SQL30108N will be sent
to the application. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using sysplex setup. The interrupt processing mode *
* should be 2 & query time out should be set. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V102 FP1 or later releases *
**************************************************************** |
| Local Fix: |
Set InterruptProcessingMode as 0 |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
V101 FP2 fixes the issue |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2012
17.12.2012
17.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
