JDBC Overview and several drivers

Dbvisualizer 8.0.10 connecting Oracle database error 172001
Cause: Database driver error Ojdbc14.jar version is too low to be replaced by Ojdbc6.jar.

To remind you, Ojdbc6.jar is much higher than the Ojdbc14.jar version, because 6 of it means support for jdk1.6, while 14 means supporting jdk1.4. Please note that also useful 14 and since the version is very high quick change, because the new version solves a lot of bugs.

The following describes the JDBC overview and several drivers

JDBC (Java database Connectivity, DB connection) is the Java API used to execute SQL. Developers can use these standard APIs to connect and manipulate the database JDBC is the Java specification, taking into account the applicability of the specification. JDBC provides only the most straightforward database specification. The classes in the java.sql package are the standard methods that Java uses to connect to a database.

JDBC has the following 3 product components:

1) JDBC Driver Manager: Is the backbone of the JDBC architecture. He is actually very small, and very simple, the main role is to connect Java to the specified JDBC driver, and then exit

2) JDBC Driver Test Tool: Provides a certain level of confidence for the driver for the JDBC driver developer. Only drivers passed through the JDBC test will be considered to be JDBC compliant.

3) JDBC-ODBC Bridge: The ODBC driver can be used as the JDBC driver. Its emergence provides a way for the rapid development of JDBC, and its long-term goal is to provide access to some of the less common DBMS methods.

Common JDBC drivers fall into the following categories:

(1) Jdbc-odbc Bridge +ODBC Driver

JavaSoft Bridge products Use the ODBC driver to provide JDBC access. Note that ODBC binaries, in many cases including database client code, must be loaded into the

On each client with the driver. As a result, this type of driver is best suited to the Enterprise network (the installation of clients on this network is not a major problem), or Java

Write the application server code for the three-tier structure.

(2) Local API

This type of driver translates the JDBC calls on the client API into calls to Oracle, Sybase, Informix, DB2, or other DBMS. Note that the Elephant Bridge driver One

, this type of driver requires that some binary code be loaded onto each client.

(3) JDBC Network Pure Java driver This driver translates jdbc into a DBMS-independent network protocol, which is then transformed by a server into a DBMS protocol. This network server middleware can

To connect its pure Java client to a number of different databases. The specific protocol used depends on the provider. Typically, this is the most flexible JDBC driver. It's possible that all this

Providers of solutions provide products that are suitable for use in the intranet. To enable these products to also support Internet access, they must deal with the security of the web, by preventing

Additional requirements for access to the firewall. Several providers are adding JDBC drivers to their existing database middleware products.

(4) Local protocol Pure Java driver This type of driver translates the JDBC call directly into the network protocol used by the DBMS. This allows the DBMS server to be called directly from the client machine and is a useful workaround for intranet access. Since many of these protocols are dedicated, the database provider itself will be the main source, and several providers are already doing it

The

According to experts, the category (3), (4) drivers will be the first way to access the database from JDBC. The (1), (2) class drivers are also in the direct pure Java driver

It will be used as a transition plan before listing. There may be variants for the (1), (2) class of drivers, which require connectors, but usually these are more inaccessible

Solution. The (3), (4) class drivers provide all the benefits of Java, including automatic installation (for example, by using the appletapplet of the JDBC driver to download

The driver).

JDBC Overview and several drivers