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

JOURNAL DOES NOT USE DIAGPATH WHEN VIEWING THE NOTIFY LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The tab where you can view the notification log in Journal is 
always looking under $INSTHOME/sqllib/dump/*.nfy to populate the 
view. 
 
Whenever DIAGPATH is not set it should pick from default path 
i.e $INSTHOME/sqllib/db2dump/*.nfy else it should pick from the 
path configured in DIAGPATH
Problem-Zusammenfassung:
JOURNAL DOES NOT USE DIAGPATH WHEN VIEWING THE NOTIFY LOG
Local-Fix:
To view the log in Journal, use the default DIAGPATH of 
$INSTHOME/sqllib/db2dump
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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

Lösung
First fixed in DB2 LUW v9.7 Fixpak 1
Workaround
To view the log in Journal, use the default DIAGPATH of 
$INSTHOME/sqllib/db2dump
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.06.2009
29.12.2009
29.12.2009
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.1 FixList