Instant Client Oracle 64 Bit

[Erwin Beatz]

OracleInstant Client enables development and deployment of applications that connect to Oracle Database, either on-premise or in the Cloud. The Instant Client libraries provide the necessary network connectivity and advanced data features to make full use of Oracle Database. The libraries are used by the Oracle APIs of popular languages and environments including Python, Node.js, Go, PHP and Ruby, as well as providing access for Oracle Call Interface (OCI), Oracle C++ Call Interface (OCCI), JDBC OCI, ODBC and Pro*C applications. Tools included in Instant Client, such as SQL*Plus, SQL*Loader and Oracle Data Pump, provide quick and convenient data access.

Instant Client RPM packages for Oracle Linux can now be installed from yum.oracle.com for Oracle Linux 8 and Oracle Linux 7. Older releases are available for Oracle Linux 9, Oracle Linux 8, Oracle Linux 7 and Oracle Linux 6.

Whether your applications are in the cloud or on-premise, you can install Instant Client and connect to cloud databases. Follow the normal installation process for your operating system. Some cloud-specific references are shown below.

DigiCert retired the Organizational Unit (OU) field for all public TLS/SSLcertificates to comply with industry standards as of August 2022. This meansthat public TLS/SSL certificates issued by DigiCert will no longer have an OUfield. Refer to MOS note 2911553.1for details.

To avoid disruption to applications connecting to Oracle Autonomous Database onShared Exadata Infrastructure (ADB-S) during the server side certificatechange, you must use hostname based matching of the server certificate.

The following versions of Oracle Instant Client automatically support hostnamebased matching:

Versions: 18.19 (or later), 19.2 (or later), 21 (base release or later), 23.4 (or later)

Oracle Call Interface (OCI), Oracle C++ Call Interface (OCCI) or ODBCapplications must use one of the above client versions.Oracle Database drivers based on Oracle Instant Client or Oracle DatabaseClient (e.g ODPI-C, python-oracledb Thick mode, cx_Oracle, node-oracledb Thick mode,godror, PHP OCI8, PHP PDO_OCI, ruby-oci8, ROracle, and rust-oracle) must usethe driver with a compatible client version from the list above.An additional step is required if you have changed the ADB-S connection string.

ADB-S connection strings contain a hostname "...(HOST=xyz)..." which depends onthe region. For example, in the Chicago region the hostname would be"adb.us-chicago-1.oraclecloud.com". If you have replaced the default hostnamewith an IP address or a custom hostname, then hostname based DN matching willfail. The solution is to add a new entry to your /etc/hosts file using theoriginal ADB-S domain suffix. Your connection string should then use this newname. For example an entry "localtunnel.adb.us-chicago-1.oraclecloud.com"could be created and used.

My configuration works fine on the old version of SQL developer, but in the new version I receive an error when testing the oracle client. My client type is set to Instant Client. See attached. I tried both the old and new instant client as well. Again, the new instant client works fine with the old version of SQL developer, but I get the same error with the new SQL developer and new instant client. Need some help. I am a little stuck right now.

My understanding is this just needs a TNS_ADMIN environment variable pointing to location of tnsnames.ora and sqlnet.ora files set up along with install folder of instant client in PATH to communicate with remote oracle databases

oracle-xe is the name of the docker container running my database (from official repo as well).

First I have to say that when I install ping to the docker client container, I can ping oracle-xe. Also I can connect to the database using sql developer from my windows. And from the oracle client docker container if I use this command line it works :

sqlplus userName/password@oracle-xe/XE

My problem is only when trying to connect using the tnsnames.ora inside the oracle client container.

Here is my command line to run the client : docker run -ti --network=sai --rm oracle-instantclient bash

when I run sqlplus (without parameters) and after entering username/password I got this message :

ORA-12162: TNS:net service name is incorrectly specified

then if I set the ORACLE_SID variable (which shouldn't be needed since it's defined in the tnsnames.ora) I got this other error :

ORA-12545: Connect failed because target host or object does not exist

I wanted to try tnsping but it's not included in the oracle instant client and I didn't know where to find it. I tried using the one installed in the oracle database container but it's not working.

I hope someone can help me solve this issue

For our Oracle connections I use the instant client. This unzips to a directory of your choosing. I then add a reference to that directory in the PATH system environment variable. You will probably have to reboot for the path variable to be added. (or add it manually...)

I just want to have GIS Server connections work in ArcGIS Pro regardless of what project I'm in... I'd really prefer for things to just work without having to customize the app / add add-ins but alas that's apparently not a thing

The link that you have provided, is for Oracle Instant Client....which doesn't have any standard setup.exe. As Tom mentioned, its a zip file which can be extracted to any location of your choosing and the path added to "Environment Variable" for using it.

Asrujit, I downloaded the Instant Client Basic V 12.1.0.2.0. Would this be the correct client? I just read in the ArcGIS Pro help that you can download the Oracle Instant Client from My Esri but I was unable to find it on an Esri site so defaulted to the Oracle site. Thank you for your help.

I have an old 32-bit software program that connects to an Oracle database but only works with the Microsoft ODBC driver for Oracle. It does not work with the more up-to-date native Oracle ODBC driver.

For clarification, the C:\oracle\instantclient32_12_1 directory I specified contains files like oci.dll and ociw32.dll and belonged to the 32-bit Instant Client install. I guess it doesn't matter for 64-bit, since there is no Microsoft ODBC 64-bit client.

The Oracle Instant Client is a light-weight, freely distributable implementation of an Oracle client. A big advantage of the Instant Client is it does not need a formal installation. Instead, it can be unzipped and used without any fuss.

Since September 2018 the instant client RPMs have been freely available on yum.oracle.com. If you are using Oracle Linux and have root access you can install the instant client using Yum with a few simple commands.

There are a number of downloads available, depending on which features you require. The Linux versions also come with an RPM option, but as this requires root privilege to install, it may not be considered so desirable. The basic download provides all the core functionality necessary to make basic connections from Java. In this case, I wanted to make SQL*Plus connections, so I downloaded the following zip files.

When using the Instant Client, we need to make sure the LD_LIBRARY_PATH environment variable is set to point to the location where the software was unzipped. In this case, I also set the PATH environment variable.

If you would prefer to use a "tnsnames.ora" file, you can do that too. Just set the TNS_ADMIN environment variable to the directory holding the file and it will work as expected. For example, imagine I had a "tnsnames.ora" file in my home directory with the following contents.

p2sora7.dll (version 8.6.1.50) seems to be the dll which was used by legacy Crystal Reports designer tool, whereas deployment with Windows 7 and other software components seem to be relatively newer versions. I doubt a version incompatibility issue here.

Hard to say.However, as Prathamesh mentioned, the p2sora.dll was last used in CR 8.5 and WIN7 was not even a concept at that time (1999 (?)). E.g.; CR 8.5 is not supported on WIN 7. Only way for you to find out if full Oracle client will make this work is to install it.

Crystal Reports 8.5 used the PATH statement to find the various DB clients, If Oracles instant Client install doesn't put the location of OCI*.dll in the PATH CR won't be able to find it and it will never work, not that we ever support the instant client in 8.5 anyways.

Quick aside, the normal way we have this configured in the current setup of VS 2019, VC 7, instant client 19 32-bit is to make a copy of the file orasql19.dll as orasql8.dll this enabled things to work without the need of any extra configuration. Even though the normal recommendation is using a procedure pointer or the initcall directive.

Moving to client 19.18 but 64-bit the results are a bit different. At connect we get SQLCODE -1 which should be unique constraint violated, but when running the tests with connection trace activated we can see that no attempt to connect to the remote server is made. The error is internal to the client. A clue is in the error message which is "ORA-00001: unique constraint (%s.%s) violated" i.e an incomplete error message

I'm unable to come up with any additional test and will submit at much wordier entry as a support case. But I cannot help to be curious about if anyone else has tried this and found a workable solution.

Someone at MF really should write a white paper about how to configure visual cobol and pro*cobol/instant client ON WINDOWS since today the information is spread out in different forum posts and knowledge base articles. With a lot of it being quite old or for unix/linux. Not the most fun of subjects but one that needs some love and a document that is current.

3a8082e126