This content has been marked as final. Show 2 replies
Having two oracle clients co-exists is tricky on windows, though its fairly convenient on Unix/Linux.
You have to go through what all registry variables the install scripts are going to set.
You had a working Instant Client but after a full Install its gone messy as the full install would have set few registry variables pointing to the full client installation
Even a simple environment variable like PATH and which install's bin is being picked up by the app and if that indeed the right version to pick or not can mess up our lives. If you can set and control all these variables for each of your installations through scripts and remove them from registry then you can have multiple oracle clients on the same box.
According to documentation at [http://docs.oracle.com/cd/E20434_01/doc/win.112/e23174/featConfig.htm]
Configuration File Support
For customers who have numerous applications on a computer that depends on a single version of ODP.NET, the Windows Registry settings for a given version of ODP.NET may not necessarily be applicable for all applications that use that version of ODP.NET. To provide more granular control, ODP.NET Configuration File Support allows developers to specify ODP.NET configuration settings in an application config, web.config, or a machine.config file.
If a computer does not require granular control beyond configuration settings at the ODP.NET version level, there is no need to specify ODP.NET configuration settings through configuration files.
The following is an example of a web.config file for .NET Framework 2.0 and higher:
<?xml version="1.0" encoding="utf-8" ?>
<add name="DllPath" value="C:\oracle\bin"/>
<add name="FetchSize" value="131072"/>
<add name="PromotableTransaction" value="promotable"/>
<add name="StatementCacheSize" value="10"/>
<add name="TraceFileName" value="C:\odpnet2.trc"/>
<add name="TraceLevel" value="63"/>
<add name="TraceOption" value="1"/>