Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 








Oracle Database Tips by Donald BurlesonJuly 17,  2015

JDBC Server-Side Internal Driver for RAC

The Oracle JDBC server-side internal driver supports any Java code that runs inside an Oracle database, such as Java stored procedures or Enterprise JavaBeans, and must access the same database. This driver allows the Java Virtual Machine (JVM) to communicate directly with the SQL engine. This allows the server-side internal driver, JVM, database, KPRB (server-side) C library, and SQL engine to all run within the same address space. When running code using the server-side internal drivers within an Oracle RAC instance, it basically runs in that particular database instance.

The middleware software layers now handle connectivity to the backend Oracle database. Let us examine how some of the popular application servers handle database connectivity and utilize the RAC database.

JDBC Oracle Call Interface Driver

The JDBC OCI driver is a Type II driver for use with client-server Java applications. This driver requires an Oracle client installation, and therefore is Oracle platform-specific and not suitable for applets but great for RAC.

The JDBC Oracle Call Interface (OCI) driver accesses Oracle and RAC-specific native code (that is, non-Java) libraries on the client or middle tier, providing a richer set of functions, and some performance boost compared to the JDBC Thin driver, especially in RAC.

Using the JDBC OCI driver allows the tnsnames.ora entry to be used. Therefore, it is a good choice to access the Oracle RAC database with the full functionality of the TAF configuration for load balancing and automatic failover.

While using the JDBC OCI driver with RAC, the database can be specified with an Oracle Net keyword-value pair. The Oracle Net keyword-value pair substitutes for the tnsnames entry. The following example uses the same parameters as the preceding example, but in the keyword-value format:

Connection conn = DriverManager.getConnection

Here is a JDBC connect string for connecting to Oracle via JDBC:


See these related notes on using Real Application Clusters with JDBC:

Oracle Grid and Real Application Clusters

See working examples of Oracle Grid and RAC in the book Oracle Grid and Real Application Clusters.

Order directly from Rampant and save 30%. 



Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.