question

SiddharthaReddy-2322 avatar image
0 Votes"
SiddharthaReddy-2322 asked KranthiPakala-MSFT commented

ADF V2 pipeline failing with DB2 connector in one resource but successfully ran in another resource with same source.

Hi,

I'm getting an error in ADF V2 pipeline. The source is IBM DB2 database. Test connection is successful, but giving error while querying the DB.

Here's the error.

Failure happened on 'Source' side. 'Type=Microsoft.HostIntegration.DrdaClient.DrdaException,Message=Routine "SYSIBM.SQLSTATISTICS" (specific name "STATISTICS") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-572". SQLSTATE=38553 SQLCODE=-443,Source=Microsoft.HostIntegration.Drda.Requester,'

PS: There was an activity from IBM cloud to upgrade the DB2 cloud databases to latest version and maintenance. Since then the pipeline started to fail.

Any pointers/help is very much appreciated.

Thanks,
Sid

azure-data-factory
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SiddharthaReddy-2322 avatar image
0 Votes"
SiddharthaReddy-2322 answered

This has been resolved after the IBM team ran some binding packages after the DB upgrade. Below the link for reference.

https://www.ibm.com/docs/en/db2/11.5?topic=pack-binding-bind-files-after-installing-fix-packs

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KranthiPakala-MSFT avatar image
0 Votes"
KranthiPakala-MSFT answered KranthiPakala-MSFT commented

Hi @siddharthareddy-2322,

Welcome to Microsoft Q&A forum and thanks for reaching out. As you stated that the issue started upgrade of the version on IBM DB2 side, it seems like a versioning issue.

Please refer to this related article from IBM which has possible root cause and resolution details and see if that helps to resolve the issue: SQL0443N with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553 when calling stored procedure SYSIBM.SQLXXXXXXX()

In case if it wasn't helpful I would recommend to reach out in IBM community forum as the error message is more specific to IBM DB2 and IBM community forum is better suited for this ask. Here is the the IBM Community forum link: https://community.ibm.com/community/user/home

Hope this info helps. Do let us know how it goes.



Please don’t forget to Accept Answer and Up-Vote wherever the information provided helps you, this can be beneficial to other community members.


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @KranthiPakala-MSFT ,

Thanks for the welcome and the info. It seems you're right about the versioning issue. I will contact IBM support and try to take their help and will let you know how it goes.

Thanks!
Sid

0 Votes 0 ·

Hi @siddharthareddy-2322, Thanks for your response. Please do keep this thread updated on with your findings from IBM support.




Please don’t forget to Accept Answer and Up-Vote wherever the information provided helps you, this can be beneficial to other community members.

0 Votes 0 ·

Hi @KranthiPakala-MSFT , it has been resolved after the IBM team ran some binding packages after the DB upgrade. Below the link for reference.

https://www.ibm.com/docs/en/db2/11.5?topic=pack-binding-bind-files-after-installing-fix-packs

Thanks anyways for your support and response.

Regards,
Sid

0 Votes 0 ·
Show more comments