|
Problem IC66232
|
Status: Closed |
DB2EVMON EXECUTABLE CAN TRAP WHILE FORMATTING AN EVENT MONITOR F ILE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* The executable db2evmon may trap while formatting an *
* eventmonitor file and return the message "Segmentation *
* fault".The 'Segmentation fault' message typically results in *
* a corefile and incomplete output. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 2. *
**************************************************************** |
| 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.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.7 Fix Pack 2. |
| Workaround |
db2 set event monitor db2detaildeadlockfile state=0
and delete all the .evt files. Then
db2 set event monitor db2detaildeadlockfile state=1
and see the new .evt file created. Then once a deadlock occurs
try formatting the .evt file. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.02.2010
02.07.2010
02.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
