IBM Support

IT34696: MEMORY CRASH/TRAP WITH LOCAL PREDICATE ON OJ SUBSELECT

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

  • db2 query may abend when the following conditions are met:
    
    -There is at least one inner join
    
    -There is at least one outer join under the inner join
    
    -There are multiple local predicates on one of the branches of
    outer join
    
    stack of trap shows:
    <StackTrace>
    -------Frame------ ------Function + Offset------
    0x0900000000536014 pthread_kill + 0xD4
    0x0900000000535864 _p_raise + 0x44
    0x09000000000398E8 raise + 0x48
    0x09000000000562E4 abort + 0xC4
    0x090000001C0B85F8 sqloExitEDU + 0x298
    0x090000001C125144 sqle_panic__Fi + 0x7A4
    0x090000001C0D7CA8 sqloCrashOnCriticalMemoryValidationFailure +
    0x48
    0x090000001C143270
    diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb +
    0x4F0
    0x090000001C14AA44
    MemTreeGet__13SQLO_MEM_POOLFCUlT1PP17SqloChunkSubgroupPUi +
    0x864
    0x090000001C142BBC
    allocateMemoryBlock__13SQLO_MEM_POOLFCUlT1UiT1PP17SqloChunkSubgr
    oupPUiCP12SMemLogEvent + 0xFC
    0x090000001C0D2FA0 sqloGetMemoryBlockExtended + 0xAA0
    0x090000001F8A5F40
    IPRA.$sqlnr_reorder_OJ_qgm_action__FCP9sqlnq_oprR17sqlnq_qunElem
    ListT2PP13sqlnq_deplistPiRP9sqlnq_qtbCP3loc + 0x180
    0x090000001F8975E4
    sqlnr_reorder_IJ_qgm__FCP9sqlnq_qunCP9sqlnq_oprPP13sqlnq_deplist
    PiRP9sqlnq_qtbCP3loc + 0x1DE4
    0x090000001F86A3B0 sqlnr_qrwprep_phase2__FP3locPi + 0x3B50
    0x090000001F8EA84C
    sqlnr_prep2_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x4C
    0x090000001F77DC98
    sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres
    s + 0x218
    0x090000001F77E044
    sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass +
    0xC4
    0x090000001F77E548 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress
    + 0x308
    0x090000001F8EBE34 sqlnr_exe__FP9sqlnq_qur + 0x854
    0x090000001F9794A0
    sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
    lrr_cmpl_enviT7PP9sqlnq_qur + 0x74C0
    0x090000001F971F68
    sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
    lrr_cmpl_env + 0x28
    0x0900000021930EE4
    sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_
    LOCK_INFOP16sqlra_cached_varPiT11_Pb + 0xBE4
    0x090000001CE267E4
    sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi
    T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14
    SQLP_LOCK_INFOPP16sqlra_cached_varT12_bT19_Pb + 0xA84
    0x0900000021922C70 sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0xC50
    0x090000001E1D9920 sqlrr_execute_immediate__FP8sqlrr_cbi +
    0x3120
    0x090000001E18057C
    sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x87C
    0x09000000235ADBE0
    sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0x1220
    0x09000000235221C8
    sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
    interface + 0x268
    0x0900000023525264
    sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
    0x2264
    0x09000000234F023C
    IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C
    0x09000000234F8954
    sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4
    0x09000000234EE2F0
    IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13F0
    0x09000000234EB73C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
    0x33C
    0x090000001C1F6C20 RunEDU__8sqeAgentFv + 0xB60
    0x090000001C1D0E40 EDUDriver__9sqzEDUObjFv + 0x300
    0x090000001C0B1E00 sqloEDUEntry + 0x360
    

Local fix

  • Set DB2_ANTIJOIN=NO
    
    or set optimization level to less or equal to 1
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6 or higher                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1.4.6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34696

  • 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

    2020-10-27

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

  • 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

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

Document Information

Modified date:
01 April 2021