|
Problem IC64466
|
Status: Closed |
INSTALL OF DB2 MERGE MODULES FAILS BECAUSE OF A REGISTRY KEY ISSUE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The install of DB2 merge modules failed at creating the registry
key:
HKLM\SOFTWARE\IBM\DB2\InstalledCopies\[CopyName]\\COMPONENTS.
Although the registry key defined in the DB2 merge module is:
HKLM\SOFTWARE\IBM\DB2\InstalledCopies\[CopyName]\[ProductNameNoI
nstallName]\COMPONENTS,
since the property of "ProductNameNoInstallName" is not set
during the db2 merge module install, it becomes ~\\COMPONENTS. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* INSTALL OF DB2 MERGE MODULES FAILS BECAUSE OF A REGISTRY KEY *
* ISSUE. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The install of DB2 merge modules failed at creating the *
* registrykey: *
* *
* HKLM\SOFTWARE\IBM\DB2\InstalledCopies\[CopyName]\\COMPONENTS.
* *
* Although the registry key defined in the DB2 merge module *
* is: *
* HKLM\SOFTWARE\IBM\DB2\InstalledCopies\[CopyName]\[ProductNameN
* InstallName]\COMPONENTS, *
* since the property of "ProductNameNoInstallName" is not set *
* during the db2 merge module install, it becomes *
* ~\\COMPONENTS. *
****************************************************************
* RECOMMENDATION: *
* Please move to fix pack 2 for v9.7 *
**************************************************************** |
| Local Fix: |
The work-around for this problem is:
After embedding DB2 merge module into your software project,
modify the install image by adding the following entry into the
image .MSI's Property file:
Property: ProductNameNoInstallName
Value : IBM Data Server Runtime Client |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 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 9a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Please move to fix pack 2 for v9.7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2009
31.08.2010
31.08.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
