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

DB2DIAG -F FAILS WITH MEMORY FAULT IF THE DIAGPATH DOES NOT EXIST.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
First Fixed in DB2 UDB Version 9.7 Fix Pack 11.
Workaround
Set Diagpath to a path that is defined.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.06.2015
07.10.2015
07.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP11
Problem behoben lt. FixList in der Version
9.7.0.11 FixList