ODBC for DB2 Driver Fails with Not Valid Datatype Error

When you try to submit special select statements against a DB2 Table by using the Microsoft Open Database Connectivity (ODBC) for DB2 driver that is delivered with Microsoft Host Integration Server 2000, you may get an error message that indicates not valid datatype values.

Under certain conditions, the ODBC Driver for DB2 driver does not process a NULL row marker byte. This causes the whole buffer to be off by one byte. Therefore, all later rows contain corrupted values.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. 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.

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.

Microsoft has confirmed that this is a problem in Host Integration Server 2000.

When a SELECT statement is issued, the host returns an SQL Communication Area Reply Data (SQLCARD). In this case, the returned SQLSTATE is "00000" in the second row of data. This indicates any special condition, such as an empty column, that is a result of an OUTER JOIN statement. Because the SQLSTATE is all zeros, the ODBC Driver for DB2 skips the SQLCARD and moves on to parse the next byte in the data buffer. This is a QRYDTA NULL row marker because this column is empty. The NULL row marker is skipped in error, therefore causing the whole data buffer to be off by one byte.