home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63593 Status: Closed

DB2EVMON EXECUTABLE CAN TRAP WHILE FORMATTING AN EVENT MONITOR F ILE

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
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 Summary:
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.
available fix packs:
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

Solution
Problem was first fixed in Version 9.1 Fix Pack 9.
Workaround
see local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66232 IC67887 IC67890 IC67891 IC67892 IC67893 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.10.2009
14.04.2010
14.04.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList