|
Problem IC68202
|
Status: Closed |
DB2 ENCOUNTERS "UNLOCKING AN UNLATCHED LOCK" ERROR AND PANICS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem 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". |
| 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. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 UDB Version 9.7 FixPak 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC69178
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.04.2010
30.09.2010
30.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
