DB2 - Problem description
Problem IC69859 | Status: Closed |
DB2 PROFILE REGISTRY KEYS IN THE 32-BIT HIVE WERE NOT REMOVED BY THE DB2 UNINSTALL | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When a 64-bit DB2 product is uninstalled from a x64 windows system, the following registry keys in the 32-bit registry hive might not be removed: HKLM\SOFTWARE\Wow6432Node\IBM\DB2\InstalledCopies\{CopyName}\GLO BAL_PROFILE HKLM\SOFTWARE\Wow6432Node\IBM\DB2\InstalledCopies\{CopyName}\PRO FILES Since these registry keys were created by the DB2 Management Service, not by the DB2 Installer, they are not removed by Windows Installer during the uninstall. This APAR will enhance the uninstaller to remove these keys during the uninstall. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 v9.7 on Windows 64-bit * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 PROFILE REGISTRY KEYS IN THE 32-BIT HIVE WERE NOT * * REMOVED BY * * THE DB2 UNINSTALL * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 Fixpack 5 * **************************************************************** | |
Local Fix: | |
These registry keys left on the system (not removed by uninstall) will not affect anything. Users can manually remove those registry keys if needed. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v9.7 Fixpack 5 | |
Workaround | |
These registry keys remained on the system (not removed by uninstall) will not affect anything. Users can manually remove those registry keys if needed. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.07.2010 02.01.2012 02.01.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |