Instant Client ODBC requires the Oracle Instant Client Basic or Basic Light package (depending on your locale requirements) also be installed. Download the desired package from OTN for your operating system and follow the installation instructions on the download page. For example, unzip the package to C:\instantclient_19_3 on Windows, unzip to /opt/oracle/instantclient_19_3 on Linux or other platforms, or use yum to install the RPM packages on Linux.
1) A lot of the suggestions have involved putting the ip address of the Oracle server in the connection string to bypass the tnsnames.ora file. Unfortunately the app has to work with a user set oracle connection, so we don't have any of that information. All i have to work with is a DSN. I have to make it connect from a windows service using an Oracle DSN.
OK, I'm going to answer my own question here just to keep the final resolution separate from the helpful suggestions that led me to it. The post referenced by Nicola )once I read it carefully) turned out to have the answer. My service was running from Program Files(x86) and the oracle driver can NOT handle ( ) in the path of the calling app.
I moved my service to D:\ServiceTest and it works fine.My problem now is that I don't think our app can be moved out of Program Files (x86).
Thank you all for your help, I appreciate everyone's input but I will have to give the bounty to Nicola, as he pointed me to the post that contained the answer.Thanks again for all your help
Anyway, both downloaded files, you need to unzip to THE SAME folder (for example: c:\oracle\instant_client_11), then add the folder to the PATH environment variable:
Then add the TNS_ADMIN environment variable indicating the path to the tnsnames.ora file (in my PC it is c:\oracle\11.2.0\CLIENT\network\admin):
Next, open the command line (Run as administrator) and go to the folder where you unzip ODBC driver, in my case:
If you are having trouble working through this guide, please read the following guide: -on-windows.html%23 . And if you are specifically looking for a wire protocol supporting oracle driver, here it is: -database
Am I understanding your problem correctly - when you installed oracle, you entered
different passwords for SYS and SYSTEM and now can't get it to work because it wants
you to use "manager" for SYSTEM password? If this is correct, I may have a solution
because I ran into the same thing last night.
Another annoying Doh moment!
The little "i" in ADF/ Edit Linked Service/ Secret Name, gives the the format for the oracle connection string using the obsolete "sSid=" instead of "servicename=". (I have not used SIDs for > 10 years.)
I am new to Azure and ADF and struggle to find the detail I need in "Learn More" .
Now, the issue ... when we run a script, we get this error "ERROR: Unable to load oracle client (oci.dll)
ERROR: A Connection to the oracle DBMS is not currently supported, or is not installed at your site.".