IBM Support

IT21440: INSTANCE CRASH EVENT MONITOR WHEN PERFORMING A LOAD VIA CURSOR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Instance can crash as a result of memory corruption if you have
    the following:
    
    - Event Monitor Created & Enabled.
    - LOAD FROM CURSOR with a very large SQL Statement (~ 16KiB text
    and larger).
    
    As this is memory corruption the faulting stack may vary but is
    likely to include event
    monitor and/or fast writer functions. An example may be:
    
    generateEvent__18sqmEvmonGenFactoryXT19
       sqmEvmonType_policyXSP17SP47SP25SP8_T37
       sqmEvmonUtilLocation_Collector_policy_FP19sqmFastWriterRecord
    + 0xF00
    collectEventData__34sqmEvmonUtilStart_Collector_policyFCPC9sqeBs
       uEduR15sqmRecordHelperCP19sqmFastWriterRecord + 0xFF8
    generateEvent__18sqmEvmonGenFactoryXT19sqmEvmonType_policyXSP17S
       P44SP23SP8_T34sqmEvmonUtilStart_Collector_policy_Fv + 0xC84
    sqmGenerateLoadStartEvent__FCP8sqlrr_cbP26
       sqluCLoadRequestDescriptorP20SQLU_LOADAPI_LOAD_CBP20
       sqlmUtilInvocationIDb + 0x374
    sqlu_register_table_load__FP26sqluCLoadRequestDescriptorP24
       sqlusCLoadMPPCoordinatorP15sql_static_dataPb + 0x1A48
    iRun__24sqlusCLoadMPPCoordinatorFv + 0x80
    ...
    
    It may also trap and fail to produce a stack trace with the
    reported si_addr being the
    hexadecimal representation of an ASCII string.
    

Local fix

  • The issue can be avoided by:
    - Reducing the SQL Statement text size in the CURSOR.
    - Disable the Event Monitors.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Platforms                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 LUW v11.1 Mod 3 Fixpack 3                     *
    ****************************************************************
    

Problem conclusion

  • First Fixed in Db2 LUW v11.1 Mod 3 Fixpack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21440

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-14

  • Closed date

    2018-03-16

  • Last modified date

    2018-03-16

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

    IT21412

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 March 2018