Support Article
Running extract rule generates errors in BIX log
SA-61483
Summary
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 errorMessage:ResultSet.next 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.