Hi,
We are currently using ODAC version 9.1.4 and thinking to upgrade it to a newer version. However, when I upgraded it to the version 9.3.10 or above and was connecting to a database with Oracle instant client, I got the error message "Invalid Home Name:". Since we used to connect successfully by setting the home name to empty when connecting with Oracle instant client with its path in the environment variable "PATH", what should I change in order to connect with instant client?
Thanks,
Cliff
connect with instant client
Re: connect with instant client
Hello,
We have already fixed the problem. The fix will be included in the next version. Currently, you should specify the Oracle client data in the registry: http://blog.devart.com/how-to-configure ... lient.html .
We have already fixed the problem. The fix will be included in the next version. Currently, you should specify the Oracle client data in the registry: http://blog.devart.com/how-to-configure ... lient.html .
-
cliffchan512
- Posts: 20
- Joined: Fri 01 Jun 2012 11:34
Re: connect with instant client
Hi,
We have tried a newer ODAC version 9.5.16 and confirmed that the issue of instant client without home specified is fixed, however we encountered another issue that there was runtime error 216 when application close with oracle connection established. This issue doesn't exist in version 9.1.4 (we are currently using) or 9.4.14 (we tried but there is instant client's issue), then we debugged and see that somehow it may relate to release of TOracleHome in callstack.
We go further and found that if we put a sentence of code OracleSession.Home.Release after OracleSession.Disconnect before the session is free, the runtime error was gone. Please advice.
Thanks,
Cliff
We have tried a newer ODAC version 9.5.16 and confirmed that the issue of instant client without home specified is fixed, however we encountered another issue that there was runtime error 216 when application close with oracle connection established. This issue doesn't exist in version 9.1.4 (we are currently using) or 9.4.14 (we tried but there is instant client's issue), then we debugged and see that somehow it may relate to release of TOracleHome in callstack.
We go further and found that if we put a sentence of code OracleSession.Home.Release after OracleSession.Disconnect before the session is free, the runtime error was gone. Please advice.
Thanks,
Cliff
Re: connect with instant client
Hello
We cannot reproduce this issue with a simple application that contains TOraSession only. Can you send us a simple sample application reproducing this issue at alexp[dog]devart[dot]com?
In addition, please specify whether you are get the "run-time error 216" with standard Oracle client, instant Oracle client or in both cases.
We cannot reproduce this issue with a simple application that contains TOraSession only. Can you send us a simple sample application reproducing this issue at alexp[dog]devart[dot]com?
In addition, please specify whether you are get the "run-time error 216" with standard Oracle client, instant Oracle client or in both cases.
-
cliffchan512
- Posts: 20
- Joined: Fri 01 Jun 2012 11:34
Re: connect with instant client
Hello,
This issue happens no matter the oracle client is installed or instant, however I cannot reproduce it on another machine. Any idea?
This issue happens no matter the oracle client is installed or instant, however I cannot reproduce it on another machine. Any idea?
Re: connect with instant client
Hello,
This may be caused by that you have installed and configured several Oracle clients on your machine. Please specify the number, versions and type (Instant/Installed) of Oracle clients. Also provide their settings in the registry, environmental variables, etc.
This may be caused by that you have installed and configured several Oracle clients on your machine. Please specify the number, versions and type (Instant/Installed) of Oracle clients. Also provide their settings in the registry, environmental variables, etc.