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

DB2IUPGRADE FAILS WHEN MOVING FROM V8.2 TO V9.7FP5 AND HIGHER

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
db2ckupgrade in v97 should be able to run against a v8 , v9.1 
and v9.7 instance. 
 
The function sqloGetNormalizedEnvLang( ) is exported from 
db2locale.dll in v8. 
 
The link db2locale.dll to db2ckupgrade.exe in v97 is not the 
same as in v8.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2IUPGRADE FAILS WHEN MOVING FROM V8.2 TO V9.7FP5 AND       * 
* HIGHER                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please move to fix pack 4 of DB2 v10.1                       * 
****************************************************************
Local-Fix:
Install v97fp4 
Run db2ckupgrade from v97fp4 
If db2ckupgrade runs fine , then upgrade instance to v97fp4 
followed by upgrading database. 
Install v97fp8 
Do fix pack update to v97fp8 
Run db2updv97
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Please move to fix pack 4 of DB2 v10.1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.12.2013
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList