|
Problem IC72727
|
Status: Closed |
"Provider cannot be found" on OLEDB provider IBMDADB2 after v9.7 DB2 is upgraded to a higher fixpack on 64-bit Windows |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The values for the V97 DB2 OLEDB registry keys are lost after it
is upgraded to a higher fix pack level on a 64-bit Windows
system.
The OLE DB application receives the error messages similar as
the following:
Error: Provider cannot be found. It may not be properly
installed.
Code: 800A0E7A
Source: ADODB.Connection
Since the OLEDB registry keys do not have their GUID values, you
will get the following error when you tried to register it
manually with the regsvr32.exe command line.
The module "<full path of the .dll file>" failed to load.
Make sure the binary is stored at the specified path or debug it
to check for problems with the binary or dependent .DLL files.
A dynamic link library (DLL) initialization routine failed.
For reference, the following is the command line to
register the DB2's OLE DB provider manually:
To register the 32-bit driver in the 32-bit registry:
C:\Windows\SysWOW64\regsvr32.exe <DB2 copy installation
directory>\bin\ibmdadb2.dll
To register the 64-bit driver in the 64-bit registry:
C:\Windows\System32\regsvr32.exe <DB2 copy installation
directory>\bin\ibmdadb264.dll |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 64-bit Windows are affected. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The values for the V97 DB2 OLEDB registry keys are lost *
* after a fix pack is applied on a 64-bit Windows system. *
* *
* The OLE DB application receives the error messages similar *
* as the following: *
* *
* Error: Provider cannot be found. It may not be properly *
* installed. *
* Code: 800A0E7A *
* Source: ADODB.Connection *
* *
* Since the OLEDB registry keys do not have their GUID values, *
* you will get the following error when you tried to register *
* it manually with the regsvr32.exe command line. *
* *
* The module "<full path of the .dll file>" failed to load. *
* Make sure the binary is stored at the specified path or *
* debug it to check for problems with the binary or dependent *
* .DLL files. *
* A dynamic link library (DLL) initialization routine failed. *
* *
* For your reference, the following is the command line to *
* register the DB2's OLE DB provider manually: *
* *
* To register the 32-bit driver in the 32-bit registry: *
* C:\Windows\SysWOW64\regsvr32.exe <DB2 copy installation *
* directory>\bin\ibmdadb2.dll *
* *
* To register the 64-bit driver in the 64-bit registry: *
* C:\Windows\System32\regsvr32.exe <DB2 copy installation *
* directory>\bin\ibmdadb264.dll *
****************************************************************
* RECOMMENDATION: *
* Download and install the V97 FP4 DB2 Fix Pack image which *
* contains the fix for this problem, and install it on top of *
* the existing DB2 copy. *
**************************************************************** |
| Local Fix: |
Install the V97 DB2 product at the higher fix pack to a new DB2
copy, instead of installing it on top of the lower Fix Pack.
Then, move the DB2 instances in the existing copy to the new
copy by executing the
db2iupdt.exe command line. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 4. |
| Workaround |
Install the V97 DB2 product at the higher fix pack to a new DB2
copy, instead of installing it on top of the lower Fix Pack.
Then, move the DB2 instances in the existing copy to the new
copy by executing the db2iupdt.exe command line. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72826
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.11.2010
28.04.2011
28.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
