JR27140: SQL "NO DATA FOUND" IS NOT RETURNED WHEN UPDATING A ROW THAT DOESNOT EXIST.

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

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

• User's Affected: All
  Problem summary:   SQL0100W /SQLSTATE 2000 IS NOT RETURNED WHEN
  UPDATING A ROW THAT DOES NOT EXIST.
  
  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 conclusion

• First fixed in v8fp16
  

Temporary fix

• Use ExecutionContext.getUpdateCount() to get the number of rows
  updated.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR27415

Fix information

• Fixed component name

  DB2 CEE WINDOWS

• Fixed component ID

  5765F3001

Applicable component levels

• R820 PSY

     UP