Oracle Instant Client 64-bit

[Vernon]

Ihave not installed it on my system as I require approvals from my workplace. I am also worried that the downloads may be placed in locations that I am not aware of and I would not be able to fix it should I install both versions.

Edit: I have tried using python-oracledb but my login faced the issue of case_sensitive_logon being set to False. To resolve this I would have to use the thick driver which requires instant client based on the documentation I have read, which leads me back to the same problem.

Instant Client ZIP files can be installed into any subdirectory you like. You can install 32-bit and 64-bit into different locations on the same machine. At runtime you will need to set the library search path to the appropriate Instant Client directory for the tool you want to run. For example on Windows you would need to set PATH. On Linux you would need to set LD_LIBRARY_PATH. Often this can be done in a batch or shell script that also invokes your tool or program.

As noted in comments, the latest version of cx_Oracle, now called python-oracledb, doesn't necessarily need Instant Client, so you should/could consider upgrading. See the python-oracledb release announcement.

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 downloaded the instant client 12.1 installed to d:\instantclient_12_1. Changed path and added TNS_ADMIN. I went to DOS prompt and entered in SQLPLUS it worked but TOAD cannot find the oracle home. Thanks in advance for any help. BTW running Windows 8

I have the same issue on a new installation of Toad 13.0.0.80 (64-bit)on a new laptop - is the Instant Client installed as part of the Toad installation.? On the old laptop I have the 64 bit Instant Client installed. My message on the new laptop is no Oracle client found - it is 64-bit Toad for Oracle version.

When I try to connect to Oracle, I experience this error message. Currently I have both of 32 bits and 64 bits OCI installed. How do I make sure Alteryx picks up 64 bits instead of 32 bits? Any settings from Alteryx?

Currently if I use 32 bits OCI, it works.

I just wanted to respond to this post just to put closure to it, even Henriette had helped you resolve the issue. Generally speaking, the issue appears to have stemmed from moving the location of the installation of the Oracle instant client. Alteryx did not know where to find it after that point. Pointing Alteryx to the new location, along with a few other troubleshooting steps, resolved your issue.

Thank you for your post. As this will likely require a closer look at your computer and configurations, please submit a support request to sup...@alteryx.com. A Customer Support Engineer will be more than happy to assist you.

You can also have both versions of the driver running if needed for backwards compatibility. You just need to have you SQL_PATH with both locations separated by a semi-colon. Keep in mind that Alteryx will only read the variables when it opens, so you will need to close designer and re-open to make Alteryx aware of the new location.

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.

Hi,

i've installed PB12.6 trial version, and try to connect with Oracle 64bit instant client v.12.

OS is win10.

Connecting with sqlplus always is ok, but when i try to connect from DB profile in the PB panel, i get the "Oracle library OCI.DLL could not be loaded" error.

If i switch to the Oracle 32bit instant client v.12 (placed in another path and setting the ORACLE_HOME, PATH and TNS_ADMIN environment variable) it works.

So i can't understand if with Powerbuilder 12.6 is possible connecting with 64 bit Oracle client.

Usually you have to install an Oracle client (even today I needed an Oracle ODBC - not for QlikView but for another reason and installed - or rather copy - the Instant client 10 with ODBC - see

).

Anyhow, I would prefer OLEDB for Oracle for QlikView which also needs an Oracle Client, but as far as I remember a "grown up" Client, Instant Client is not sufficient. Usually OLEDB comes with the client, see

for details.

I have had an issue with QlikView and Oracle ODBC (don't remember the versions) where e. g. a value of 200 in the database resulted in 200,0000000001 in QlikView - but only in QlikView. When reading the value via ODBC e.g. by a simple VBScript, the correct value of 200 was returned. Since then I ain't used ODBC for Oracle for QlikView any more (besides, OLEDB should actually be faster and should be the better choice anyhow).

A quick thought - I had a similar issue. None of the oracle ODBCs were showing up for me in th QW client installed in the server. Finally, when I installed Client64 bit insted of the other one, issue got solved.

That's correct, the 64/32 bit problem is also a known issue. AFAIR you need to call odbcad32 if installing a 32 bit ODBC on a 64 bit machine or something like that. Nevertheless I seriously recommend OLEDB.

Even with OLEDB, you need 64-bit Oracle client for QV 64-bit, and 32 for 32. QV doesn't see "wrong" client.

Warning - I was never able to make Publisher 32 to reload from Oracle (neither ODBC nor OLEDB), although QV Developer on the same machine was fine. Didn't have this problem with Publisher 32. Version 8.01 and 8.50. Apprciate if anyone can share positive experience.

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.

In Procedure division:

move "PATH" to EnvName

display EnvName upon environment-name

accept EnvVal from environment-value *> After this statement EnVVal will contain the value of PATH at the runtime

display EnvVal

This has really been extensively tested on our side with no success which is why we've opened a case to see MF's opinion on this, plus posting here to see if someone has managed to put together a recipe for VS2022/VC8/Instant Client that actually works.

It wasn't clear to me from your response if you checked the value of PATH just before the EXEC SQL CONNECT (using the DISPLAY/ACCEPT code above). For certain with the 173 errors, some module in the oracle client is not being resolved or the correct one is not being picked up.

I just set up a Windows 10 VM environment using the same versions of everything as you are, using the Oracle Instant Client 19 for 64-bit and I when I use the set procedure-poiinter method it works and when I use the copy to orasql8.dll method it also works.

Support say they have this working and you have this working. This tells me were doing something wrong but since there isn't any official documentation from Micro Focus about how to set up Visual Cobol and Pro*Cobol using Instant Client on Windows there is nothing to compare to. This is my biggest complaint about the entire experience, trying to find forum posts and old knowledge base articles that discuss parts of the solution and often with much older versions of the products.

I have no idea how many VC users are using Pro*cobol and at the same time looking at using the latest versions. Perhaps you should just stay on something old that works. Again, the lack of documentation is probably an indication of the number of users.

3a8082e126