suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT18614 Status: Closed

DB2 TRAPS ON SQLELOOKUPAUDITSETTINGS WITH
SQLO_SLATCH_ERROR_HELDX_WITH_SHARED_HOLDERS ON DPF

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 can crash with the following on a DPF system: 
 
FUNCTION: DB2 UDB, SQO Latch Tracing, 
SQLO_SLATCH_CAS64::getConflictComplex, probe:210 
MESSAGE : 
ZRC=0x870F00FB=-2029059845=SQLO_SLATCH_ERROR_HELDX_WITH_SHARED_H 
OLDERS 
          "shared latch found with both exclusive and shared 
holders.  Latch likely corrupt." 
CALLED  : OS, -, unspecified_system_function 
OSERR   : 3473536 "Error 3473536 occurred." 
DATA #1 : String, 13 bytes 
invalid latch 
DATA #2 : File name, 16 bytes 
sqloLatchCAS64.C 
DATA #3 : Source file line number, 8 bytes 
515 
DATA #4 : Codepath, 8 bytes 
0 
DATA #5 : String, 139 bytes 
0xFFFFFFFFFFFFFFFF: { 
   held X: 1 
   reserved for X: 1 
   shared holders: 65535 
   firstSharIndex: 0x1FFFFF 
   firstExclIndex: 0x1FFFFF 
} 
DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes 
0x1 (SQLO_LATCH_MODE_SHARED) 
DATA #7 : String, 428 bytes 
{ 
   state         = 0xFFFFFFFFFFFFFFFF 
                 = { 
                       held X: 1 
                       reserved for X: 1 
                       shared holders: 65535 
                       firstSharIndex: 0x1FFFFF 
                       firstExclIndex: 0x1FFFFF 
                   } 
   starve X mode = true 
   xWaitCount    = 0 
   requestCount  = 0 
   identity      = SQLRAUDITSETTINGS::auditSettingsLatch (770) 
} 
DATA #8 : Hexdump, 16 bytes 
0x0A000600E839FD20 : FFFF FFFF FFFF FFFF 0302 0000 0000 0000 
................ 
 
Likely you will see two agents trap 
 
agent stack : 
 
0x0900000000510F14 pthread_kill + 0xD4 
0x090000001C39A20C sqloDumpEDU + 0x54 
0x090000001C0B74BC sqle_panic__Fv + 0x160 
0x090000001E36E820 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7 + 0x2CC 
0x090000001E36E470 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7@glue339 + 0xA0 
0x090000001BC73420 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 
0x40 
0x090000001CC3206C getConflict__17SQLO_SLATCH_CAS64FCUl + 0xC8 
0x090000001CC32144 getConflict__17SQLO_SLATCH_CAS64FCUl@glueFD + 
0x74 
0x090000001BD10588 
sqleLookupAuditSettings__FPCcCP18sqlexAuditSettings + 0x2C8 
0x090000001CDB9468 
sqlexGetConnectAuditSettings__FP14db2UCinterfaceP18sqlexAuditSet 
tings + 0x30 
0x090000001CDBA574 sqlexEngAuthenticate__FP14db2UCinterface + 
0xE0 
0x090000001CDBB744 
AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x29C 
0x090000001CB4014C sqlelostWrp__FP14db2UCinterface + 0x38 
0x090000001CB40200 sqleUCengnInit__FP14db2UCinterfaceUs + 0x64 
0x090000001CDC2194 sqleUCagentConnect + 0x2B4 
0x090000001CDC3064 
sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x104 
 
Waiting on latch type: 
(SQLO_LT_SQLRAUDITSETTINGS__auditSettingsLatch) - Address: 
(a000600e839fd20), Line: 2842, File: sqle_database.C 
Holding Latch type: 
(SQLO_LT_sqlr_db__exclusiveDDLMemoryListLatch) - Address: 
(a000600e80af9b8), Line: 2833, File: sqle_database.C HoldCount: 
1 
 
subagent : 
 
0x0900000000510F14 pthread_kill + 0xD4 
0x090000001C39A20C sqloDumpEDU + 0x54 
0x090000001C0B74BC sqle_panic__Fv + 0x160 
0x090000001E36E820 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7 + 0x2CC 
0x090000001E36E470 
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T 
3T7@glue339 + 0xA0 
0x090000001BC73420 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 
0x40 
0x090000001CC3206C getConflict__17SQLO_SLATCH_CAS64FCUl + 0xC8 
0x090000001CD38224 
getConflict__17SQLO_SLATCH_CAS64FCUl@glueFD@clone1 + 0x74 
0x090000001D78269C sqlrr_appl_init__FP8sqeAgentP5sqlca + 0xE78 
0x090000001D77FC98 
InitEngineComponents__14sqeApplicationFcP8sqeAgentP8SQLE_BWAP5sq 
lcaP22SQLESRSU_STATUS_VECTORT1 + 0x9B8 
0x090000001CAC1C3C 
AppStartUsing__14sqeApplicationFP8SQLE_BWAP8sqeAgentcT3P5sqlcaPc 
+ 0x62C 
0x090000001C2D761C 
sqleSubAgentStartUsing__FP8sqeAgentP16SQLE_CLIENT_INFO + 0x3E8 
0x090000001BE0AB90 
AppSecondaryStartUsing__14sqeApplicationFP8sqeAgentP16SQLE_CLIEN 
T_INFOP5sqlca + 0x590 
0x090000001BF4BD0C initSubAgent__8sqeAgentFv + 0x678 
0x090000001EAA891C sqleProcessSubRequest__FP8sqeAgent + 0x454 
0x090000001DC156FC RunEDU__8sqeAgentFv + 0xF0 
0x090000001CAA39F8 EDUDriver__9sqzEDUObjFv + 0x100 
0x090000001CAA38B4 sqlzRunEDU__FPcUi + 0x24 
0x090000001CAB0E4C sqloEDUEntry + 0x264 
 
Waiting on latch type: 
(SQLO_LT_SQLRAUDITSETTINGS__auditSettingsLatch) - Address: 
(a000600e839fd20), Line: 2234, File: sqlrr.C 
 
 
The signature of this APAR is the latch in 
SQLO_LT_SQLRAUDITSETTINGS__auditSettingsLatch)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Activate database explicitly
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.12.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)