DB2 - Problembeschreibung
Problem IT25396 | Status: Geschlossen |
PURESCALE HADR STANDBY MIGHT CRASH WITH SQLO_XLATCH::RELEASECONFLICT: "UNLOCKING AN UNLATCHED LOCK" | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
Under rare timing conditions HADR standby might crash the instance during the deactivation of the database. Db2diag.log will contain a message similar to this one: EDUID : 216724 EDUNAME: db2shred.3 (SAMPLE) 1 FUNCTION: DB2 UDB, SQO Latch Tracing, sqlo_xlatch::releaseConflict, probe:10 DATA #1 : String, 27 bytes unlocking an unlatched lock DATA #3 : String, 101 bytes { lock = { 0x00000000 [ unlocked ] } identity = sqeScoordCB::sCoordLatch (135) } Stack (included in the db2diag.log) and the trap file will indicate that error is originating from the following stack: sqle_panic sqloSpinLockReleaseConflict sqleSubCoordTerm sqeAgent::RunEDU() | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * PureScale * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version Db2 version 11.1 Mod 3 Fix Pack 3 or * * higher. * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : IT25391 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.06.2018 17.06.2018 17.06.2018 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |