IBM Support

IT02013: INSERT/UPDATE/DELETE STATEMENT THAT FIRES A TRIGGER MAY RETURN SQL0901N WITH "SECTION LENGTH MISMATCH"

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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>
    

Local fix

Problem summary

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

Problem conclusion

  • First fixed in DB2 LUW Version 9.7 Fix Pack 10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT02013

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-23

  • Closed date

    2014-11-10

  • Last modified date

    2014-11-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT02032 IT02033

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT02013

Modified date: 10 November 2014