home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC76600 Status: Geschlossen

WRONG LOG FILENAME DISPLAYED BY DB2IUPGRADE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When you upgrade an instance db2iupgrade and db2imchk might 
display a wrong filename: "DBI1266I  Refer to the log file 
/home/db2inst1/migration.log for more information." 
 
The correct filename is upgrade.log and can be found in the 
instance owner's home directory. 
 
Starting with DB2 v9.7 Fix Pack 5 the name of the log file will 
be changed to db2ckupgrade.log 
The DBI1266I message will reflect this change as in the 
following example: 
"DBI1266I  Refer to the log file /home/db2inst1/db2ckupgrade.log 
for more information."
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When you upgrade an instance db2iupgrade and db2imchk might  * 
*                                                              * 
* display a wrong filename: "DBI1266I  Refer to the log file   * 
*                                                              * 
* /home/db2inst1/migration.log for more information."          * 
*                                                              * 
*                                                              * 
*                                                              * 
* The correct filename is upgrade.log and can be found in the  * 
*                                                              * 
* instance owner's home directory.                             * 
*                                                              * 
*                                                              * 
*                                                              * 
* Starting with DB2 v9.7 Fix Pack 5 the name of the log file   * 
* will                                                         * 
* be changed to db2ckupgrade.log                               * 
*                                                              * 
* The DBI1266I message will reflect this change as in the      * 
*                                                              * 
* following example:                                           * 
*                                                              * 
* "DBI1266I  Refer to the log file                             * 
* /home/db2inst1/db2ckupgrade.log                              * 
* for more information."                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 Fix Pack 5                               * 
****************************************************************
Local-Fix:
In versions previous to v9.7 Fix Pack 5 the log file is called 
upgrade.log, please inspect this file for any errors or issues 
related to upgrades.
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 v9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.05.2011
19.01.2012
19.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList