PROBLEM FACING DURING FETCHING DATA FROM DB2 to SQL USING OLE DB FOR DB2 PROVIDER

• ashishkm88

  SSC Enthusiast

  Points: 115

  More actions

  May 28, 2012 at 11:34 pm

  #274708

  Hi ,

  I have created a SSIS package which have a Data Flow Control, which simply replicate a flat table from DB2 to SQL server database. I used Microsoft OLE Provider for DB2 as source connection. During off- hours replication has done sucessfully but during the transaction hours (Day-Time) following error is occurs in source .

  [OLE DB Source [1]] 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: "A TCPIP socket error has occured (10055): An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. ".

  Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009.

  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component,but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

  Error: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.

  Error: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled.

  Error: SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited.

  Could any one help me on this regards!

  Thanks

  Ashish Kumar MIshra

• EdVassie

  SSC Guru

  Points: 60516

  More actions

  May 30, 2012 at 3:04 am

  #1494507

  All I can suggest is ask someone who knows about network troubleshooting.

  If no-one else has better advice and you cannot fix the problem, raise a case with Microsoft. They will either resolve the problem or identify it is happening on the IBM side.

  Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
  

  When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

• Jack Corbett

  SSC Guru

  Points: 184394

  More actions

  May 30, 2012 at 1:25 pm

  #1494856

  Have you seen this blog post, http://blogs.msdn.com/b/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx?

  It's been years since I've connected to DB2, but I seem to recall seeing an error like this for a linked server or .NET application and I think it had something to do with permissions on the DB2 side.

  Jack Corbett
  Consultant - Straight Path Solutions
  Check out these links on how to get faster and more accurate answers:
  Forum Etiquette: How to post data/code on a forum to get the best help
  Need an Answer? Actually, No ... You Need a Question