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

DB2 LEVEL AND INSTALL PATH IN GLOBAL REGISTRY ARE NOT UPDATED AFTER
APPLYING SPECIAL BUILD

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
When upgrading to newer DB2 versions (eg. from DB2 9.5 FP3 to 
9.5 FP5) in a DPF environment, the global registry instance 
records on all nodes will be updated to reflect the new DB2 
level and install path. However this does not happen in the 
case of special builds (eg. from DB2 9.5 FP5 to 9.5 FP5 special 
build) as the base DB2 version remains the same (ie. DB2 9.5 
FP5). Only the instance records on the node on which db2iupdt 
was run will be updated. The profile.reg in old special build 
install paths may also not be cleaned up.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When upgrading to newer DB2 versions (eg. from DB2 9.5 FP3   * 
* to                                                           * 
* 9.5 FP5) in a DPF environment, the global registry instance  * 
*                                                              * 
* records on all nodes will be updated to reflect the new DB2  * 
*                                                              * 
* level and install path. However this does not happen in the  * 
*                                                              * 
* case of special builds (eg. from DB2 9.5 FP5 to 9.5 FP5      * 
* special                                                      * 
* build) as the base DB2 version remains the same (ie. DB2 9.5 * 
*                                                              * 
* FP5). Only the instance records on the node on which         * 
* db2iupdt                                                     * 
* was run will be updated. The profile.reg in old special      * 
* build                                                        * 
* install paths may also not be cleaned up.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.5 FP9 or later.                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 9.5 FP9. 
 
When DB2 is started after applying a fixpack, the various 
records in the global registry will be updated to reflect the 
new installation path. The profiles registry is also cleaned up 
and the outdated records are removed. However the same operation 
is not performed after updating special builds as the fixpack 
level remains the same. This fix will allow the logic to apply 
to special builds as well.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.04.2011
11.03.2012
11.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList