cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

OJDBC8 stoped working on LTS 17.3

ScottDunk
New Contributor

Hi,

 

we upgraded our clusters to LTS 17.3 as we needed some functionality from that release and our OJDBC8 drivers have stopped working.  Downgraded back to LTS 14 and its all fine again.

What are the latest OJDBC drivers that are compatible with LTS 17.3?

1 REPLY 1

Ashwin_DSA
Databricks Employee
Databricks Employee

Hi @ScottDunk,

Looking at the release notes for LTS 14 and LTS 17.3, it appears to be a compatibility issue...

LTS 14:java14.pngLTS 17.3:java17.png As you can see from the images above, Databricks 17.3 LTS upgrades the cluster JVM to Java 17. Oracleโ€™s own compatibility matrix requires a JDKโ€‘17โ€‘certified JDBC driver (e.g., ojdbc10 or a recent ojdbc8 from the 19c line). The current driver youโ€™re using is an older ojdbc8 build that Oracle only certifies for Java 8/11, which is why it breaks once the JVM is Java 17. The recommended approach is to update the Oracle driver, not to keep the old Java 8 runtime.

Do you mind if I ask which version of Oracle you are currently using? Is it 19c or 21c?

If this answer resolves your question, could you mark it as โ€œAccept as Solutionโ€? That helps other users quickly find the correct fix.

 

 

 

Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***