|
Problem IC73030
|
Status: Closed |
AT V97FP2, SQL0365N ERROR OCCURS WHEN 'UPDATE ... WHERE CURRENT OF' IS USED BY AN APPLICATION USING JCC DRIVER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
An application using jcc driver gets a -365 error on an execute
immediate.
ErrorID : -365
Error Message : The value of the extended indicator variable in
position "0" is not valid. SQLCODE=-365, SQLSTATE=22539,
DRIVER=3.59.81
The error is detected by sqlriridc due to extended indicator
setting mismatch for the update and the cursor. The extended
indicator is a new function of v97fp2 and it is by default
turned on for jcc driver. The error happens when application
uses 'UPDATE ... where current of' as the following sample.
PreparedStatement stmt1 = conn.prepareStatement("SELECT
C1, C2 FROM T1 WHERE C1 = 1 FOR UPDATE");
Statement stmt2 = conn.createStatement();
ResultSet rs = stmt1.executeQuery();
String cursorname = rs.getCursorName();
while (rs.next())
{
if (rs.getInt("C1") == 1){
int updateCount = stmt2.executeUpdate("UPDATE T1
SET C2='12345' WHERE CURRENT OF " + cursorname);
rs.updateString("C2","12345");
rs.updateRow();
}
} |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* An application using jcc driver gets a -365 error on an *
* execute immediate. *
* *
* ErrorID : -365 *
* Error Message : The value of the extended indicator variable *
* in position "0" is not valid. SQLCODE=-365, SQLSTATE=22539, *
* DRIVER=3.59.81 *
* *
* The error is caused by extended indicator setting mismatch *
* for the update and the cursor. The extended indicator is a *
* new function of v97fp2 and it is by default turned on for *
* jcc driver. The error happens when application uses 'UPDATE *
* ... where current of' . *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 FixPack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This was first fixed by V97 FP4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73226
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
