Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Running extract rule generates errors in BIX log



When running an extract on an Oracle database source system, the extract generates error messages in the Business Intelligence Exchange (BIX) log.

Error Messages

internal.access.ExtractImpl) ERROR - SQL error while reading the blob: errorCode = 17014 was not called

Steps to Reproduce

Run the extract.

Root Cause

A defect or configuration issue in the operating environment.
The issue occurs when using the ojdbc6.jar JDBC driver (11.2.x) for Oracle instead of the ojdbc7 (12.1.x) driver.


Perform the following local-change:

Update the Oracle JDBC driver version on the system such that it uses the ojdbc7.jar.


Published August 24, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us