DB2 - Problembeschreibung
Problem IC95991 | Status: Geschlossen |
A LOCK ON THE NOTIFY LOG OR DB2DIAG.LOG CAN MAKE THE ENGINE SO SLOW THAT IT WOULD LOOK LIKE A HANG | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
A lock by another application or anything else on the notify log or db2diag.log file can potentially make the engine work very slow if there are lot of messages being asked to be written to the log files due to some condition in the engine ( such as lock escalation ). The engine can become so slow that it would look like a "hang". The situation is exasperated on a DPF system where all the nodes are writing to the same db2diag.log or notify.log file. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Either apply the suggested workaround or upgrade to DB2 v9.7 * * Fixpack 9. * **************************************************************** | |
Local-Fix: | |
Viable workarounds include: 1) Find out who or what is locking the file(s) and kill that process OR 2) db2diag -A ( to change the log file ) -- ( but this will help only if the lock is on db2diag.log file ) OR 3) For DPF systems, have the logs split on Node numbers using the new functionality of DIAGPATH ( refer Infocenter ) OR 4) For DPF systems, have one local DIAGPATH for each physical servers OR | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 v9.7 Fixpack 9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96246 IC96247 IC96366 IC96689 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.09.2013 26.09.2013 26.09.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.0., 9.7., 9.7.FP9 | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 |