IBM Support

IV93868: A DEADLATCH AND HANG OCCURS WHEN ALTERING A TABLE TO ATTACH A PARTITION WITH XML INDEXES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A deadlatch occurs when altering a table to attach a partition
    and there are XML indexes.
    
    During the hang the stack of the self deadlocked db2agent will
    resemble:
    0x0900000000111894 thread_wait + 0x94
    0x0900000145BA1664 getConflictComplex__17SQLO_SLATCH_CAS64FCUl +
    0x6E4
    0x0900000145BA1D64 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x84
    0x0900000147924E70
    sqliIP_CreatePage__FP7SQLI_CBP14SQLI_PAGE_DESCUi + 0x1E50
    0x0900000147922D48
    sqliIP_FixPage__FP7SQLI_CBP14SQLI_PAGE_DESCiUiPUl + 0x1A8
    0x09000001498241BC sqliHardenJITS__FP7SQLI_CBP14SQLI_PAGE_DESCUl
    + 0x217C
    0x09000001468A4A3C
    sqliaddk__FP8sqeAgentP9SQLD_IXCBP8SQLD_KEY12SQLI_KEYDATAP14SQLP_
    LOCK_INFOP8SQLP_LRBUlP10SQLI_IXPCRPPv + 0x113C
    0x0900000148F3DC2C
    sqliInsertIntoIndex__FP7SQLI_CBP10SQLD_IPRED12SQLI_KEYDATA +
    0xEC
    0x0900000148F2D6EC
    IPRA.$sqliScanLeaf2NoLocking__FP7SQLI_CBP11SQLI_SFGLOB + 0x292C
    0x0900000148F23CE0 sqlifnxt__FP7SQLI_CBP11SQLI_SFGLOB + 0xEC0
    0x090000014688C254
    sqlirdk__FP8sqeAgentP10SQLI_IXPCRP9SQLD_IXCBUlP8SQLD_KEYP12SQLI_
    KEYDATAP9sqli_scanPi + 0x2374
    0x090000014695A058 sqldIndexFetch__FP8SQLD_CCBP8SQLZ_RID + 0x9B8
    0x090000014695D46C
    sqldRowFetch__FP8sqeAgentP8SQLD_CCBUlT3PP10SQLD_VALUEP8SQLZ_RIDT
    3P12SQLD_ID_LISTP9SQLP_LSN8 + 0xAEC
    0x09000001486CBDC4
    sqldScanInx1AndPopInx2__FP8sqlrr_cbUsT2UcPUcT2T5N32T4T5T2T5T2 +
    0x1BC4
    0x0900000148D62964
    sqlrlAltAttPopXMLPathInxsLocalNode__FP8sqlrr_cbUsT2UcPUcT2T5N22T
    4P8sqlrg_idN22T4T5T2T5N22T4T11_ + 0x164
    0x0900000148D631B0
    sqlrlAlterAttachMaintainXMLPathInxs__FP8sqlrr_cbP8sqlrg_pdP18sql
    rg_datapartinfoPUcUsT4T5T2T3T4T5T4T5 + 0x1D0
    0x0900000148D66304
    sqlrlAlterPartitionOps__FP8sqlrr_cbPUcUsT2T3UcT2T3T2T3P17sqlrl_t
    able_parmsPP8sqlrg_pdN23P18sqlrg_datapartinfo + 0x2F24
    0x0900000148D93500
    sqlrlalt__FP8sqlrr_cbPUcsT2T3T2T3T2T3P8sqlrg_pdP17sqlrl_table_pa
    rmsilP18sqlrg_datapartinfoPbbP9sqlnq_ftbT16_ + 0xE760
    
    The db2pd -latch output will resemble:
    Database Member 0 -- Active -- Up 0 days 00:56:47 -- Date
    2017-02-24-00.57.25.940680
    
    Latches:
    Address            Holder     Waiter     Filename
    LOC        LatchType            HoldCount
    0x078000000C1A0478 1543       0
    ../include/sqle_workload_disp.h 53
    SQLO_LT_sqeWLDispatcher__m_tunerLatch 1
    0x07000000A10C0CF8 21126      0
    /view/db2_v111m1fp1_aix64_s1612051900/vbs/engn/include/sqlpSavep
    oint.h 72         SQLO_LT_SQLP_SAVEPOINTS__spLatch 1
    0x07000000BD9D9780 21126      0          sqldmopn.C
    2293       SQLO_LT_SQLD_TCB_LOTCH__tcbIndexValidityLotch 1
    0x07000000AA796C58 21126      0          sqlbfix_statics.C
    1472       SQLO_LT_SQLB_BPD__bpdLatch_SX S
    0x07000000AA789938 21126      0          sqlbfix_statics.C
    1472       SQLO_LT_SQLB_BPD__bpdLatch_SX S
    0x07000000BCE5E5F0 22691      0
    /view/db2_v111m1fp1_aix64_s1612051900/vbs/engn/include/sqldtm_in
    lines.h 338        SQLO_LT_SQLD_TCB__tcbExist 1
    
    Latch Waiters With No Holders:
    Address            Holder     Waiter     Filename
    LOC        LatchType
    0x07000000BCE5E680 0          21126
    /view/db2_v111m1fp1_aix64_s1612051900/vbs/engn/include/sqldtm_in
    lines.h 839        SQLO_LT_SQLD_TCB_LOTCH__tcbIndexValidityLotch
    0x07000000BCE5E680 0          22691
    /view/db2_v111m1fp1_aix64_s1612051900/vbs/engn/include/sqldtm_in
    lines.h 1113       SQLO_LT_SQLD_TCB_LOTCH__tcbIndexValidityLotch
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV93868

  • Reported component name

    DB2 PURESCALE F

  • Reported component ID

    5724Y6900

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-01

  • Closed date

    2017-06-28

  • Last modified date

    2017-06-28

  • 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 PURESCALE F

  • Fixed component ID

    5724Y6900

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU029","label":"Software"},"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:
01 August 2020