Post reply

Processing was cancelled due to an interrupt. SQLSTATE=57014

  • January 5, 2011 at 2:06 am

    #388555

    My SSIS package throws below error while fetching data from DB2 to SQL Server. SSIS package fetch 50 tables from DB2. but this throws error only for 1 or 2 tables repeatedly.

    Source: Data Flow Task ADO NET Source [90] Description: The component "ADO NET Source" (90) was unable to process the data. ERROR [HY008] [IBM][CLI Driver][DB2/AIX64] SQL0952N Processing was cancelled due to an interrupt. SQLSTATE=57014 End Error Error: 2011-01-04 23:05:39.74 Code: 0xC0047038 Source: Data Flow Task SSIS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "ADO NET Source" (90) returned error code 0xC02090F5.

    Appriciate if someone show some light on this.

  • January 5, 2011 at 3:17 am

    #1269378

    I think it has more to do with DB2 then with SQL Server or SSIS, so you should probably check out your source.

    Probably an issue with QUERYTIMEOUTINTERVAL.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 5, 2011 at 3:30 am

    #1269382

    Thanks Koen for the quick response.

    We get the same error ever after changing querytimeout of DB2 client to 0.

    is there any property to be configured in DB2 Server? any idea

  • January 5, 2011 at 3:50 am

    #1269392

    Ramkumar (LivingForSQLServer) (1/5/2011)

    Thanks Koen for the quick response.

    We get the same error ever after changing querytimeout of DB2 client to 0.

    is there any property to be configured in DB2 Server? any idea

    I have no idea 🙂

    I have no experience with DB2, I just found out about querytimeout through a quick google search.

    Anayway, I think you might have more luck in specialized DB2 forums.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • August 15, 2012 at 9:13 am

    #1526046

    Kindly Help me out ...Even I face the same Issue...

    Is there anything to do with teh DB2 settings like time out etc.,

    From SSIS do I have to configure the ADO.Net Source Command Timeout ...to 0??

    Please let me know the resolution

    Regards

    Gayathri.B

  • August 15, 2012 at 9:52 am

    #1526073

    gayathri-b (8/15/2012)

    Kindly Help me out ...Even I face the same Issue...

    Is there anything to do with teh DB2 settings like time out etc.,

    From SSIS do I have to configure the ADO.Net Source Command Timeout ...to 0??

    Please let me know the resolution

    Regards

    Gayathri.B

    This is a SQL Server forum, not DB2. You're asking the wrong people.

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • August 16, 2012 at 2:05 am

    #1526376

    Hello MR-Hall of Fame

    Thanks for enlightening me...!!

    But I feel question has something more to do with SSIS +DB2,If a person has faced similar issue ,I guess its nothing wrong in seeking an opinion in very much relevant forum..

    rather than worrying more about the place where we post and how we post.

  • August 16, 2012 at 1:31 pm

    #1526812

    seem my response is not updated here.

    we fixed that issue by updating DB2 client driver, changing DB2 data source property b/w ADO and OLEDB

    and by trying differnt DB2 property values in SSIS. hope this helps

  • August 20, 2012 at 1:43 am

    #1527453

    Hello ramkumar,

    Thanks a lot for your response...

    It would be great if you can let me knwo what has to be changed in the DB2 Client Driver.

    By the second statement ,do you mean to use OLEDB data provider for db2 in SSIS data flow task rather than using the ADo.Net Data source Task ??

    Am using Ado.net source task..but Am not sure regarding the setting of DB2 Properties in the SSIS

    I face this Issue only when I try to pull information from the DB2 Database source,by running jobs in two different servers at the same time.

    I also tried tos et the command timeout property of Ado.net source to 0 .But still I get this error

    kindly please elaborate regarding the fix..

    I would be highly obliged.

    Thanks in advance!!

  • September 12, 2012 at 7:52 am

    #1536720

    i have the same issue,

    would be great if more details could be given as to what was changed.

    latest IBM driver is 9.7, but then there is also 10.1 (in testing i guess)

    thanks

  • September 12, 2012 at 2:27 pm

    #1536915

    I do not remember exact fix for this issue. focus on driver updates, try with ADO and OLEDB with different properties. thanks.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply