Is it possible to install both the 32-bit Oracle Database thick client and the 64-bit Oracle Database thick client (with Oracle Data Access Components) on the same Windows 7 computer, without the 2 conflicting?
Does this require changing default environment variables, registry settings, and/or install directories?
For example, with both Oracle clients installed, will Windows 7 be confused if MS Office Excel (32-bit) attempts to use Oracle Provider for OLEDB: will it attempt to use the 64-bit provider and fail, instead of using the 32-bit Oracle Provider for OLEDB.
Edited by: 8096367 on Feb 4, 2013 5:15 PM
You should not do this.
Environment variables such as PATH can only give preference to one item of any given name. With DLLs for example the first DLL of any given name that is found will be the one loaded by Windows. It would be up to the software doing the loading to determine if that is the correct version and most software just looks by name.
That is what is known as 'dll hell'; the wrong version of a dll is being used.
You don't need both clients installed so why do you want to do that?
Pl identify which version of Win 7 - you will need Professional or higher. Pl also identify which exact version of Oracle client.
I have no personal experience with this myself, but the 11gR2 docs say you can install both the 32-bit and 64-bit clients as long as you use different ORACLE_BASE directories.
By using different path yes you can install.
Master Note For Oracle Database Client Installation [ID 1157463.1]
Client / Server / Interoperability Support Between Different Oracle Versions [ID 207303.1]
Doesn't this write both ORACLE_HOME paths to the PATH environment variable, and then cause, as mentioned above, DLL hell? With WOW64, it is unclear to me how Microsoft separates 32-bit paths from 64-bit paths.
Unfortunately, my company is running 32-bit Microsoft Office 2007 and other 32-bit programs that use the Oracle thick client install, and my company also uses 64-bit programs that require the Oracle thick client install too.
The solution thus far has been to uninstall one of the programs, and thus clean-up the %PATH% environment variable; or rearrange the order of the Oracle client homes in %PATH% to make the broken one work.