|
Problem IT09715
|
Status: Closed |
DB2DIAG -F FAILS WITH MEMORY FAULT IF THE DIAGPATH DOES NOT EXIST. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Database was restored to a new environment. The diagpath that
was configured did not exist on the new Server.
db2diag -f gave:
$ db2diag -f
Segmentation fault(coredump)
Issue recreated on Windows via:
mkdir c:\dummy
db2 update dbm cfg using diagpath c:\dummy
rmdir c:\dummy
The db2diag -f will now fail
windows eventviewer shows:
Faulting application name: db2diag.exe, version: 9.7.800.717,
time stamp: 0x5148f112
Faulting module name: db2diag.exe, version: 9.7.800.717, time
stamp: 0x5148f112
Exception code: 0xc0000005
Note without a valid diagpath, DB2 continues to function
normally but will run as if diaglevel is set to 0. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 UDB Version 9.7 Fix Pack 11. *
**************************************************************** |
| Local Fix: |
Ensure the diagpath points to a valid path. |
| Solution |
First Fixed in DB2 UDB Version 9.7 Fix Pack 11. |
| Workaround |
Set Diagpath to a path that is defined. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.06.2015
07.10.2015
07.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
