DB2OLEDB Provider: Access Violation When Doing INSERT into DB2 Table

When you are using the Microsoft OLE DB Provider for DB2 (DB2OLEDB) that is included with Host Integration Server 2000 to do an INSERT into a DB2 table from a SQL linked server and you are doing this by SELECTing data from a Microsoft SQL Server table by using either a four-part naming convention or OPENQUERY, an access violation (AV) occurs.

This problem can occur when the INSERT contains more than 145 columns.

SQL Server may generate a stack dump and write out information to the ERRORLOG file and a symptom dump file when the access violation occurs. The beginning of the stack dump in the ERRORLOG file may appear similar to the following: NOTE: The INSERT into the DB2 table actually completes successfully even though the access violation occurs.

If the INSERT has more than 145 columns, a pointer is being overwritten when the OLE DB Provider's SQL parser is trying to clean up its queue after the INSERT has been processed. The overwriting of the pointer results in the access violation. Because this occurs after the INSERT is processed, the DB2 table is successfully updated by the INSERT command.

To 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: The English version of this fix should have the following file attributes or later:


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 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.