Version Compatibility for Oracle JDBC Drivers This section discusses the general JDBC version compatibility issues. Backward Compatibility Oracle Database 12 c Release 1 (12.1) JDBC drivers are certified with supported Oracle Database releases (11.x.0.x). However, they are not certified to work with older, unsupported database releases, such as 10.2.x, 10.1.x, 9.2.x, and 9.0.1.x. Forward Compatibility Existing and supported JDBC drivers are certified to work with Oracle Database 12 c Release 1 (12.1). Verifying a JDBC Client Installation To verify a JDBC client installation, you must do all of the following: • • • • • This section describes the steps for verifying an Oracle client installation of the JDBC drivers, assuming that you have already installed the driver of your choice. Installation of an Oracle JDBC driver is platform-specific.

Server Manager allows you to centrally manage JDBC drivers that are required to enable the various web-based servers. Classes12.jar: Oracle 10g (JDK 1.4) ojdbc4.jar. Certified with JDK 8; It contains the JDBC driver classes except classes for NLS support in Oracle Object and Collection types. Ojdbc8_g.jar (6,708,730 bytes) - (SHA1.

You must follow the installation instructions for the driver you want to install in your platform-specific documentation. If you use the JDBC Thin driver, then there is no additional installation on the client computer. If you use the JDBC Oracle Call Interface (OCI) driver, then you must also install the Oracle client software.

This includes Oracle Net and the OCI libraries. Check the Installed Directories and Files Installing the Oracle Java products creates, among other things, the following directories: • ORACLE_HOME /jdbc • ORACLE_HOME /jlib Check whether or not the following directories and files have been created and populated in the ORACLE_HOME /jdbc directory: • demo This directory contains a compressed file, demo.zip or demo.tar. When you uncompress this compressed file, the samples directory and the Samples-Readme.txt file are created.

I was looking at the following link to find out the JDBC driver for 11g. You don't need to change the JDBC jar file. See the Oracle JDBC FAQ 'Which JDBC drivers.

The samples directory contains sample programs, including examples of how to use JDBC escape syntax and Oracle SQL syntax, PL/SQL blocks, streams, user-defined types, additional Oracle type extensions, and Oracle performance extensions. • doc This directory contains the javadoc.zip file, which is the Oracle JDBC application programming interface (API) documentation. • lib The lib directory contains the following required Java classes: • orai18n.jar and orai18n-mapping.jar Contain classes for globalization and multibyte character sets support • ojdbc6.jar, ojdbc6_g.jar, ojdbc7.jar, and ojdbc7_g.jar Contain the JDBC driver classes for use with JDK 6 and JDK 7. Note: • Since Oracle Database 11 g Release 1, support for a version of JDK earlier than version 5.0 has been removed. Also, the ojdbc14.jar, ojdbc5.jar and classes12.jar files are no longer shipped.

Instead, you can use the ojdbc6.jar and ojdbc7.jar files, which are shipped with Oracle Database 12 c. • If you are using JSE 6 and later, then there is no need to explicitly load the JDBC driver.

This means that the Java run-time loads the driver when needed and you need not include Class. Analog Devices Ad1888 @ Sis 7012 Audio Device Pci on this page. forName('oracle.jdbc.OracleDriver') or new oracle.jdbc.OracleDriver() in your code. But if you are using J2SE 5.0, then you need to load the JDBC driver explicitly. • Readme.txt This file contains late-breaking and release-specific information about the drivers, which may not have been included in other documentation on the product. Check whether or not the following directories have been created and populated in the ORACLE_HOME /jlib directory: • jta.jar and jndi.jar These files contain classes for the Java Transaction API (JTA) and the Java Naming and Directory Interface (JNDI).

These are required only if you are using JTA features for distributed transaction management or JNDI features for naming services. Note: If you use the JTA features and the JNDI features, then you must specify jta.jar and jndi.jar in your CLASSPATH environment variable.

JDBC OCI Driver To use the JDBC OCI driver, you must also set the following value for the library path environment variable: • On Solaris or Linux, set the LD_LIBRARY_PATH environment variable as follows: ORACLE_HOME/lib This directory contains the libocijdbc11.so shared object library. • On Microsoft Windows, set the PATH environment variable as follows: ORACLE_HOME bin This directory contains the ocijdbc11.dll dynamic link library. All of the JDBC OCI demonstration programs can be run in the Instant Client mode by including the JDBC OCI Instant Client data shared library on the library path environment variable. See Also: JDBC Thin Driver To use the JDBC Thin driver, you do not have to set any other environment variables. However, to use the JDBC server-side Thin driver, you need to set permission.