home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66780 Status: Geschlossen

A CRASH IN A THREADED FMP PROCESS WHILST WRITING TO THE DB2DIAG.LOG CAN
BLOCK ACCESS TO THE DB2DIAG.LOG.

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
If a thread in a threaded FMP process crashes in a function 
writing to the db2diag.log, access to the db2diag.log will 
be blocked. The scope for such a crash is limited. 
 
The file lock held whilst writing will prevent other 
processes from access the db2diag.log until the FMP process 
terminates. Internal latching within the process to 
protect access to the db2diag.log will prevent the FMP 
from terminating.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 UDB LUW V9.1 FP10.                             * 
****************************************************************
Local-Fix:
Kill the offending FMP process or issue "db2diag -A" to 
create a new db2diag.log file.
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Lösung
Update to DB2 UDB LUW V9.1 FP10.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66782 IC66793 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.03.2010
14.06.2011
14.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP10
Problem behoben lt. FixList in der Version
9.1.0.10 FixList