home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT02239 Status: Closed

SQL AGAINST A TABLE FAILS WITH ERROR SQL0901N , WHEN COMPLEX
TRIGGERS/FUNCTIONS WITH MERGE ARE DEFINED ON THAT TABLE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customer using DB2 using complex triggers or functions with  * 
* MERGE                                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7fp10                                      * 
****************************************************************
Local Fix:
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.
Solution
Fixed in V9.7 fp10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.06.2014
18.11.2014
18.11.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList