FIX: ODBC .NET Managed Provider always binds decimal data type as precision 28 (811239)



The information in this article applies to:

  • Microsoft .NET Framework 1.0
  • Microsoft ADO.NET (included with the .NET Framework) 1.0

SYMPTOMS

The Microsoft ODBC .NET managed provider always binds a decimal or numeric data type value with a precision of 28. Even if you manually set the precision of a decimal or numeric parameter to something other than 28, the ODBC .NET managed provider changes it back to 28.

Some third-party drivers (for example: Oracle RDB ODBC Driver) may not support a decimal or numeric data type value with a precision of 28. When you use these third-party drivers to pass decimal or numeric parameters, you may receive the following error message:

DIAG [HY104] [Oracle][ODBC]Invalid precision or scale value. (0)

DIAG [HY021] [Oracle][ODBC]Inconsistent descriptor information. (0)

MORE INFORMATION

With this current fix, the ODBC .NET managed provider does the following:
  1. If the user specifies a precision, the ODBC .NET managed provider takes the lesser value of the returned precision, and the URT type decimal value with a precision of 28.
  2. If the user does not specify a precision, the .NET ODBC managed provider calls SQLGetTypeInfo with SQL_DECIMAL to get the maximum precision that is supported for the data type.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 fix has the file attributes (or later) 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 tool in Control Panel.
Date        Version       Size     File name     Platform
 -----------------------------------------------------------
 18-Dec-2002  1.0.4032.0    327,680  Microsoft.data.odbc.dll     x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbNetFrame100preSP3fix kbfix kbbug kbManaged kbProvider KB811239