DB2 - Problem description
Problem IC86849 | Status: Closed |
DEFAULT IBMDADB2 PROVIDER NOT REGISTERED WHEN INSTALLING IBM DATA SERVER DRIVER OR SWITCHING DEFAULT COPY TO THE DS DRIVER | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The following error may be displayed when running an OLE DB application with the IBM Data Server Driver package 'IBMDADB2' provider is not registered or 'IBMDADB2.1' provider is not registered This occurs because only the provider qualified by the copy name is registered (IBMDADB2.IBMDBCL1) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * IBM Data Server Driver on Windows Operating Systems * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 Fixpack 8 * **************************************************************** | |
Local Fix: | |
As a workaround, the connection string can be updated to use the provider qualified with the copy name such as: Provider=IBMDADB2.IBMDBCL1;etc.... If it is necessary to use the default provider name, it can also be created manually in the registry: Use the following location as a template: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\IBMDADB2.IBMDBCL1 Create a new section called: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\IBMDADB2 Then create all the associated values within this location so it matches exactly as what is located within HKEY_LOCAL_MACHINE\SOFTWARE\Classes\IBMDADB2.IBMDBCL1 | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v9.7 Fixpack 8 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91282 IC91284 IC91724 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.09.2012 19.04.2013 19.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |