DB2 FOR LUW / DB2FORLUW / A50 - DB2

The specific conditions to hit this error are: 
-Any Update, insert, Delete or Merge SQL statement containing 
complex triggers may fail with error SQL0901N 
- a MERGE statement with a WHEN MATCHED clause and without WHEN 
NOT MATCHED clause. 
- a large number of triggers invoked or a large number of 
statements in the triggers or involved in some user defined 
function with a large number of statements 
- The MERGE statement can be either within the function / 
triggers or the top level statement being executed. 
 
Following example SQL shows the failure: 
$ db2  "delete from abc where ACTIONID=141" 
 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "RID=<EXP>, 
bad EXP".) 
SQLSTATE=58004

**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using COMPLEX TRIGGERS/FUNCTIONS WITH MERGE ARE     * 
* DEFINED ON THAT TABLE                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5fp3                                      * 
****************************************************************

Workarounds would include reducing the MERGE statement to 
underlying UPDATE or DELETE operation, since there is no WHEN 
NOT MATCHED clause, or simplifying the triggers / functions to 
reduce complexity.

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem fixed in DB2 V10.5fp3

not known / see Local fix

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

06.05.2014
08.09.2014
08.09.2014