home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC73925 Status: Geschlossen

DB2 MIGHT ENCOUNTER "UNLOCKING AN UNLATCHED LOCK" ERROR AND THE
INSTANCE WILL BE SHUT DOWN.

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
DB2 might encounter "unlocking an unlatched lock" error and the 
instance will be shut down. 
 
In db2diag.log you will see messages similar to the following: 
================================== 
2010-01-01-01.01.01.123456+789 I123456789A12345   LEVEL: Severe 
PID     : 1234567              TID  : 1           PROC : 
db2agent (idle) 7 
INSTANCE: DB2INST1             NODE : 001         DB   : SAMPLE 
APPHDL  : 0-1234               APPID: 
192.168.1.1.12345.10121223410 
AUTHID  : DB2INST1 
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 
0x07800000001c7088 
DATA #3 : String, 108 bytes 
{ 
   lock          = { 0x00000000 [ unlocked ] } 
   identity      = SQLE_APP_GROUP_CB::appGroupLatch (81) 
} 
DATA #4 : Hexdump, 8 bytes 
0x07800000001C7088 : 0000 0000 0051 0000 
.....Q.. 
CALLSTCK: 
  [0] 0x0900000002DE882C sqloSpinLockReleaseConflict + 0xEC 
  [1] 0x090000000411E390 
@49@3@sqloexcs_notrack__FP12sqloSpinLock + 0x0 
  [2] 0x090000000393DC20 
sqleSubsequentConnect__FP7sqlebwaP8sqledbcbP20sqle_agent_private 
cbUcP8sqlo_gmt 
+ 0xF0 
  [3] 0x0900000003FF6A2C 
sqleserl__FP7sqlebwaP13sqle_agent_cbRccP8sqlo_gmt + 0x850 
  [4] 0x0900000004015098 
sqlesrsu__FP7sqlebwaP13sqle_agent_cbcT3P5sqlcaPc + 0x2A4 
  [5] 0x0900000003FBC02C 
sqleSecondaryStartUsing__FP13sqle_agent_cbP14sqleClientInfo + 
0x278 
  [6] 0x0900000002E4C94C sqleInitSubAgent__FP13sqle_agent_cb + 
0x1144 
  [7] 0x09000000043A3194 
sqleProcessSubRequest__FP13sqle_agent_cb + 0x208 
  [8] 0x0900000003308FA0 sqleRunAgent__FPcUi + 0x8E4 
  [9] 0x090000000403CA84 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270 
================================== 
Please check the "identity" section to make sure the problematic 
latch is "SQLE_APP_GROUP_CB::appGroupLatch". 
 
In trap file you can see a call stack similar to the following: 
================================== 
sqloDumpEDU 
sqle_panic 
sqle_panic 
sqloSpinLockReleaseConflict 
sqloexcs_notrack 
  ...... 
==================================
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.1 on Linux, Unix and Windows          * 
* platform.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 might encounter "unlocking an unlatched lock" error and  * 
* the instance will be shut down.                              * 
*                                                              * 
* In db2diag.log you will see messages similar to the          * 
* following:                                                   * 
* ==================================                           * 
* 2010-01-01-01.01.01.123456+789 I123456789A12345   LEVEL:     * 
* Severe                                                       * 
* PID     : 1234567              TID  : 1           PROC :     * 
* db2agent (idle) 7                                            * 
* INSTANCE: DB2INST1             NODE : 001         DB   :     * 
* SAMPLE                                                       * 
* APPHDL  : 0-1234               APPID:                        * 
* 192.168.1.1.12345.10121223410                                * 
* AUTHID  : DB2INST1                                           * 
* 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                                   * 
* 0x07800000001c7088                                           * 
* DATA #3 : String, 108 bytes                                  * 
* {                                                            * 
* lock          = { 0x00000000 [ unlocked ] }                  * 
* identity      = SQLE_APP_GROUP_CB::appGroupLatch (81)        * 
* }                                                            * 
* DATA #4 : Hexdump, 8 bytes                                   * 
* 0x07800000001C7088 : 0000 0000 0051 0000                     * 
* .....Q..                                                     * 
* CALLSTCK:                                                    * 
* [0] 0x0900000002DE882C sqloSpinLockReleaseConflict + 0xEC    * 
* [1] 0x090000000411E390                                       * 
* @49@3@sqloexcs_notrack__FP12sqloSpinLock + 0x0               * 
* [2] 0x090000000393DC20                                       * 
* sqleSubsequentConnect__FP7sqlebwaP8sqledbcbP20sqle_agent_pri * 
* va                                                           * 
* + 0xF0                                                       * 
* [3] 0x0900000003FF6A2C                                       * 
* sqleserl__FP7sqlebwaP13sqle_agent_cbRccP8sqlo_gmt + 0x850    * 
* [4] 0x0900000004015098                                       * 
* sqlesrsu__FP7sqlebwaP13sqle_agent_cbcT3P5sqlcaPc + 0x2A4     * 
* [5] 0x0900000003FBC02C                                       * 
* sqleSecondaryStartUsing__FP13sqle_agent_cbP14sqleClientInfo  * 
* + 0x278                                                      * 
* [6] 0x0900000002E4C94C sqleInitSubAgent__FP13sqle_agent_cb   * 
* + 0x1144                                                     * 
* [7] 0x09000000043A3194                                       * 
* sqleProcessSubRequest__FP13sqle_agent_cb + 0x208             * 
* [8] 0x0900000003308FA0 sqleRunAgent__FPcUi + 0x8E4           * 
* [9] 0x090000000403CA84                                       * 
* sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x270       * 
* ==================================                           * 
* Please check the "identity" section to make sure the         * 
* problematic latch is "SQLE_APP_GROUP_CB::appGroupLatch".     * 
*                                                              * 
* In trap file you can see a call stack similar to the         * 
* following:                                                   * 
* ==================================                           * 
* sqloDumpEDU                                                  * 
* sqle_panic                                                   * 
* sqle_panic                                                   * 
* sqloSpinLockReleaseConflict                                  * 
* sqloexcs_notrack                                             * 
* ......                                                       * 
* ==================================                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.1 FixPak 11 or higher levels.   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
First fixed in DB2 UDB Version 9.1 FixPak 11.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.01.2011
19.01.2012
19.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.
Problem behoben lt. FixList in der Version
9.1.0.11 FixList