IBM Support

IT27039: DB2 CRASH OR LONG COMPILATION TIME THAT MIGHT ERROR OUT WITH SQL101N - BOX_COPY__9SQLNQ_QTBFPP9SQLNQ_QTBP9SQLNQ_QURI SQLNR_SUBSU

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • DB2 engine crashes or a query takes a long time to compile or
    may error out with SQL0101N due to running out of statement heap
    during compile
    state.
    
    The problem could occur for queries containing common sub
    expressions (CSE) that have predicates applied against these
    CSEs. This problem can also be observed for queries containing 2
    and more correlated sub-queries that share a common correlated
    source.
    
    Query fails - box_copy__9sqlnq_qtbFPP9sqlnq_qtbP9sqlnq_quri
    sqlnr_subsume_prds_theorem_prover
    
    If you observe DB2 crash, the crashed stack could contain these
    frames:
    
    <StackTrace>
    -------Frame------ ------Function + Offset------
    0x090000000FB84630
    box_copy__9sqlnq_qtbFPP9sqlnq_qtbP9sqlnq_quriN43bT8 + 0x1CB0
    0x09000000113BFE2C
    IPRA.$sqlnr_subsume_prds_theorem_prover__FP9sqlnq_mchP9sqlnq_qtb
    Ri + 0x42C
    0x09000000113BD684
    sqlnr_subsume_prds_sel_sel__FP9sqlnq_mchP9sqlnq_qtbRi + 0x5A4
    0x09000000113B72B4 sqlnr_subsume_prds__FP9sqlnq_mchRi + 0x134
    0x09000000113B2F80
    sqlnr_subsume_derived_match__FP9sqlnq_qtbT1P3locRP9sqlnq_mch20sq
    lnq_ast_match_modei + 0x1160
    0x09000000113AEC40
    sqlnr_subsume_match__FP9sqlnq_qtbT1P3locRP9sqlnq_mch20sqlnq_ast_
    match_modei + 0x3C0
    0x0900000012A5DA54
    IPRA.$sqlnr_adapt_col_4_formcser_detail__FP9sqlnq_qtbT1P3locRbT4
    + 0x5D4
    0x0900000012A5D294
    sqlnr_adapt_col_4_formcser__FP9sqlnq_qtbP3locRbT3 + 0x434
    0x0900000012A5384C IPRA.$sqlnr_optprep_chunk1__FCP9sqlnq_qur +
    0x1C6C
    0x0900000012A51B1C
    sqlnr_optprep_chunk1_action__FP10sqlnr_qrwaPiP14sqlnr_progress +
    0x1C
    0x0900000010F83318
    sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres
    s + 0x218
    0x0900000010F836C4
    sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass +
    0xC4
    0x0900000010F83BC8 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress
    + 0x308
    0x090000001130BF8C sqlnr_exe__FP9sqlnq_qur + 0xF8C
    0x09000000112E75C0
    sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
    lrr_cmpl_enviT7PP9sqlnq_qur + 0x73E0
    0x09000000112E0168
    sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq
    lrr_cmpl_env + 0x28
    0x090000000EB7B55C
    sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_
    LOCK_INFOP16sqlra_cached_varPiT11_Pb + 0xBDC
    0x090000000DAAE0F0
    sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi
    T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14
    SQLP_LOCK_INFOPP16sqlra_cached_varT12_bT19_Pb + 0xA50
    0x090000000EB6DD9C sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0xBFC
    0x090000000E2CFADC
    sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0x57C
    0x09000000136F8230
    sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x12B0
    0x0900000013682C10
    sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
    interface + 0x2B0
    0x0900000013685C64
    sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb +
    0x2264
    0x090000001365221C
    IPRA.$sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xE9C
    0x090000001365AD14
    sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4
    0x09000000136502E0
    IPRA.$sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x13E0
    0x090000001364D734 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
    0x334
    0x090000000CA0D1A0 RunEDU__8sqeAgentFv + 0xB60
    0x090000000C9EFD20 EDUDriver__9sqzEDUObjFv + 0x2E0
    0x090000000C8DEC14 sqloEDUEntry + 0x374
    </StackTrace>
    
    Workaround:
    db2set -im DB2COMPOPT=NO_DERPRD_FF
    

Local fix

  • db2set -im DB2COMPOPT=NO_DERPRD_FF
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to latest fix pack                                   *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT27039

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-11-20

  • Closed date

    2022-03-10

  • Last modified date

    2022-03-10

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022