DB2 - Problem description
Problem IC76021 | Status: Closed |
SOME 32-BIT DB2 REGISTRY KEYS ARE NOT SET DURING THE SILENT INSTALL OF 64-BIT IBM DATA SERVER DRIVER PACKAGE (DSDRIVER) | |
product: | |
DB2 CONNECT / DB2CONNCT / 950 - DB2 | |
Problem description: | |
When the 64-bit IBM Data Server Driver Package (DsDriver) is installed via a response file based silent install, the following 32-bit DB2 registry keys are not set in the 32-bit registry hive (1) DB2 Path Name, under: HKLM\SOFTWARE\Wow6432Node\IBM\DB2\InstalledCopies\<CopyName>\ Some 32-bit DB2 applications need this registry to work with the 32-bit DB2 libraries installed with the 64-bit DB2 product. (2) The OLEDB GUIDs, under: HKLM\SOFTWARE\Wow6432Node\IBM\DB2\InstalledCopies\<CopyName>\Ins tallData\ These OLEDB GUIDs are needed in order to register the DB2 OLE DB providers. Thus, because those 32-bit DB2 registry keys are not set during the silent 64-bit DsDriver install, some 32-bit DB2 applications will not be able to work with the 64-bit DsDriver installed, and the OLE DB provider will not be registered. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * WINDOWS * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * UPGRADE TO DB2 V9.5 FP 9 OR HIGHER * * * * OR * * * * USE TEMPORARY FIX * **************************************************************** | |
Local Fix: | |
Install the 64-bit DsDriver via a GUI install, instead of the response file based silent install. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
FIRST FIXED IN DB2 V9.5 FP 9 | |
Workaround | |
Install the 64-bit DsDriver via a GUI install, instead of the response file based silent install. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.04.2011 08.03.2012 08.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 |