IC64539: SQLSETSTMTATTRW(SQL_ATTR_CHAINING_END) RETURNS 0, EVEN WHEN ONE OF THE PREVIOUS CHAINED STATEMENTS FAILED

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

• In a CLI application several actions can be chained together.
  When one of these actions fail, the ending
  SQLSetStmtAttrW(SQL_ATTR_CHAINING_END) should not return with a
  SQL_SUCCESS (return status=0).
  
  For example, consider the following scenario:
  A SQLExecute() fails with SQL0911 deadlock and the server rolls
  back the the transaction. Since this is never reported back, the
  application continues the current transaction. This way, we can
  end up with a partially written transaction, leading to data
  loss and/or logical data inconsistency.
  
  In addition, the SQLRowCount() will report a wrong value after a
  partially committed transaction.
  

Local fix

Problem summary

• USERS AFFETCED:
  All
  
  PROBLEM DESCRIPTION:
  See ERROR DESCRIPTION
  
  PROBLEM SUMMARY:
  See ERROR DESCRIPTION
  

Problem conclusion

• Problem was first fixed in Version 9.1 Fix Pack 9.
  

Temporary fix

Comments

APAR Information

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

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

  IC64540 IC64541 IC64680

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• R820 PSN

     UP

• R910 PSN

     UP

• R950 PSN

     UP

• R970 PSN

     UP

• R980 PSN

     UP