DB2 FOR LUW / DB2FORLUW / 970 - 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. The issue will be fixed in 10.5 fp 9  *
* and v11 fp2.                                                 *
****************************************************************
* RECOMMENDATION:                                              *
* The issue will be fixed in 10.5 fp 9 and v11 fp2.            *
****************************************************************

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.

not known / see Local fix

forerunner  : IT19796 
follow-up : 

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

21.03.2017
31.07.2017
31.07.2017

9.0.