DB2 - Problem description
| Problem IT02033 | Status: Closed |
INSERT/UPDATE/DELETE STATEMENT THAT FIRES A TRIGGER MAY RETURN SQL0901N WITH "SECTION LENGTH MISMATCH" | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
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> | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users running on DB2 Version 10.5 on Linux, Unix and * * Windows platforms and using triggers. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to DB2 LUW Version 10.5 Fix Pack 4 or higher levels. * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
| Solution | |
First fixed in DB2 LUW Version 10.5 Fix Pack 4. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.05.2014 08.09.2014 08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.4 |
|