<docbook><section><title>JavaUnknownHostOdbc</title><title> Error Message: Connection failed: java.net.UnknownHostException: ODBC </title> Error Message: <computeroutput>Connection failed: java.net.UnknownHostException: ODBC</computeroutput> 
<para>Usually seen in a large block of Java error text, such as this -- </para><programlisting>java.sql.SQLException: [OpenLink][OPLJDBC3]Connection failed: java.net.UnknownHostException: ODBC
at openlink.jdbc3.OPLMessage.makeException(Unknown Source)
at openlink.jdbc3.Driver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
</programlisting><para> This message typically means our Type 3 Driver has been loaded instead of our Type 1 Driver.</para><para>You should generally have only one of the above drivers included in your CLASSPATH environment variable.
 Choose the one best matched to your active JVM, and supporting the connection Type, 1 or 3, you require.</para><para>Our Type 1 JDBC Drivers have the following attributes -- 
</para><table><title /><tgroup><thead /><tbody>
<row />
<row><entry> opljdbc.jar    </entry><entry> openlink.jdbc.Driver  </entry><entry>  JDBC 1         </entry><entry>  1.1.x             </entry></row>
<row><entry> opljdbc2.jar   </entry><entry> openlink.jdbc2.Driver </entry><entry>  JDBC 2         </entry><entry>  1.2.x and 1.3.x   </entry></row>
<row><entry> opljdbc3.jar   </entry><entry> openlink.jdbc3.Driver </entry><entry>  JDBC 3         </entry><entry>  1.4.x and 1.5.x   </entry></row>
<row><entry> opljdbc4.jar   </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4         </entry><entry>  1.6.x             </entry></row>
<row><entry> opljdbc4_1.jar </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4.1       </entry><entry>  1.7.x             </entry></row>
<row><entry> opljdbc4_2.jar </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4.2       </entry><entry>  1.8.x             </entry></row>
</tbody></tgroup></table>
<para>Our pure Type 3 JDBC Drivers have the following attributes -- 
</para><table><title /><tgroup><thead /><tbody>
<row />
<row><entry> megathin.jar    </entry><entry> openlink.jdbc.Driver  </entry><entry>  JDBC 1         </entry><entry>  1.1.x             </entry></row>
<row><entry> megathin2.jar   </entry><entry> openlink.jdbc2.Driver </entry><entry>  JDBC 2         </entry><entry>  1.2.x and 1.3.x   </entry></row>
<row><entry> megathin3.jar   </entry><entry> openlink.jdbc3.Driver </entry><entry>  JDBC 3         </entry><entry>  1.4.x and 1.5.x   </entry></row>
<row><entry> megathin4.jar   </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4         </entry><entry>  1.6.x             </entry></row>
<row><entry> megathin4_1.jar </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4.1       </entry><entry>  1.7.x             </entry></row>
<row><entry> megathin4_2.jar </entry><entry> openlink.jdbc4.Driver </entry><entry>  JDBC 4.2       </entry><entry>  1.8.x             </entry></row>
</tbody></tgroup></table>
<para> The pure Type 3 JDBC Drivers cannot be used for Type 1 connections.
 The Type 1 Drivers are produced as hybrids, and may also be used for Type 3 connections.</para><para> </para><bridgehead class="http://www.w3.org/1999/xhtml:h2"> Evidence </bridgehead>
<itemizedlist mark="bullet" spacing="compact"><listitem> CLASSPATH environment variable</listitem>
</itemizedlist><para> </para></section></docbook>