DB2 FOR LUW / DB2FORLUW / A10 - DB2

During the firing of a trigger as part of an 
INSERT/UPDATE/DELETE (IUD) statement, implicit rebind will be 
driven if the trigger package is found to be invalid. Suppose 
the trigger package gets revalidated successfully, but the 
trigger action fails with an error causing a rollback, the 
changes to the catalog from the implicit rebind is undone, but 
the stale cached package is left in the package cache. The next 
IUD statement that fires the same trigger may hit SQL0901N with 
"Section length mismatch" when trying to load the section from 
the system catalog to the package cache. 
 
A diaglog entry similar to this will be produced: 
 
2014-02-21-03.08.06.712025-300 I6628233A914         LEVEL: 
Severe 
PID     : 13697272             TID : 19900          KTID : 
93192261 
PROC    : db2sysc 
INSTANCE:              NODE : 000           DB   : TPCDS 
APPHDL  : 0-138                APPID: 
AUTHID  :              HOSTNAME: 
EDUID   : 19900                EDUNAME: db2agent (TPCDS) 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 23 
 sqlerrmc: Section length mismatch 
 sqlerrp : SQLRA01D 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFEA2      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
Stack Trace will show these functions: 
 
<StackTrace> 
sqlra_cache_fill_sec 
sqlra_find_sect 
sqlra_get_section 
sqlrr_sql_request_pre 
</StackTrace>

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running on DB2 Version 10.1 on Linux, Unix and     * 
* Windows platforms and using triggers.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 10.1 Fix Pack 5 or higher levels.  * 
****************************************************************

First fixed in DB2 LUW Version 10.1 Fix Pack 5.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.05.2014
13.07.2015
13.07.2015