DB2 FOR LUW / DB2FORLUW / A10 - DB2

INSERT and UPDATE statements may experience poor performance 
when the source of such operation references one or more tables 
with column access controls. References to protected tables may 
be directly in the full-select or nested within views, triggers, 
inline SQL functions. Typical queries affected by this issue may 
also include INNER and OUTER JOINS, GROUP BYs, UNION ALL 
operators and will have a WHERE clause, ON clause or HAVING 
clause in the top full-select that is the source for the INSERT 
or UPDATE. 
 
Under such a scenario the predicates present in the WHERE, ON or 
HAVING clauses may not be applied at the base access or a 
sub-optimal join order may be chosen for executing the source of 
the INSERT or UPDATE. 
 
Workarounds 
Rewrite the query to place the predicates directly in lower 
operations of the query.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 UDB Version 10.1 FixPak 5                      * 
****************************************************************

First fixed in DB2 UDB Version 10.1 FixPak 5

not known / see Local fix

Requesting another review.

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

23.03.2015
13.07.2015
13.07.2015