DB2 - Problembeschreibung
Problem IC64539 | Status: Geschlossen |
SQLSETSTMTATTRW(SQL_ATTR_CHAINING_END) RETURNS 0, EVEN WHEN ONE OF THE PREVIOUS CHAINED STATEMENTS FAILED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
USERS AFFETCED: All PROBLEM DESCRIPTION: See ERROR DESCRIPTION PROBLEM SUMMARY: See ERROR DESCRIPTION | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Lösung | |
Problem was first fixed in Version 9.1 Fix Pack 9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64540 IC64541 IC64680 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.11.2009 16.04.2010 11.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP9 | |
Problem behoben lt. FixList in der Version | |
9.1.0.9 |