DB2 FOR LUW / DB2FORLUW / 950 - 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 AFFECTED: 
All 
 
PROBLEM DESCRIPTION: 
See ERROR DESCRIPTION 
 
PROBLEM SUMMARY: 
See ERROR DESCRIPTION

DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 UDB Version 9.5, FixPak 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.11.2009
15.12.2009
11.12.2010

9.5.