DB2 - Problem description
|Problem IC64539||Status: Closed|
SQLSETSTMTATTRW(SQL_ATTR_CHAINING_END) RETURNS 0, EVEN WHEN ONE OF THE PREVIOUS CHAINED STATEMENTS FAILED
DB2 FOR LUW / DB2FORLUW / 910 - DB2
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.
USERS AFFETCED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION
|available fix packs:|
Problem was first fixed in Version 9.1 Fix Pack 9.
not known / see Local fix
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)|
|Problem solved according to the fixlist(s) of the following version(s)|