IBM Support

JR33398: INSTANCE ABEND POSSIBLE DUE TO INCORRECTION EXECUTION SECTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An instance may abend when copying data into a table queue under
    some very specific access plan conditions.
    A typical trap file may show the following functions on top in
    the stacktrace :
    
    Stack:
    ======================
    
     memmove
     sqlkt_pack_tuple
     sqlktins
     sqlritqb2
    
    
     The problem is due to an incorrect buffer location being
    accessed.
     This can only be confirmed by db2 service personnel by
    examining the "section dump" of the execution plan,
     which is located in the binary dump file.
    
     From an access plan point of view, at least the following
    conditions need to be true  :
     * There is a star join that has a join of a dimension table
    (above the IXAND operator ) that references
     the same columns of the dimension table that were already
    accessed in the star join (below the IXAND operator )
     ( this may also be referred to as a back join )
    * The dimension table column that is accessed in the star join
    is accessed via list prefetching
      i.e. there is a RID scan operator followed by a fetch
    operation on the base table.
    
    * The index scan in the list prefetch of the dimension table
    within the star join has a sargable predicate on a column that
    is used in the back join.
    

Local fix

  • There is no known workaround for this problem, other than to
    force a different access plan to avoid
     at least one of the above conditions.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users in a DPF environment                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Instance crash possible under very specific and              *
    * rareconditions in an SQL access plan.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply db2 v9.5 fixpak 5 at the database server side          *
    ****************************************************************
    

Problem conclusion

  • The problem was first fixed in v9.5 fixpak 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR33398

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-18

  • Closed date

    2010-02-10

  • Last modified date

    2010-02-10

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

    IZ53526

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

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 February 2010