|
Problem IT39056
|
Status: Closed |
IMPROPER SPECIAL REGISTER CURRENT SCHEMA CAUSING SQLSYNTAXERROREXCEPTION
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem description: |
Type4 connectivity: With heavy transaction load and in a sysplex
enabled environment current schema special registers
are not replayed properly when connected to Db2 on z/OS V12 and
causes SqlSyntaxErrorException.
In a sysplex environment during the WLB, there is transport
switch that happens to distribute the workload across members.
Driver replays the special register values to keep the
connection values same across the members during execution.
Under heavy load, some time the replay was not proper causing
wrong special register replay. In such scenario, when the
current schema is replayed wrongly, it can cause a
SqlSyntaxErrorException from server during SQL execution. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 JCC Users using WLB against Db2 on z/os V12 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to Db2 11.1.4.7 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2 JCC Users using WLB against Db2 on z/os V12 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to Db2 11.1.4.7 *
**************************************************************** |
| Comment |
Problem fixed in Db V11.1.4.7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.11.2021
10.01.2022
24.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
