locked
IBM DB2 --> SQL SERVER (DTS_E_INDUCEDTRANSFORMFAILUREONERROR & DTS_E_PRIMEOUTPUTFAILED) RRS feed

  • Question

  • Hello,

    I am getting the below Errors in SSIS.

    scenario: We have a pkg which connects the IBM DB2 and gets the data and loads it into SQL Server 2005 SP3 Enterprise Edition.

    We have multiple connctions to DB2 from the Pkgs and gets the data. If we run the each task as its own they executes fine, but if we run the whole Pkg at a time we are getting these errors.

    While running the whole pkg we did not see any RED failures on the tasks we did see only YELLOW but there is no progress. It hangs there forever. We noticed below errors on different tasks each time when we run. If its a size issue I should get the same error when I run each task on its own right?

    [DataReader Source [26693]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "component "DataReader Source" (26693)" failed because error code 0x80004003 occurred, and the error row disposition on "output column "XETPAN" (27479)" specifies failure on error. An error occurred on the specified object of the specified component.  There may be error messages posted before this with more information about the failure.

    Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on component "DataReader Source" (26693) returned error code 0xC02090F5.  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.

    Is anyone had this issue?

    Is it happing because of multiple connections to IBM DB2?

    Any help much appreciated.

    Thanks,
    Karumajji


    Karumajji
    Thursday, October 15, 2009 8:04 PM

Answers

  • I suppose a connection could be blocked by some DB2 setting.  Try setting your connection manager object's property, RetainSameConnection to True and see if that changes anything.
    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    Thursday, October 15, 2009 8:43 PM

All replies

  • I suppose a connection could be blocked by some DB2 setting.  Try setting your connection manager object's property, RetainSameConnection to True and see if that changes anything.
    Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer
    Thursday, October 15, 2009 8:43 PM
  • Maybe you're getting a deadlock?  Are you inserting into the DB2 system?


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, October 23, 2009 8:05 PM