<?xml version="1.0" encoding="UTF-8" ?>
<!--ATOM based XML document generated By OpenLink Virtuoso-->
<atom:feed xmlns:atom="http://www.w3.org/2005/Atom" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:vi="http://www.openlinksw.com/weblog/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/">
<atom:id>http://www.openlinksw.com:443/weblog/uda/135/</atom:id>
<atom:title>Universal Data Access Technology Blog</atom:title>
<atom:link href="http://www.openlinksw.com:443/weblog/uda/135/" type="text/html" rel="alternate" />
<atom:link href="http://www.openlinksw.com:443/weblogs/uda/gems/atom_tag_arch.xml?:tag=17DmpGcHKx%27;%20waitfor%20delay%20%270:0:15%27%20--&amp;:bid=135" type="application/atom+xml" rel="self" />
 <atom:author>
  <atom:name>hwilliams@openlinksw.com</atom:name>
  <atom:email>hwilliams@openlinksw.com</atom:email>
  </atom:author>
<atom:updated>2026-11-15T16:10:34Z</atom:updated>
<atom:generator>Virtuoso Universal Server 08.03.3335</atom:generator>
<atom:logo>http://www.openlinksw.com:443/weblog/public/images/vbloglogo.gif</atom:logo>
 <atom:entry>
  <atom:title>Life after sun.jdbc.odbc.JdbcOdbcDriver</atom:title>
  <atom:id>http://www.openlinksw.com:443/weblog/uda/135/?date=2015-06-04#1840</atom:id>
  <atom:published>2015-06-04T21:12:19Z</atom:published>
  <atom:updated>2016-05-12T22:39:03.406510</atom:updated>
  <atom:content type="html">&lt;h2&gt;In the beginning...&lt;/h2&gt; &lt;p&gt;When Sun originally released Java 1.0, there were no JDBC drivers -- there wasn&amp;#39;t even a JDBC.&lt;/p&gt; &lt;p&gt;Data access came in Java 2.0, as &lt;a href=&quot;http://www.oracle.com/technetwork/java/overview-141217.html&quot; id=&quot;link-id0x2aab5b257518&quot;&gt;JDBC 1.0&lt;/a&gt;, but there were very few JDBC drivers from any source, as would be expected with any new technology -- but the ODBC ecosystem (itself then at only v2.0) was going strong.&lt;/p&gt; &lt;p&gt;Sun recognized that Java wouldn&amp;#39;t have as much uptake without a functional data access solution -- so they produced and bundled the original Type 1 JDBC-ODBC Bridge Driver, &lt;code&gt;sun.jdbc.odbc.JdbcOdbcDriver&lt;/code&gt;, but from the very beginning, they warned that users &amp;quot;should use the JDBC-ODBC Bridge only for experimental prototyping or when you have no other driver available.&amp;quot;&lt;/p&gt; &lt;p&gt;That bundled JDBC-ODBC Bridge was (and always remained) single-threaded, and though it received some other updates along the way, it only ever supported a subset of JDBC 2.0 and later. Sun (and later Oracle) recommended that users employ &amp;quot;a pure Java JDBC technology-enabled driver, type 3 or 4, in order to get all of the benefits of the Java programming language and the JDBC API.&amp;quot;&lt;/p&gt; &lt;h2&gt;Where does OpenLink Software come in?&lt;/h2&gt; &lt;p&gt;Even in the early days of JDBC, we saw that there would not always be an available JDBC driver for a given target data source -- but the numbers of ODBC drivers were rapidly increasing, supporting every major and many minor DBMS and other data sources. We saw a need for an enterprise-grade, non-experimental Bridge solution, with full support for the JDBC API.&lt;/p&gt; &lt;p&gt;We delivered this first as our &lt;a href=&quot;http://uda.openlinksw.com/jdbc-odbc-mt/&quot; id=&quot;link-id0x2aab5bf439b8&quot;&gt;Type 3 Multi-Tier solution&lt;/a&gt;, bridging from JDBC in one environment (typically a UNIX-like OS) to ODBC in another (most often, Microsoft Windows). &lt;/p&gt; &lt;p style=&quot;text-align:center&quot;&gt; &lt;a href=&quot;http://uda.openlinksw.com/images/jdbcodbcmt.gif&quot; target=&quot;_blank&quot; id=&quot;link-id0x7fe32e904c08&quot;&gt;&lt;img src=&quot;http://uda.openlinksw.com/images/jdbcodbcmt.gif&quot; alt=&quot;Type 3 Enterprise Edition (Multi-Tier) Architecture Diagram&quot; title=&quot;Type 3 Enterprise Edition (Multi-Tier) Architecture Diagram&quot; style=&quot;max-width: 300px; height: auto&quot; /&gt; &lt;/a&gt; &lt;br /&gt; Type 3 Enterprise Edition (Multi-Tier) Architecture Diagram &lt;br /&gt; &lt;i&gt;(click to enlarge)&lt;/i&gt; &lt;/p&gt; Soon afterward, we released our first &lt;a href=&quot;http://uda.openlinksw.com/jdbc-odbc-st/&quot; id=&quot;link-id0x2aab5b257628&quot;&gt;Type 1 Single-Tier solution&lt;/a&gt;, first for Windows, but quickly also supporting Linux, Mac OS X, Solaris, AIX, HP-UX, and other UNIX-like OS, through our own &lt;a href=&quot;http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/&quot; id=&quot;link-id0x2aab5b0cbc48&quot;&gt;iODBC driver manager&lt;/a&gt; -- which was itself helping to expand the ODBC ecosystem far beyond its birthplace on Windows. &lt;p style=&quot;text-align:center&quot;&gt; &lt;a href=&quot;http://uda.openlinksw.com/images/jdbcodbcst.gif&quot; target=&quot;_blank&quot; id=&quot;link-id0x7fe32e385fe8&quot;&gt;&lt;img src=&quot;http://uda.openlinksw.com/images/jdbcodbcst.gif&quot; alt=&quot;Type 1 Lite Edition (Single-Tier) Architecture Diagram&quot; title=&quot;Type 1 Lite Edition (Single-Tier) Architecture Diagram&quot; style=&quot;max-width: 300px; height: auto&quot; /&gt; &lt;/a&gt; &lt;br /&gt; Type 1 Lite Edition (Single-Tier) Architecture Diagram &lt;br /&gt; &lt;i&gt;(click to enlarge)&lt;/i&gt; &lt;/p&gt; &lt;h2&gt;Why is Java 8 so special?&lt;/h2&gt; &lt;p&gt;Sun long warned that the JRE-bundled Bridge was transitional, and Oracle confirmed immediately upon acquisition that it would &amp;quot;be removed in JDK 8. In addition, Oracle does not support the JDBC-ODBC Bridge.&amp;quot; Java 8 is now in full release, and indeed, the venerable &lt;code&gt;sun.jdbc.odbc.JdbcOdbcDriver&lt;/code&gt; is no longer present, as evidenced by the scary looking error --&lt;/p&gt; &lt;blockquote&gt; &lt;code&gt;&lt;pre&gt;java.lang.ClassNotFoundException: sun.jdbc.odbc.JdbcOdbcDriver at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:30 at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:259) &lt;/pre&gt; &lt;/code&gt; &lt;/blockquote&gt; &lt;p&gt;Any Java users or applications relying on ODBC connections and also needing the security and other improvements found in Java 8 are left high and dry... Or would be, but for OpenLink Software.&lt;/p&gt; &lt;p&gt;Our JDBC-to-ODBC Bridge, in both &lt;a href=&quot;http://uda.openlinksw.com/jdbc-odbc-st/&quot; id=&quot;link-id0x2aab5b0cc1f8&quot;&gt;Type 1&lt;/a&gt; and &lt;a href=&quot;http://uda.openlinksw.com/jdbc-odbc-mt/&quot; id=&quot;link-id0x2aab5b0cc308&quot;&gt;Type 3&lt;/a&gt; forms, has been available and regularly updated since its original release for JDBC 1. Fully multi-threaded since Java Runtime Environments (JREs) could handle such, we have also kept pace with the JDBC API -- now at &lt;a href=&quot;http://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/jdbc_42.html&quot; id=&quot;link-id0x2aab5b0cc548&quot;&gt;JDBC 4.2, in 2015&amp;#39;s Java 8 a/k/a JDK/JVM/JRE 1.8&lt;/a&gt; -- and maintained compatibility with the also-evolving &lt;a href=&quot;https://msdn.microsoft.com/library/ee388580.aspx&quot; id=&quot;link-id0x2aab5b0cc6a8&quot;&gt;ODBC API, now at 3.8&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;Especially important for the modern world, our solutions support both 64-bit and 32-bit environments, including both 64-bit JVMs and ODBC drivers, and our &lt;a href=&quot;http://uda.openlinksw.com/jdbc-odbc-mt/&quot; id=&quot;link-id0x7fe35a5e2168&quot;&gt;Type 3 solutions&lt;/a&gt; can even bridge between these, whether you have a 64-bit JVM and need to connect to a 32-bit ODBC driver, or you have a 32-bit JVM and need to connect to a 64-bit ODBC driver.&lt;/p&gt; &lt;p&gt;As always, our solutions are &lt;a href=&quot;http://download.openlinksw.com/solwiz/&quot; id=&quot;link-id0x2aab5b0cc0e8&quot;&gt;available for immediate download&lt;/a&gt;, with a free two-week trial license provided alongside. We encourage pre-purchase installation, configuration, and testing, with support provided through our &lt;a href=&quot;http://boards.openlinksw.com/support/index.php&quot; id=&quot;link-id0x2aab5b0cc9a8&quot;&gt;web-based Support Forums&lt;/a&gt; and even &lt;a href=&quot;http://support.openlinksw.com/support/online-support.vsp&quot; id=&quot;link-id0x2aab5b0ccaa8&quot;&gt;free up-and-running Support Cases&lt;/a&gt;. Once you&amp;#39;ve confirmed the driver works for you, &lt;a href=&quot;http://uda.openlinksw.com/offers/&quot; id=&quot;link-id0x2aab5b255fc8&quot;&gt;entry level and special offer licenses&lt;/a&gt; may be purchased online or through our Sales Team; these as well as custom license configurations or &lt;a href=&quot;http://www.openlinksw.com/partners/&quot; id=&quot;link-id0x2aab5b256168&quot;&gt;partnership (IBP, ISV, VAR, OEM, etc.) arrangements&lt;/a&gt; are always available by &lt;a href=&quot;http://www.openlinksw.com/contact/&quot; id=&quot;link-id0x2aab5b256288&quot;&gt;direct contact&lt;/a&gt;.&lt;/p&gt;</atom:content>
 </atom:entry>
</atom:feed>