DB2 - Problembeschreibung
Problem IC95854 | Status: Geschlossen |
ERRORS SUCH AS SQL0313N AFTER A CLI APPLICATION EXECUTES DELETE or UPDATE with WHERE CURRENT OF <cursor-name> clause | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
After an application that uses the CLI (Call Level Interface) API has executed a DELETE or UPDATE statement with WHERE CURRENT OF <cursor-name> clause, applications might get errors such as SQL0313N when they later execute another SQL statement. That is because when a CLI application executes a DELETE or UPDATE statement with WHERE CURRENT OF <cursor-name> clause the CLI package section for a CLI statement handle that is still open might incorrectly be released and then the same CLI package section is reused for a different SQL statement. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of applications that use the CLI (Call Level * * Interface) API to connect to DB2 for Linux, UNIX and Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** | |
Local-Fix: | |
As a workaround you can set the isolation level for the CLI statement handle of the DELETE or UPDATE statement with WHERE CURRENT of clause to be the same as of that of the SELECT ... FOR UPDATE ... statement that created cursor <cursor-name>. You can set the isolation level by setting the CLI statement handle attribute SQL_ATTR_TXN_ISOLATION. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 10.1 Fix Pack 4 At a minimum, this fix should be applied on the client. | |
Workaround | |
As a workaround you can set the isolation level for the CLI statement handle of the DELETE or UPDATE statement with WHERE CURRENT of clause to be the same as of that of the SELECT ... FOR UPDATE ... statement that created cursor <cursor-name>. You can set the isolation level by setting the CLI statement handle attribute SQL_ATTR_TXN_ISOLATION. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95933 IC95934 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.09.2013 27.06.2014 27.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |