IBM Support

IC80616: Crash in SQL PL associative arrays when allocating memory for new array elements

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using SQL PL associative arrays the DB2 instance may crash
    with a segmentation fault (signal #11 on Unix/Linux) or memory
    access violation (C0000005 on Windows) with the following stack:
    
    <redBlackTree::rbGetFirstNode>
    <associativeArrayHeader::getFirstNode>
    <associativeArrayHeader::getFirstIndex>
    <sqlriArrayDescriptor::destroyAllChildren>
    <sqlriArrayDescriptor::allocateDyn>
    <sqlriArrayDescriptor::setElement>
    <PVM::setArrayElement>
    <PVM::run>
    <pvm_entry>
     <sqloInvokeFnArgs>
    <sqlriInvokerTrusted>
    <sqlriInvokeInvoker>
    <sqlricall>
    <sqlriSectInvoke>
    <sqlrr_process_execute_request>
    <sqlrr_execute>
    <sqljs_ddm_excsqlstt>
    <sqljsParse>
    <sqljsSqlam>
    <sqljsDriveRequests>
    <sqljsDrdaAsInnerDriver>
    <sqljsDrdaAsDriver>
    <sqeAgent::RunEDU>
    <sqlzRunEDU>
    <sqloInitEDUServices>
    
    This issue is caused by a logic problem during the error
    handling of a failure to allocate memory from the application
    heap for new elements in a SQL PL associative array.
    
    This APAR will fix the error handling to remove the crashing
    conditions such that the correct memory allocation failure
    message (such as SQL20442) will be returned.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v9.7 Fixpack 6.                                   *
    ****************************************************************
    

Problem conclusion

  • Problem first fixed in v9.7 Fixpack 6.  This fix should be
    applied to the DB2 server.
    

Temporary fix

  • See LOCAL FIX.
    

Comments

APAR Information

  • APAR number

    IC80616

  • 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

    2011-12-29

  • Closed date

    2012-06-04

  • Last modified date

    2012-06-04

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

    IC80615

  • 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

  • R950 PSN

       UP

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC80616

Modified date: 04 June 2012