DB2 - Problem description
Problem IT21923 | Status: Closed |
POSSIBLE TRAP IN RELEASECONFLICT() BECAUSE PAUDITSETTINGS->AUDITSETTINGSLATCH IS ALREADY UNLOCKED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
A trap similar to this might happen with the Audit Setting latch: [1] 0x090000000F2FBF0C releaseConflict + 0x60 [2] 0x09000000110E5CA0 releaseConflict + 0x464 [3] 0x090000000FF3099C sqlrr_pn_init + 0x2068 [4] 0x090000000FF2ECF0 sqlrr_pn_init + 0x3BC [5] 0x0900000010921DDC sqlrr_appl_init + 0x3160 [6] 0x090000001092FC94 sqlrr_appl_init + 0x4BB0 [7] 0x090000001091B334 InitEngineComponents + 0x2BEC [8] 0x0900000010910900 AppStartUsing + 0x81C [9] 0x0900000012B0CC50 AppLocalStart + 0x530 The db2diag.log would have the latch entry dumped and it would look like this: DATA #7 : String, 414 bytes { state = 0x0000000000000000 = { held X: 0 reserved for X: 0 shared holders: 0 firstSharIndex: 0x0 firstExclIndex: 0x0 } starve X mode = true xWaitCount = 0 requestCount = 0 identity = SQLRAUDITSETTINGS::auditSettingsLatch (745) } | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher * **************************************************************** | |
Local Fix: | |
no workaround | |
available fix packs: | |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.08.2017 19.03.2018 19.03.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |