Atitit. Summary of how the client connects to the oracle database

Client connection to the oracle database summary directory Java program connection is generally connected using the jar driver ..... 1 desktop GUI generally uses C language to drive oci. dll1 direct connection... 1 Indirect Connection (tns and envivar need to be configured )... four types of 1JDBC driver... 1 Java program connection is generally connected using the jar driver .. The ID string is t.

Client connection to the oracle database summary directory Java program connection is generally connected using the jar driver ..... 1 desktop GUI generally uses C language to drive oci. dll1 direct connection... 1 Indirect Connection (tns and its envi var need to be configured )... 1. Four types of JDBC drivers... 1 Java program connection is generally connected using the jar driver .. The ID string is t.

Summary of how the client connects to the oracle database

Directory

Java program connection is generally connected using the jar driver ..... 1

The desktop GUI generally adopts the C language to drive oci. dll1

Connect directly... 1

Indirect Connection (tns and its envi var need to be configured)... 1

Four types of JDBC drivers... 1

Java program connection generally uses the jar driver connection ..

The identifier string is thin... It is also called the thin driver.

Of course, you can also use the oci c Class Library driver to identify the string as oci. However, considering jni calls, increasing layers may not necessarily improve performance ..

Author old wow's paw Attilax iron, EMAIL: 1466519819@qq.com
Reprinted please indicate Source: http://blog.csdn.net/attilax

The desktop GUI generally adopts the C language to drive oci. dll.

Oci is the abbreviation of Oracle CallInterface. Using the OCI driver can achieve the best performance, while using java

The thin driver can achieve the best portability.

Unfortunately, neither plsql nor toed comes with oci. dll .... Only navicate comes with the oci driver. The actual oci. dll is only 1 M-2 M ..

. While oci. dll can be extracted from the ora client, or HA-Instant Client-v11.2.0.3.0-x86.rar (45 M )..

Direct Connection

This method is the best and convenient .... Supported by navicate. plsql can only use indirect connections, and toad also seems to be able to connect indirectly ..

Common mysql and mssql are also directly connected, so the user experience is good ..

Indirect Connection (tns and envi var need to be configured)

Relatively troublesome .. Centralized configuration management, which is useful in many client programs ..

Four JDBC driver types

1. JDBC-ODBC bridge plus ODBCdriver: JDBC-ODBC bridge driver, which converts JDBC calls to ODBC calls. (This combination provides JDBC access via ODBC drivers. ODBC binarycode -- and in parallel cases, database client code -- must be loaded on each clientmachine that uses a JDBC-ODBC Bridge. sun provides a JDBC-ODBC Bridge driver, which is appropriate for experimental use and for situations in which no otherdriver is available .) note that ODBC binary code (including database client code in many cases) must be loaded to each client using the driver. This type of driver is most suitable for Enterprise Network (the installation of the client on this network is not a major problem), or a layer-3 Application Server written in Java 5, server code.

2. Native-API partly-Java driver: converts a JDBC call to a call to the database client API. (A native-API partly Java technology-enabled driver: This type ofdriver converts JDBC callinto callon the client API for Oracle, Sybase, Informix, DB2, or other DBMS. note that, like the bridge driver, this style ofdriver requires that some binary code be loaded on each client machine .) this type of driver converts JDBC calls on the client API to Oracle, Sybase, Informix, DB2, or other DBMS calls. Note that, like a bridge driver, this type of driver requires that some binary code be loaded to each client.

3. Pure Java Driver for Database Middleware: first, the JDBC call is converted to the DBMS-independent network protocol, and then the Middleware on the server is converted to the network protocol that can be received by the specific Database server. (Net-protocol fully Javatechnology-enabled driver # This style of driver translates JDBC callinto themiddleware vendor's protocol, which is then translated to a DBMS protocol by amiddleware server. the middleware provides connectivity to includifferentdatabases .) this network server middleware can connect its pure Java client to a variety of different databases. The specific protocol used depends on the provider. Generally, this is the most flexible JDBC driver. It is possible that providers of all such solutions provide products suitable for Intranet. In order for these products to support Internet access, they must handle additional requirements for Web security and access through the firewall. Several providers are adding JDBC drivers to their existing database middleware Products.

4. Direct-to-Database Pure JavaDriver: converts a JDBC call directly to a network protocol that can be received by a specific Database server. (Native-protocol fully Javatechnology-enabled driver # This style of driver converts JDBC callinto thenetwork protocol used directly by DBMSs, allowing a direct call from the clientmachine to the DBMS server and providing a practical solution for intranetaccess .) this will allow direct calls to the DBMS server from the client machine, which is a very practical solution for Intranet access. Since many of these protocols are dedicated, the Data Warehouse provider itself will be the main source, and several providers are already working on this.

3rd and 4 drivers will become the preferred method to access the database from JDBC. 1st and 2 drivers will be used as a transitional solution before the direct pure Java driver is available. There may be some variants of the 1st and 2 Drivers (not listed in the table below) that require connectors, but these are generally more undesirable solutions. 3rd and 4 drivers provide all the advantages of Java, including automatic installation (for example, downloading the driver by using the applet Of The JDBC driver ).

Reference

Oracle-to-oracle jdbc Connection Methods: oci and thin-phoebus0501-blog .htm