DB2 FOR LUW / DB2FORLUW / A50 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

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.

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.03.2017
29.09.2017
12.10.2017

9.0.