DB2 - Problembeschreibung
Problem IC66596 | Status: Geschlossen |
CONCURRENT CREATE EVENT MONITOR STATEMENTS DEADLOCK | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Concurrently executing CREATE EVENT MONITOR statements may deadlock. Deadlock event monitor output shows that both statements are holding row locks in SYSIBM.SYSTABLES that the other application is requesting. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 Version 9.5 GA through to Fix Pack 5 servers on * * Linux, Unix and Windows platforms executing concurrent * * create event monitor statements. * **************************************************************** * PROBLEM DESCRIPTION: * * Create event monitor statements which are defined to make * * use of tables (either explicitly specified in the create * * statement, or implicitly defined based on the event monitor * * name), need to create these tables as part of the statement. * * Incorrect isolation levels while scanning SYSIBM.SYSTABLES * * to carry out the necessary logic lead to the possibility of * * deadlocks. * **************************************************************** * RECOMMENDATION: * * Avoid creating event monitors concurrently, or apply DB2 * * Version 9.5 Fix Pack 6. * **************************************************************** | |
Local-Fix: | |
Ensure that applications are not creating event monitors concurrently. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 Version 9.5 Fix Pack 6 and all subsequent Fix Packs. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC66624 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.02.2010 23.04.2010 23.04.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |