Fixes are available
DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
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
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: All users of Legacy JDBC app/net driver Problem 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. Problem Summary: 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.
Problem conclusion
Problem First Fixed on Version 9,5 Fixpak 1 (s080328)
Temporary fix
Comments
APAR Information
APAR number
JR28736
Reported component name
DB2 CEE WINDOWS
Reported component ID
5765F3001
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-03-19
Closed date
2008-05-07
Last modified date
2008-05-07
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
R820 PSY
UP
R910 PSY
UP
R950 PSY
UP
Document Information
Modified date:
06 October 2021