MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
DB2DriverRunFailed

What does this error mean?

The DB2 JDBC driver failed during an ADF copy activity. When the error contains SQLSTATE=51002 SQLCODE=-805, the required DB2 packages are missing or not bound to the database.

Common causes

  • 1The DB2 packages required for JDBC connectivity are not bound — indicated by SQLSTATE=51002 SQLCODE=-805
  • 2The packageCollection property is not configured, defaulting to a collection that does not have the required packages
  • 3The DB2 user account lacks EXECUTE privilege on the required packages

How to fix it

  1. 1Set the packageCollection property to "NULLID" in the ADF DB2 linked service configuration.
  2. 2Alternatively, ask the DB2 DBA to bind the required packages to the database: BIND PACKAGE (NULLID) .
  3. 3Verify the DB2 user account has EXECUTE privilege on the packages in the configured packageCollection.
  4. 4See the ADF DB2 connector documentation "Linked service properties" section for the packageCollection setting.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-db2

Other data source errors