IBM Support

IT30178: POTENTIAL HANG WAITING ON TRANENTRY LATCH IN SQLPM_WRITE_APPL_LOCKS DURING LOCK SNAPSHOT

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

  • When a federated application starts up it will hold the
    tranEntry latch.
    
    Snapshot processing first gets the dblatch and then tries to get
    the tranEntry latch.
    
    It is possible for a hang to occur if a LOCK snapshot is
    processing when such a federated application is preparing to
    commit.
    New connections may hang waiting for the dblatch that the
    snapshot is holding.
    
    Stacks :
    
    Federated Application :
    semop
    sqloSSemP
    sqlccipcrecv
    sqlccrecv
    sqlerFedInvokeFencedRoutine
    sqlriFedInvokeInvoker
    sqlqg_Call_FMP_Thread
    sqlqgFedPrepare
    sqlqgFedPrepareInvoker_
    sqlpxprp IPRA.$sqlr_f2pc
    sqlrrcom_dps
    sqlrrcom
    sqlrr_commit
    executeSection
    executeQuery
    run
    pvm_entry
    ?
    
    
    LatchInformation
    Holding Latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch)
    Holding Latch type: (SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch)
    Holding Latch type: (SQLO_LT_SQLP_SAVEPOINTS__spLatch)
    Holding Latch type: (SQLO_LT_SQLP_TENTRY__subTranChainLatch)
    
    
    Lock Snapshot
    
    sqloXlatchConflict
    sqlpm_write_locks_indoubt_tran
    IPRA.$sqm_snap_db_locks
    sqlmonssagnt
    sqlmonssbackend
    sqlesrvr
    sqleMappingFnServer
    sqlerKnownProcedure
    sqlerCallDL
    sqljs_ddm_excsqlstt
    ?
    
    
    LatchInformation
    Waiting on latch type: (SQLO_LT_SQLP_TENTRY__tranEntryLatch)
    Holding Latch type: (SQLO_LT_sqeLocalDatabase__dblatch)
    Holding Latch type:
    (SQLO_LT_SQLP_TENTRY__snapshotProcessingLatch)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30178

  • 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

    2019-09-04

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

  • 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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020