IBM Support

IZ56540: SQLPUPGRADELOCK () : CANNOT FIND HEADER ERROR, AFTER LOCK ESCALATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • On a multi-node system, with MDC in use on the table, one of the
    DB2 agents escalates locks and soon after another DB2 agent
    could get dumped with an error indicated from sqlpUpgradeLock()
    , while tryig to dalete a row.
    
    db2diag,.log marks
    
    
    2008-11-20-07.37.44.918025-300 I31144528A782      LEVEL: Error
    PID     : 3809518              TID  : 120203      PROC : db2sysc
    5
    INSTANCE: svtdbm5              NODE : 005         DB   : SLEE
    APPHDL  : 15-3780              APPID: *N5.svtdbm5.081120123549
    AUTHID  : SVTDBM5
    EDUID   : 120203               EDUNAME: db2agntp (SLEE) 5
    FUNCTION: DB2 UDB, lock manager, sqlpUpgradeLock, probe:560
    MESSAGE : Cannot find header!
    DATA #1 : Hexdump, 64 bytes
    0x0700000161BFD428 : 0008 0055 0000 0000 0006 0000 6200 0000
    ...U........b...
    0x0700000161BFD438 : 0000 0000 0000 0000 0000 0002 0000 0002
    ................
    0x0700000161BFD448 : 0000 0000 0000 0005 0000 0001 0000 6021
    ..............`!
    0x0700000161BFD458 : 0000 0000 0000 0000 0000 0001 0000 0000
    ................
    
    2008-11-20-07.37.44.937763-300 I31145311A492      LEVEL: Severe
    PID     : 3809518              TID  : 120203      PROC : db2sysc
    5
    INSTANCE: svtdbm5              NODE : 005         DB   : SLEE
    APPHDL  : 15-3780              APPID: *N5.svtdbm5.081120123549
    AUTHID  : SVTDBM5
    EDUID   : 120203               EDUNAME: db2agntp (SLEE) 5
    FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler,
    probe:100
    MESSAGE : DIA0505I Execution of a component signal handling
    function has begun.
    
    2008-11-20-07.37.44.938182-300 I31145804A702      LEVEL: Severe
    PID     : 3809518              TID  : 120203      PROC : db2sysc
    5
    INSTANCE: svtdbm5              NODE : 005         DB   : SLEE
    APPHDL  : 15-3780              APPID: *N5.svtdbm5.081120123549
    AUTHID  : SVTDBM5
    EDUID   : 120203               EDUNAME: db2agntp (SLEE 5
    FUNCTION: DB2 UDB, relation data serv, sqlrr_signal_handler,
    probe:125
    MESSAGE : MASTER TIME INFO
    DATA #1 : Hexdump, 40 bytes
    0x070000084A5EF358 : 0000 0000 4924 4997 0363 0000 000D 3AC8
    ....I$I..c....:.
    0x070000084A5EF368 : 0007 DC7A E5FB F043 0000 0000 0055 50AC
    ...z...C.....UP.
    0x070000084A5EF378 : 8007 DC7A E5FB F042
    ...z...B
    
    Stack Trace Shows :
    
    
    0x090000000042B5BC pthread_kill + 0x88
    0x09000000053F6DA8 sqloDumpEDU + 0x24
    0x0900000005920B3C sqlpUpgradeLock__FP8sqeAgentP14SQLP_LOCK_INFO
    + 0x1A60
    0x0900000007290944
    sqldMDCLogAndDeleteRecord__FP13SQLD_DFM_WORKP8SQLD_TCBiT3 +
    0x498
    0x09000000061C1554 sqldRemoveRow__FP13SQLD_DFM_WORKi + 0x558
    0x09000000061D27A0 sqldDeleteRow__FP13SQLD_DFM_WORKPci + 0x274
    0x09000000061E1CD0 sqldRowDelete__FP8sqeAgentP8SQLD_CCBUl +
    0x28C
    0x0900000006213930 sqlridel__FP8sqlrr_cb + 0x408
    0x0900000006602BAC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
    0xE8
    0x090000000773FDC4 sqlrr_dss_router__FP8sqlrr_cb + 0x8F0
    0x0900000006C473DC
    sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xEBC
    0x0900000006C436FC sqleSubRequestRouter__FP8sqeAgentPUiT2 +
    0x7E0
    0x0900000006C3F9F4 sqleProcessSubRequest__FP8sqeAgent + 0x120
    0x0900000006628878 RunEDU__8sqeAgentFv + 0x330
    0x0900000006687EA0 EDUDriver__9sqzEDUObjFv + 0x78
    0x09000000066861D8 sqloEDUEntry + 0x3A0
    

Local fix

  • reducing the possibilty of lock escalation will lower the
    probility of this issue occuring.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DPF users, MDC tables                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In DPF environments where there are MDC tables and lock      *
    * escalations, there exists the possibility that one of the    *
    * DB2 agents could return an error and end prematurely dumping *
    * its stack.  The db2diag.log message would indicate this      *
    * error message.                                               *
    *                                                              *
    * 2008-11-20-07.37.44.918025-300 I31144528A782      LEVEL:     *
    * Error                                                        *
    * PID     : 3809518              TID  : 120203      PROC :     *
    * db2sysc 5                                                    *
    * INSTANCE: svtdbm5              NODE : 005         DB   :     *
    * SLEE                                                         *
    * APPHDL  : 15-3780              APPID:                        *
    * *N5.svtdbm5.081120123549                                     *
    * AUTHID  : SVTDBM5                                            *
    * EDUID   : 120203               EDUNAME: db2agntp (SLEE) 5    *
    * FUNCTION: DB2 UDB, lock manager, sqlpUpgradeLock, probe:560  *
    * MESSAGE : Cannot find header!                                *
    * DATA #1 : Hexdump, 64 bytes                                  *
    * 0x0700000161BFD428 : 0008 0055 0000 0000 0006 0000 6200 0000 *
    *    ...U........b...                                          *
    * 0x0700000161BFD438 : 0000 0000 0000 0000 0000 0002 0000 0002 *
    *    ................                                          *
    * 0x0700000161BFD448 : 0000 0000 0000 0005 0000 0001 0000 6021 *
    *    ..............`!                                          *
    * 0x0700000161BFD458 : 0000 0000 0000 0000 0000 0001 0000 0000 *
    *    ................                                          *
    *                                                              *
    *                                                              *
    * The stack dump would be as follows.                          *
    *                                                              *
    * 0x090000000042B5BC pthread_kill + 0x88                       *
    * 0x09000000053F6DA8 sqloDumpEDU + 0x24                        *
    * 0x0900000005920B3C                                           *
    * sqlpUpgradeLock__FP8sqeAgentP14SQLP_LOCK_INFO + 0x1A60       *
    * 0x0900000007290944                                           *
    * sqldMDCLogAndDeleteRecord__FP13SQLD_DFM_WORKP8SQLD_TCBiT3 +  *
    * 0x498                                                        *
    * 0x09000000061C1554 sqldRemoveRow__FP13SQLD_DFM_WORKi + 0x558 *
    * 0x09000000061D27A0 sqldDeleteRow__FP13SQLD_DFM_WORKPci +     *
    * 0x274                                                        *
    * 0x09000000061E1CD0 sqldRowDelete__FP8sqeAgentP8SQLD_CCBUl +  *
    * 0x28C                                                        *
    * 0x0900000006213930 sqlridel__FP8sqlrr_cb + 0x408             *
    * 0x0900000006602BAC                                           *
    * sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0xE8           *
    * 0x090000000773FDC4 sqlrr_dss_router__FP8sqlrr_cb + 0x8F0     *
    * 0x0900000006C473DC                                           *
    * sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xEBC    *
    * 0x0900000006C436FC sqleSubRequestRouter__FP8sqeAgentPUiT2 +  *
    * 0x7E0                                                        *
    * 0x0900000006C3F9F4 sqleProcessSubRequest__FP8sqeAgent +      *
    * 0x120                                                        *
    * 0x0900000006628878 RunEDU__8sqeAgentFv + 0x330               *
    * 0x0900000006687EA0 EDUDriver__9sqzEDUObjFv + 0x78            *
    * 0x09000000066861D8 sqloEDUEntry + 0x3A0                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 9.5 fp5                                       *
    ****************************************************************
    

Problem conclusion

  • Once this fix is installed the DPF environment with MDC tables,
    the lock escalations will proceed properly and all agents will
    continue processing normally without the error as seen
    previously.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ56540

  • Reported component name

    DB2 UDB WSE AIX

  • Reported component ID

    5765F3500

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-02

  • Closed date

    2010-02-17

  • Last modified date

    2010-03-08

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

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

    IC62381

Fix information

  • Fixed component name

    DB2 UDB WSE AIX

  • Fixed component ID

    5765F3500

Applicable component levels

  • R950 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"950"}]

Document Information

Modified date:
03 October 2021