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 IT20804 Status: Closed

POSSIBLE TRAP IN RELEASECONFLICT() BECAUSE
PAUDITSETTINGS->AUDITSETTINGSLATCH IS ALREADY UNLOCKED

product:
DB2 FOR LUW / DB2FORLUW / A50 - 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:                                              * 
* db2 crash                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to 10.5fp9                                           * 
****************************************************************
Local Fix:
no workaround
Solution
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) 
}
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.05.2017
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)