|
Problem IC75641
|
Status: Closed |
DB2 LEVEL AND INSTALL PATH IN GLOBAL REGISTRY ARE NOT UPDATED AFTER APPLYING SPECIAL BUILD |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
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 |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.04.2011
11.03.2012
11.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
