IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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 v10.5 Fixpack 10 or later.                *
    ****************************************************************
    

Problem conclusion

  • First Fixed in Db2 LUW v10.5 Fixpack 10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21412

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-12

  • Closed date

    2018-07-16

  • Last modified date

    2018-07-16

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

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

    IT21440

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"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":"10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 July 2018