DB2 FOR LUW / DB2FORLUW / A10 - DB2

If you have a TRIGGER which accesses the same table more than 
once you might received a SQL0101N. 
 
This can be demonstrated with following example which does 
produce the same error as customer 
 
create table t1 (c1 int ) @ 
CREATE OR REPLACE TRIGGER trig1 
  AFTER INSERT ON t1 
  FOR EACH row MODE DB2SQL 
  BEGIN ATOMIC 
  insert into t1 values 1; 
  insert into t1 values 2; 
  end @ 
 
insert into t1 values 1 @ 
 
SQL0101N  The statement was not processed because a limit such 
as a 
      memory limit, an SQL limit, or a database limit was 
reached. 
 
Explanation: 
 
This message can be returned when an attempt is made to prepare 
or 
execute an SQL statement that exceeds a limit such as a memory 
limit, an 
SQL limit, or a database limit. In this context, "memory limits" 
include 
the following examples: 
 
*  Statement heap (STMTHEAP) 
*  Application heap (APPLHEAPSZ) 
*  Application memory (APPL_MEMORY) 
*  Instance memory (INSTANCE_MEMORY) 
*  Other process or system memory limits

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 luw                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v105 fixpack 5                                * 
****************************************************************

Contact DB2 Support

Upgrade to db2 v105 fixpack 5

not known / see Local fix

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

10.03.2015
13.07.2015
13.07.2015