DB2 - Problem description
Problem IC63288 | Status: Closed |
"'IBMDADB2.1' PROVIDER IS NOT REGISTERED ON THE LOCAL MACHINE" MESSAGE MISLEADS THE PROBLEM FOR .NET AND OLEDB APPLICATIONS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
After an upgrade from V8 FP11 client to V9.1 FP5 client, .NET and OLEDB applications generate error "'IBMDADB2.1' provider is not registered on the local machine". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 V9.1 Fix Pack 5 * **************************************************************** * PROBLEM DESCRIPTION: * * "'IBMDADB2.1' PROVIDER IS NOT REGISTERED ON THE * * LOCALMACHINE"MESSAGE MISLEADS THE PROBLEM FOR .NET AND * * OLEDB APPLICATIONS. * * This is due to the limitation of "GetLongPathName". * **************************************************************** * RECOMMENDATION: * * Modify the directory permission level with read access for * * everyone to %SystemRoot% for .NET applications, and sqllib * * directory for OLEDB applications. * **************************************************************** | |
Local Fix: | |
It requires everyone read access to the %SystemRoot% directory for .NET applications, and to the sqllib directory for OLEDB applications. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Solution | |
The issue was first handled in V9.1 Fix Pack 9 or above. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66019 IC66024 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.09.2009 27.04.2010 23.07.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 |