<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OJDBC8 stoped working on LTS 17.3 in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/ojdbc8-stoped-working-on-lts-17-3/m-p/151392#M5032</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/151411"&gt;@ScottDunk&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Looking at the release notes for &lt;A href="https://docs.databricks.com/aws/en/release-notes/runtime/14.3lts#system-environment" target="_blank"&gt;LTS 14&lt;/A&gt; and &lt;A href="https://docs.databricks.com/aws/en/release-notes/runtime/17.3lts#system-environment" target="_self"&gt;LTS 17.3&lt;/A&gt;, it appears to be a compatibility issue...&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;LTS 14:&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="java14.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/24999i6D6EC62E62A1467E/image-size/large?v=v2&amp;amp;px=999" role="button" title="java14.png" alt="java14.png" /&gt;&lt;/span&gt;&lt;STRONG&gt;LTS 17.3:&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="java17.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25000iD78731743AFF8122/image-size/large?v=v2&amp;amp;px=999" role="button" title="java17.png" alt="java17.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;SPAN&gt;As you can see from the images above,&amp;nbsp;Databricks 17.3 LTS upgrades the cluster JVM to Java 17&lt;/SPAN&gt;&lt;SPAN&gt;. 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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Do you mind if I ask which version of Oracle you are currently using? Is it 19c or 21c?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Mar 2026 11:57:26 GMT</pubDate>
    <dc:creator>Ashwin_DSA</dc:creator>
    <dc:date>2026-03-19T11:57:26Z</dc:date>
    <item>
      <title>OJDBC8 stoped working on LTS 17.3</title>
      <link>https://community.databricks.com/t5/administration-architecture/ojdbc8-stoped-working-on-lts-17-3/m-p/151383#M5031</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we upgraded our clusters to LTS 17.3 as we needed some functionality from that release and our OJDBC8 drivers have stopped working.&amp;nbsp; Downgraded back to LTS 14 and its all fine again.&lt;/P&gt;&lt;P&gt;What are the latest OJDBC drivers that are compatible with LTS 17.3?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 10:56:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/ojdbc8-stoped-working-on-lts-17-3/m-p/151383#M5031</guid>
      <dc:creator>ScottDunk</dc:creator>
      <dc:date>2026-03-19T10:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: OJDBC8 stoped working on LTS 17.3</title>
      <link>https://community.databricks.com/t5/administration-architecture/ojdbc8-stoped-working-on-lts-17-3/m-p/151392#M5032</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/151411"&gt;@ScottDunk&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Looking at the release notes for &lt;A href="https://docs.databricks.com/aws/en/release-notes/runtime/14.3lts#system-environment" target="_blank"&gt;LTS 14&lt;/A&gt; and &lt;A href="https://docs.databricks.com/aws/en/release-notes/runtime/17.3lts#system-environment" target="_self"&gt;LTS 17.3&lt;/A&gt;, it appears to be a compatibility issue...&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;LTS 14:&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="java14.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/24999i6D6EC62E62A1467E/image-size/large?v=v2&amp;amp;px=999" role="button" title="java14.png" alt="java14.png" /&gt;&lt;/span&gt;&lt;STRONG&gt;LTS 17.3:&lt;/STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="java17.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/25000iD78731743AFF8122/image-size/large?v=v2&amp;amp;px=999" role="button" title="java17.png" alt="java17.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;SPAN&gt;As you can see from the images above,&amp;nbsp;Databricks 17.3 LTS upgrades the cluster JVM to Java 17&lt;/SPAN&gt;&lt;SPAN&gt;. 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.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Do you mind if I ask which version of Oracle you are currently using? Is it 19c or 21c?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2026 11:57:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/ojdbc8-stoped-working-on-lts-17-3/m-p/151392#M5032</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-03-19T11:57:26Z</dc:date>
    </item>
  </channel>
</rss>

