|
Problem IT35681
|
Status: Closed |
CLI DRIVER FAILING TO RETURN
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem description: |
When array input statements are executed through chaining and if
first record in chaining cause any error (Ex; -803) then any
subsequent errors are skipped which are received after executing
rest of statements in chaining.
Example:
when multiple processes run INSERT ? ACCEPTING DUPLICATE KEYS
statements in parallel and get deadlocked, the deadlock SQL
error is not returned by CLI, Therefore the application is
unaware of the implicit rollback, reporting false info to the
user.
From a user's perspective, this is data loss. From the db2
traces, the server sends the SQL0911N or SQL1476N/911, but the
same is not returned to the application
This scenario can happen when the first record in the chain
caused an error e.g:-803 at the server and hence subsequent
errors like -911 that might be hit in certain scenarios are not
reported back to the application. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL Db2 Connect Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v11.1.4.6 and later *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* ALL Db2 Connect Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v11.1.4.6 and later *
**************************************************************** |
| Comment |
Fixed in v11.1.4.6 and later |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.01.2021
30.06.2021
30.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
