Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
If a user tries to update a row that does not exist, there is no java.sql.SQLException or java.sql.SQLWarning thrown to indicate that the row did not exist. Since the SQLCODE is only trapped through these two objects in Java, the application thinks that the row existed and the update was successful. The problem is with legacy jdbc app/net driver.
Local fix
Use ExecutionContext.getUpdateCount() to get the number of rows updated.
Problem summary
Users Affected: Users Using Legacy JDBC .app or .net driver. Problem Description: When using the JDBC app driver, COM.ibm.db2 .jdbc.app.DB2Driver, or the JDBC net driver, COM.ibm .db2.jdbc.net.DB2Driver, if an update is done to a row that does not exist, java.sql.SQLException or java.sql.SQLWarning will not throw and error to indicate the row does not exist. Problem Summary: When using the JDBC app driver, COM.ibm.db2 .jdbc.app.DB2Driver, or the JDBC net driver, COM.ib .db2.jdbc.net.DB2Driver, if an update is done to a row that doe not exist, java.sql.SQLException or java.sql.SQLWarning will no throw and error to indicate the row does not exist.
Problem conclusion
Problem First Fixed in Version 9 Fixpak 5 (s080512).
Temporary fix
Use ExecutionContext.getUpdateCount() to get the number of rows updated.
Comments
APAR Information
APAR number
JR27415
Reported component name
DB2 CEE WINDOWS
Reported component ID
5765F3001
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-09-12
Closed date
2008-07-02
Last modified date
2008-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 CEE WINDOWS
Fixed component ID
5765F3001
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
12 October 2021