oracle probe connection error Create OCI environment failed or OCIEnvCreate failed with rc = -1
search cancel

oracle probe connection error Create OCI environment failed or OCIEnvCreate failed with rc = -1


Article ID: 34400


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)


If testing a connection in the oracle probe is failing with an error message such as: "Create OCI environment failed with rc = -1" or "OCIEnvCreate failed with rc = -1" follow the instructions below.

OCIEnvCreate returning -1 almost always indicates that the probe cannot find the oracle client (or doesn't have read/execute permissions).


  • Any UIM Version
  • Any Oracle probe version


Check the oracle probe Release Notes to see which Oracle clients are currently supported and requirements.

The first piece of information you should collect is whether the oracle_monitor probe is deployed on the same machine where the database is installed or on a different machine. If the probe is installed on a different machine then verify which 'Oracle Client' version is installed on that machine locally, and check the OS version for that server and whether the OS is 32 or 64-bit.

If customer is using zones ensure that the client and server are on the same zone even when they are on the same server.

The Release Notes for the Oracle probe contain a matrix listing the different combinations of Server and Client versions that are officially supported by the oracle probe. If you have any other version of the Oracle Client other than what is supported with your Server version then please update it to one that is officially supported.

The oracle probe requires that the Oracle client 'match' the OS (32-bit versus 64-bit) and Oracle DB server version. If you have a 64-bit OS you are running the probe on. then the Oracle client must be 64-bit as well.

Also, you will need to double-check the items below after logging in with the oracle user (you must be logged in as the oracle user instead of root)

1. Re-verify that the following variables are set on the machine where the Oracle database is installed.

   d. PATH (should include the Oracle bin directory.)

NOTE: AIX OS REQUIRES the LIBPATH as well. Please see the latest release notes.