DB2 - Problem description
Problem IC61770 | Status: Closed |
THE CONFIGURATION ASSISTANT FOR BOTH V8 AND V9 (WHEN BOTH ARE INSTALLED) USES THE SAME REGISTRY KEY TO LOCATE IBMDADB2.DLL | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When both DB2 v8 and DB2 v9 are installed, the v9 Configuration Assistant uses the v8 Registry Key for ibmdadb2.dll. This means that both the OLE DB and the ADO Connection Tests fail. The v9 Configuration Assistant reads HKEY_CLASSES_ROOT\IBMDADB2\CLSID which is the v8 key. It should be reading HKEY_CLASSES_ROOT\IBMDADB2.DB2COPY1 instead. (DB2COPY1 being the v9 installation) Please note that this problem does not affect OLEDB applications, and this is specific to Windows | |
Problem Summary: | |
Users Affected: All users of the Configuration Assistant on Windows with both DB2 v8 and DB2 v9.7 installed. Problem Description: Testing OLE DB and ADO connectivity from the DB2 v9.7 Configuration Assistant will fail. ADO and OLE DB applications will work, however. Recommendation: Do not use the Configuration Assistant to test ADO and OLE DB connectivity. | |
Local Fix: | |
Local Fix: None Work Around: None | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in FP1, defect wsdbu00551700 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.06.2009 22.12.2009 22.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |