|
Problem IC91282
|
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 / A10 - 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: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 Fixpack 3 *
**************************************************************** |
| 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 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 v10.1 Fixpack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.04.2013
03.10.2013
03.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
