An update is available that adds a new parameter to the connection string to enable error redirection inside an SSIS package in a Host Integration Server 2010 environment


This article describes an update that provides a new Fastload Optimize connection string parameter that is added to Microsoft Host Integration Server 2010 and to the version of Microsoft OLE DB Provider for DB2 v3 that is available in the Microsoft SQL Server R2 Feature pack data provider. The new Fastload Optimize parameter enables error redirection inside a SQL Server Integration Service (SSIS) package. This allows for rows to be redirected when errors occur when rows are inserted, updated, or deleted from DB2.

More Information

To enable the Fastload Optimize parameter in Host Integration Server 2010 and in OLE DB Provider for DB2 v3, you must set Fastload Optimize=True. The default parameter setting is Fastload Optimize=False. This parameter is used together with the AccessMode=OpenRowset Using Fastload setting in the SSIS package.

When the Fastload Optimize parameter is enabled, the following actions occurs:
  • Error redirection is enabled.
  • When you first run an SSIS package for which the Fastload Optimize=True is enabled, you may receive an error message that provides the optimal size for the FastLoadMaxInsertCommitSize option in the SSIS package. For example, depending on the actual data that is being sent, you may receive an error message that resembles the following:

    [OLE DB Destination [344]]
    Error: SSIS
    Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
    Error code: 0x80040E14. An OLE DB record is available.
    Source: "Microsoft DB2 OLE DB Provider"
    Hresult: 0x80040E14
    "The batch size of nnnn is too large for the destination table. To enable FastLoad with error recovery, set the batch commit size to nn.

    To set the FastLoadMaxInsertCommitSize option correctly in the SSIS package, set this option to the value for the "batch commit size" that is mentioned in the error message. In this error message, the nn placeholder represents this value.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 website: 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.


You must have Microsoft Host Integration Server 2010 and Microsoft OLE DB Provider for DB2 v3 installed to apply this hotfix.

Restart information

You may have to restart the computer after you apply this hotfix.

Replacement information

This hotfix replaces the following hotfix:
2437104 An update for Microsoft OLE DB Provider for DB2 v3 and for Host Integration Server 2010 is available to enable client transaction load balancing

File information

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.

For Microsoft Host Integration Server 2010, 32-bit Edition
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll8.5.4274.2640,84817-Mar-2011 12:23x86
Ddmstr.dll8.5.4274.267,40817-Mar-2011 12:23x86
Ipresync.dll8.5.4274.2526,16817-Mar-2011 12:23x86
Microsoft.hostintegration.dataaccesslibrary.dll8.5.4274.21,300,37617-Mar-2011 12:23x86
Microsoft.hostintegration.drdalink.dll8.5.4274.258,76017-Mar-2011 12:23x86
Microsoft.hostintegration.msdb2client.dll8.5.4274.2255,88817-Mar-2011 12:23x86
Microsoft.hostintegration.msdb2entityclient.dll8.5.4274.2395,16017-Mar-2011 12:23x86
Microsoft.hostintegration.msdb2entityclient.dll8.5.4274.2395,16017-Mar-2011 12:23x86
Microsoft.hostintegration.mshostfileclient.dll8.5.4274.2194,45617-Mar-2011 12:23x86
For Microsoft Host Integration Server 2010, 64-bit Edition
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll8.5.4274.2640,84817-Mar-2011 12:34x86
Db2oledb.dll8.5.4274.2897,87217-Mar-2011 12:34x64
Ddmstr.dll8.5.4274.255,63217-Mar-2011 12:34x64
Ddmstr.dll8.5.4274.267,40817-Mar-2011 12:34x86
Ipresync.dll8.5.4274.2717,65617-Mar-2011 12:34x64
Microsoft.hostintegration.dataaccesslibrary.dll8.5.4274.21,300,37617-Mar-2011 12:34x86
Microsoft.hostintegration.drdalink.dll8.5.4274.258,76017-Mar-2011 12:34x86
Microsoft.hostintegration.drdalink.dll8.5.4274.269,00017-Mar-2011 12:34x64
Microsoft.hostintegration.msdb2client.dll8.5.4274.2255,88817-Mar-2011 12:34x86
Microsoft.hostintegration.msdb2entityclient.dll8.5.4274.2395,16017-Mar-2011 12:34x86
Microsoft.hostintegration.mshostfileclient.dll8.5.4274.2194,45617-Mar-2011 12:34x86
Msdrda.dll8.5.4274.21,695,56817-Mar-2011 12:34x64
For Microsoft OLE DB Provider for DB2 v3, x86-based
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll8.0.4312.0628,56018-Mar-2011 17:07x86
Ddmstr.dll8.0.4312.067,40818-Mar-2011 17:07x86
Microsoft.hostintegration.dataaccesslibrary.dll8.0.4312.0788,37618-Mar-2011 17:07x86
For Microsoft OLE DB Provider for DB2 v3, x64-based
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll8.0.4312.0628,56018-Mar-2011 17:08x86
Db2oledb.dll8.0.4312.0880,97618-Mar-2011 17:08x64
Ddmstr.dll8.0.4312.055,63218-Mar-2011 17:08x64
Ddmstr.dll8.0.4312.067,40818-Mar-2011 17:08x86
Microsoft.hostintegration.dataaccesslibrary.dll8.0.4312.0788,37618-Mar-2011 17:08x86
Msdrda.dll8.0.4312.01,553,23218-Mar-2011 17:08x64
For Microsoft OLE DB Provider for DB2 v3, IA-64-based
File nameFile versionFile sizeDateTimePlatform
Db2oledb.dll8.0.4312.0628,56018-Mar-2011 17:09x86
Microsoft.hostintegration.dataaccesslibrary.dll8.0.4312.0788,37618-Mar-2011 17:09x86
Msdrda.dll8.0.4312.02,440,01618-Mar-2011 17:09IA-64
Msdrda.dll8.0.4312.0902,99218-Mar-2011 17:09x86
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.


For more information about how to use batch inserts when you connect to IBM DB2 for z/OS, see the "Choosing a reasonable number of rows" topic in "Chapter 10: Advanced programming techniques" in the IBM Redbook that is titled, "DB2 UDB for z/OS: Application Design for High Performance and Availability."

Note IBM does not recommend sending more than 100 rows in a batch.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

رقم الموضوع: 2503205 - آخر مراجعة: 18‏/07‏/2011 - المراجعة: 1