Sqlplus previous commands work in the command prompt only if you set environment variables.
So, the JDBC driver must have the same version as the Oracle server. And this native library is a part of Oracle server software. When the Oracle Instant Client is installed on the machine with the Oracle server, the JDBC driver uses the native library to connect to the Oracle server. But if we switch to Oracle driver 19.8.0.0, the connection will be successful. If we use the Oracle driver 19.3.0.0, we are going to get Incompatible version of libocijdbc. Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production Otherwise, you will see errors like Native library cannot be loaded or Incompatible version of libocijdbc.įor example, consider the following Oracle setup: But the JDBC driver must have the same version as the Oracle Instant Client. For example, Oracle Client 19.x can successfully connect to Oracle server 11.2. When the Oracle Instant Client is installed on a separate machine, versions of the Oracle Instant Client and Oracle Server may differ. Compatibility of versions in OCI mode Installation on separate machines In this case, the JDBC driver's version must be the same as the version of these native libraries. In OCI mode, the JDBC driver uses native libraries. In this mode, various versions of the JDBC driver can be used. In thin mode, the JDBC driver always connects to the TNS listener.
Oracle client download setup mfile drivers#
DataGrip uses JDBC drivers to connect to the Oracle server through the TNS protocol.
0 kommentar(er)
