DB2 - Problembeschreibung
Problem IC73359 | Status: Geschlossen |
DB2GOV START WITH FULL PATH OF LOG FILE ON DPF SYSTEM DOES NOT LOG ERROR IN LOG FILES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The 'db2gov start' command should not specify the full path of the log file. Error "GOV1014N Unable to open log file." is returned if the full path to the log file is used. However, in a DPF environment, the error is not returned. Example: db2gov start sample /db2home/db2inst1/governor/db2gov.cfg /db2home/db2inst1/sqllib/log/db2gov.log The output: ===================== db2gov deamons have been started on all nodes. Please check the corresponding log files for status! Note: The log files are stored in the /tmp/db2inst1 directory. File names are db2gov_start.nodenumber. The /tmp/db2inst1/db2gov_start looks like: ======================================= hostname01: db2gov start SAMPLE... completed ok Error that should have been logged: db2govd: GOV1014N Unable to open log file "/db2home/db2inst1/sqllib/log/sample_gov.log". RC = "" | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 Governor users on DPF environment * **************************************************************** * PROBLEM DESCRIPTION: * * On DPF system, GOV1014N error is missing when db2gov start * * command specifies the full path log file. * * And it states that governor is started successfully when it * * is not. * **************************************************************** * RECOMMENDATION: * * Upgrade to version v9.7 FP5 * **************************************************************** | |
Local-Fix: | |
Use log file name, no need to supply full path. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in Version 9.7 Fix Pak 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.12.2010 11.01.2012 11.01.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7., 9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |