DataGrip
 
2023.2
Shortcuts: Windows
Get DataGrip
You are viewing the documentation for an earlier version of DataGrip.
  1. Support and troubleshooting
  2. Troubleshooting
  3. Cannot connect to Oracle with OCI

Cannot connect to Oracle with OCI

Last modified: 20 October 2023

If the connection to Oracle database with OCI cannot be established, try the following to resolve the problem:

  1. Make sure the versions are compatible.

  2. Check the files and environment.

Check the compatibility of versions

Installation on separate machines

When the Oracle Instant Client is installed on a separate machine, versions of the Oracle Instant Client and Oracle Server may differ. For example, Oracle Client 19.x can successfully connect to Oracle server 11.2. But the JDBC driver must have the same version as the Oracle Instant Client. Otherwise, you will see errors like Native library cannot be loaded or Incompatible version of libocijdbc.

For example, consider the following Oracle setup:

  • Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

  • Oracle Instant Client 19.8.0.0

If we use the Oracle driver 19.3.0.0, we are going to get Incompatible version of libocijdbc. But if we switch to Oracle driver 19.8.0.0, the connection will be successful. Consider the following animation.

https://resources.jetbrains.com/help/img/idea/2023.2/db_incompatible_version_of_libocijdbc.png
Gif

Installation on the same machine

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. And this native library is a part of Oracle server software. So, the JDBC driver must have the same version as the Oracle server.

Summary table

Separate machines

Same machine

Versions of Oracle Instant client and Server

May differ

Will be the same (as the Oracle Instant Client is a part of Oracle server software)

Version of the JDBC driver

Same as the Oracle Instant client

Same version as the Oracle server

Check the versions

  1. To find the JDBC driver version in DataGrip, do the following:

    1. In the Data Sources and Drivers dialog (CtrlAltShift0S), select the data source and click the Driver list and select Go to Driver to access the Drivers tab of the dialog.

    2. In the Drivers tab, find the JDBC driver version in the Driver Files pane.

    For more information about how to configure the driver, refer to Configure a JDBC driver for an existing data source.

  2. Check the versions of Oracle Instant client and Server.

Files and environment variables

Requirements

The following OCI packages are required:

  1. Basic Package

  2. SQL*Plus Package

  3. JDBC Supplement Package

Packages for your operating system can be downloaded from the Oracle Instant Client Downloads page at oracle.com.

Step 1. Check the extracted files

All the files from downloaded packages must be extracted in the same directory.

  • Find the directory with extracted Instant Client files (for example, ~/Oracle/instantclient_19_8/) and make sure that none of them are missing.

Step 2. (Optional) Check environment variables

This is optional. With the environment variables being set, you can connect to your Oracle instance with the sqlplus tool. Note that these settings work only for the current session of the command prompt.

Step 3. Verify the ORA files configuration

Make sure that the tnsnames.ora file is composed by using the following approach:

  1. The file's location should look as follows: <directory_with_extracted_files>/network/admin, the directory_with_extracted_files is checked on Step 1.

    For example, ~/Oracle/instantclient_19_8/network/admin.

  2. The tnsnames.ora file should have the following structure:

    MyTNSAlias =
    (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = db.my.domain.com)(PORT = 1521))
        (CONNECT_DATA =
            (SERVER = DEDICATED)
                (SERVICE_NAME = my_service.my.domain.com)
        )
    )

    Consider the following example of the file:

    # tnsnames.ora Network Configuration File:
     {...}

See also

Related

Reference