FIX: The data conversion fails when you try to import binary character data in the OLE DB Provider for DB2 1.0

Consider the following scenario. You try to import binary character data in the Microsoft OLE DB Provider for DB2 1.0 by using a provider string. The provider string has a foreign character code set identifier (CCSID) or code page. In this scenario, the data conversion fails.

This problem occurs because the provider string does not match the CCSID of the data column.

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next OLE DB Provider for DB2 1.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

OLE DB Provider for DB2 1.0, 32-bit editions

OLE DB Provider for DB2 1.0, 64-bit editions

OLE DB Provider for DB2 1.0, Itanium-based editions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: