Type Two Driver

A native-API partly Java technology-enabled driver converts JDBC calls into calls on the client API for DBMSs. Like the bridge driver, this style of driver requires that some binary code be loaded on each client machine. An example of this type of driver is the Oracle Thick Driver, which is also called OCI.

Advantages for using this type of driver include the following:

• Allows access to almost any database since the databases ODBC drivers are readily available

• Offers significantly better performance than the JDBC/ODBC Bridge

• Limited Java feature set

Disadvantages for using this type of driver include the following:

• Applicable Client library must be installed

• Type 2 driver shows lower performance than type 3 or 4