|
Problem IC65795
|
Status: Closed |
IBM OLE DB PROVIDER WILL NOT SHOW UP IN THE LIST OF AVAILABLE 'NATIVE OLE DB' DRIVERS IN DB2 RUN-TIME CLIENT FOR WINDOWS |
| product: |
DB2 CONNECT / DB2CONNCT / 910 - DB2 |
| Problem description: |
On Windows 32-bit/64-bit server with DB2 V9.1 Runtime Client,
IBM OLE DB Provider will not show up in the list of available
'native OLE DB' drivers
for example within Microsoft SQL Server 2005/2008 and SQL
Server Business Intelligence Development Studio |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* IBM OLE DB PROVIDER WILL NOT SHOW UP IN THE LIST OF *
* AVAILABLE 'NATIVE OLE DB' DRIVERS ON DB2 RUN-TIME CLIENT FOR *
* WINDOWS *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.1 FP 9 or higher *
* *
* OR *
* *
* Use Temporary Fix *
**************************************************************** |
| Local Fix: |
Workaround is to register OLEDB manually using regsvr32, i.e,
OLEDB provider self registration code is called when you call
regsvr32 command.
for 32bit RTCL, run
C:\WINDOWS\system32\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb2.dll
for 64bit RTCL, run
C:\windows\syswow64\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb2.dll - to register a 32-bit
dll
C:\windows\system32\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb264.dll - to register a 64-bit
dll
For example, if the product is installed in
"C:\ProgramFiles\IBM"
folder on a 32-bit Windows server, running below dll
registration command resolves the problem
C:\WINDOWS\system32\regsvr32 /s C:\Program
Files\IBM\SQLLIB\BIN\ibmdadb2.dll
For regsvr32 usage options, refer:
http://support.microsoft.com/kb/249873 |
| available fix packs: |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
First fixed in DB2 V9.1 FP 9 |
| Workaround |
Workaround is to register OLEDB manually using regsvr32, i.e,
OLEDB provider self registration code is called when you call
regsvr32 command.
for 32bit RTCL, run
C:\WINDOWS\system32\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb2.dll
for 64bit RTCL, run
C:\windows\syswow64\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb2.dll - to register a 32-bit
dll
C:\windows\system32\regsvr32 /s
<DB2InstallationPath>\bin\ibmdadb264.dll - to register a 64-bit
dll
For example, if the product is installed in
"C:\ProgramFiles\IBM"
folder on a 32-bit Windows server, running below dll
registration command resolves the problem
C:\WINDOWS\system32\regsvr32 /s C:\Program
Files\IBM\SQLLIB\BIN\ibmdadb2.dll
For regsvr32 usage options, refer:
http://support.microsoft.com/kb/249873 |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65887 IC65888
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.01.2010
22.04.2010
19.08.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
