Hi All We are migrating a few DataStage jobs to SSIS 2008 and below is an issue that is bothering me. I am trying to use the FastLoad option of the Microsft OLE DB Provider for DB2 v3.0 but have been unsuccessful. I am trying to run a simple package that loads the data from one DB2 table to another without any transformation. The reason I am exploring the fast load is because the normal option of OpenRowset does not perform as well the DataStage job to load the same amount of data, its almost 10 times slower. DB2 version 9.5 Fixpack 5 SSIS 2008 Error msg [OLE DB Destination [79]] 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 Description: "An internal network library error has occurred. A network level syntax error has occurred. SQLSTATE: HY000, SQLCODE: -379". [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (79) failed with error code 0xC0202009 while processing input "OLE DB Destination Input" (92). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. Please do help me your experience with any similar issue. Thanks in advance. Thanks Saurav

Hello Saurav, the symptoms make me beleve you might have an issue with the MS OleDb provider, try either upgrading it or using the one from IBM, let us know if that helps.Arthur My Blog

Thanks for your response Arthur.. I am actually using the latest version of the MS OLEDB provider for DB2.. i.e. version 3.0 that is come packaged with 2008 R2. Have you any thoughts on the performance issues related to writing into DB2 using SSIS ? And also, how do I get the FastLoad option on this latest MS OLEDB driver to work. Would be excellent if I could get some useful inputs on these 2 concerns. Cheers Saurav

Why do you use MS OLEDB provider? Have you tried using the DB2 OLEDB provider?SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

Saurav, Please contact Host Integration Server Support. We have had several updates to the provider since it was released, and (from memory) this issue has been addressed in one of our later fixes. Thanks, CharlesCharles Ezzell - MSFT

There's a Microsoft hotfix available to address this issue. We had the same issue. It took 1:16 min to insert 1K rows into DB2. With the hot fix and fastload option, it takes only 2 sec. 500K rows takes only 56 sec. http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2428175&kbln=en-us