DB2OLEDB Provider Does Not Always Determine Nullability of Data (287761)
The information in this article applies to:
- Microsoft Host Integration Server 2000
- Microsoft SNA Server 4.0 SP4
This article was previously published under Q287761 SYMPTOMS
The DB2OLEDB provider is not always able to reliably determine the nullability of data. As a result of this, in some OpenQuery cases, the DB2OLEDB provider will sometimes return DBCOLUMNFLAGS_ISNULLABLE=0 (in other words, nonnullable) when the query is prepared, but the actual data indicates ISNULLABLE=1.
RESOLUTIONSNA Server 4.0
No fix is available for SNA Server 4.0 at this time.
Host Integration Server 2000To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
328152 How to Obtain the Latest Host Integration Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
|
| MSeidrda.dll | 01/25/01 | 12:00 | | MSeidb2d.dll | 01/25/01 | 12:00 |
NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
NOTE: This fix also requires that an update for SQL Server 2000 or SQL Server 7.0 to be applied. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
293758 FIX: Nullability Changes Not Handled by SQL Server with Linked Server Queries to DB2
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
| Modification Type: | Minor | Last Reviewed: | 3/11/2005 |
|---|
| Keywords: | kbbug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB287761 |
|---|
|