|
Problem IC64539
|
Status: Closed |
SQLSETSTMTATTRW(SQL_ATTR_CHAINING_END) RETURNS 0, EVEN WHEN ONE OF THE PREVIOUS CHAINED STATEMENTS FAILED |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
In a CLI application several actions can be chained together.
When one of these actions fail, the ending
SQLSetStmtAttrW(SQL_ATTR_CHAINING_END) should not return with a
SQL_SUCCESS (return status=0).
For example, consider the following scenario:
A SQLExecute() fails with SQL0911 deadlock and the server rolls
back the the transaction. Since this is never reported back, the
application continues the current transaction. This way, we can
end up with a partially written transaction, leading to data
loss and/or logical data inconsistency.
In addition, the SQLRowCount() will report a wrong value after a
partially committed transaction. |
| Problem Summary: |
USERS AFFETCED:
All
PROBLEM DESCRIPTION:
See ERROR DESCRIPTION
PROBLEM SUMMARY:
See ERROR DESCRIPTION |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Problem was first fixed in Version 9.1 Fix Pack 9. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC64540 IC64541 IC64680
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.11.2009
16.04.2010
11.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
