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

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error 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)
  }
  

Local fix

• no workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 3 Fix Pack 3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IT20804

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP