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 IC63593 Status: Geschlossen

DB2EVMON EXECUTABLE CAN TRAP WHILE FORMATTING AN EVENT MONITOR F ILE

Produkt:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problembeschreibung:
The executable db2evmon may trap while formatting an event monit 
or file and return the following: 
db2evmon -path . > outfile 
Reading ./00000000.evt ... 
Segmentation fault 
As a result of the segmentation fault a core file will be create 
d in the current path.
Problem-Zusammenfassung:
User Affected: All. 
Problem Description: 
The executable db2evmon may trap while formatting an event monit 
or file and return the message "Segmentation fault". 
Problem Summary. The 'Segmentation fault' message typically 
results in a core file and incomplete output. If these 
two symptoms are observed the fix for this apar should be 
installed.
Local-Fix:
db2 set event monitor db2detaildeadlockfile state=0 
and delete all the  .evt files. Then 
db2 set event monitor db2detaildeadlockfile state=1 
and see the .evt file created. Then once a deadlock occurs try f 
ormatting the .evt file.
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
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
Problem was first fixed in Version 9.1 Fix Pack 9.
Workaround
see local fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66232 IC67887 IC67890 IC67891 IC67892 IC67893 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.10.2009
14.04.2010
14.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP9
Problem behoben lt. FixList in der Version
9.1.0.9 FixList