DB2 - Problembeschreibung
Problem IC87831 | Status: Geschlossen |
RACE CONDITION PREVENTS EVENT MONITOR FAST WRITERS AND OTHER BACKGROUND AGENTS FROM STARTING | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
There is a race condition during database activation. A combination of user connections and transaction manager (TM) database connections may result in event monitor fast writer not starting. An activate of any event monitor will get error, e.g. SET EVENT MONITOR DB2ACTIVITIES STATE 1 Subsequent SQL statements can be processed. (Reason "Unable to activate event monitor because no fast writers are started".). SQLCODE=-901, SQLSTATE=58004, DRIVER=4.8.86 In db2diag.log, you may see 2012-02-24-14.42.54.222955-480 E1126722A526 LEVEL: Warning PID : 4784134 TID : 13109 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB : SAMPLE APPHDL : 0-71 APPID: 172.22.53.47.4599.120224224251 AUTHID : DB2INST EDUID : 13109 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database monitor, sqm_evmon_mgr::restartEvmons, probe:16 DATA #1 : <preformatted> Unable to activate event monitor DB2ACTIVITIES because no fast writers are started | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
force off all application deactivate database activate database | |
Lösung | |
First fixed in Version 10.1 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.11.2012 10.12.2012 10.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |