IBM Support

IC68202: DB2 ENCOUNTERS "UNLOCKING AN UNLATCHED LOCK" ERROR AND PANICS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2 may encounter "unlocking an unlatched lock" error and then
    panic. In db2diag.log you will see error message similar to the
    following:
    =========================================
    2010-01-01-01.01.01.123456+123 I1234567A1234      LEVEL: Severe
    PID     : 123456               TID  : 123456      PROC : db2sysc
    0
    INSTANCE: peadmin              NODE : 000         DB   : SAMPLE
    APPHDL  : 0-12345              APPID: *LOCAL.HOST1.123456789012
    AUTHID  : DB2INST1
    EDUID   : 123456               EDUNAME: db2agntp 0
    FUNCTION: DB2 UDB, SQO Latch Tracing,
    sqlo_xlatch::releaseConflict, probe:10
    DATA #1 : String, 27 bytes
    unlocking an unlatched lock
    DATA #2 : Pointer, 8 bytes
    0x0700000021632c30
    DATA #3 : String, 103 bytes
    {
       lock          = { 0x00000000 [ unlocked ] }
       identity      = SQLS_SLDES::serializeWrite (365)
    }
    DATA #4 : Hexdump, 8 bytes
    0x0700000021632C30 : 0000 0000 016D 0000
    .....m..
    CALLSTCK:
      [0] 0x09000000056F81F4 pdLog + 0xFC
      [1] 0x0900000001528E4C pdLog@glue3EE + 0x12C
      [2] 0x090000000189BFE4 sqloSpinLockReleaseConflict + 0x60
      [3] 0x090000000586CC58 sqloSpinLockReleaseConflict@glue7C +
    0x78
      [4] 0x09000000017E1094
    sqloxult_track__FCP11sqlo_xlatchC14SQLO_LT_VALUES@glueFFC + 0x4
      [5] 0x0900000002E95CA0
    sqlsBinSortIncremental__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi +
    0x3D4
      [6] 0x09000000058A6BEC
    sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQLD_CCBPcPUcP12sqlri_
    vectorPP10SQLD_VALUE
    + 0x424
      [7] 0x090000000570E618
    sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQLD_CCBPcPUcP12sqlri_
    vectorPP10SQLD_VALUE@glue141D
    + 0x9C
      [8] 0x0900000002E8D3FC
    sqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri_iudo + 0x36C
      [9] 0x09000000058A38D4
    sqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri_iudo@glue1019 +
    0x98
    =========================================
    
    Please check the "identity" section of the diagnostic
    information to make sure the problematic latch is
    "serializeWrite".
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of version 9.7 on Linux, Unix and                  *
    * Windowsplatforms.                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DB2 may encounter "unlocking an unlatched lock" error        *
    * andthen panic. In db2diag.log you will see error             *
    * messagesimilar to the                                        *
    * following:=========================================2010-01-01-
    * I1234567A1234      LEVEL:SeverePID     : 123456              *
    *  TID  : 123456      PROC :db2sysc 0INSTANCE: peadmin         *
    *      NODE : 000         DB   :SAMPLEAPPHDL  : 0-12345        *
    *       APPID:*LOCAL.HOST1.123456789012AUTHID  : DB2INST1EDUID *
    *   : 123456               EDUNAME: db2agntp 0FUNCTION: DB2    *
    * UDB, SQO Latch Tracing,sqlo_xlatch::releaseConflict,         *
    * probe:10DATA #1 : String, 27 bytesunlocking an unlatched     *
    * lockDATA #2 : Pointer, 8 bytes0x0700000021632c30DATA #3 :    *
    * String, 103 bytes{lock          = { 0x00000000 [ unlocked ]  *
    * }identity      = SQLS_SLDES::serializeWrite (365)}DATA #4 :  *
    * Hexdump, 8 bytes0x0700000021632C30 : 0000 0000 016D          *
    * 0000.....m..CALLSTCK:[0] 0x09000000056F81F4 pdLog + 0xFC[1]  *
    * 0x0900000001528E4C pdLog@glue3EE + 0x12C[2]                  *
    * 0x090000000189BFE4 sqloSpinLockReleaseConflict + 0x60[3]     *
    * 0x090000000586CC58 sqloSpinLockReleaseConflict@glue7C+       *
    * 0x78[4]                                                      *
    * 0x09000000017E1094sqloxult_track__FCP11sqlo_xlatchC14SQLO_LT_V
    * +0x4[5]                                                      *
    * 0x0900000002E95CA0sqlsBinSortIncremental__FP8sqeAgentP10SQLS_S
    * 0x3D4[6]                                                     *
    * 0x09000000058A6BECsqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQ
    * 0x424[7]                                                     *
    * 0x090000000570E618sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQ
    * 0x9C[8]                                                      *
    * 0x0900000002E8D3FCsqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri
    * + 0x36C[9]                                                   *
    * 0x09000000058A38D4sqlrsopen__FP8sqlrr_cbP9sqlri_taoiT3P10sqlri
    * +0x98=========================================Please check   *
    * the "identity" section of the diagnosticinformation to make  *
    * sure the problematic latch is"serializeWrite".               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 UDB Version 9.7 FixPak 3 or higher levels.    *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.7 FixPak 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68202

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-27

  • Closed date

    2010-09-30

  • Last modified date

    2010-09-30

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

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

    IC69178

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC68202

Modified date: 30 September 2010