IT20868: COMPILED COMPOUND SQL OR A PL/SQL ANONYMOUS BLOCK CAN DELETE ALLROWS OF A ON COMMIT DELETE ROWS TEMPORARY TABLE

DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• If an application has created a declared global temporary table
  (DGTT) or has instantiated a created GLOBAL temporary table
  using the ON COMMIT DELETE ROWS option (default), then issuing a
  compiled compound SQL statement or a PL/SQL anonymous block
  might delete all the rows of those tables in that connection,
  even though no commit has been issued.
  

Local fix

• Possible ways to avoid this issue include:
  1. Using the ON COMMIT PRESERVE ROWS option for global temporary
  tables and explicitly delete rows from those tables rather than
  relying on ON COMMIT DELETE rows.
  2. Reworking the compound SQL (or PL/SQL Anonymous block)
  as a procedure that is called.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 11.1 Mod 2 Fix Pack 2
  

Temporary fix

Comments

APAR Information

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

  IT19796

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

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP