Thursday, February 13 2014
Keywords: Oracle, ODBC Driver Name Change, 32 bit, ODAC, Windows Registry, Distributed, Scaled Out Enterprise Apps
Change Oracle ODBC Driver Names In Windows Registry If So Required By Your Scaled Out Application
We have an application at the company that could optionally be scaled out across many machines...its configuration settings however will remain centralized while scaled out.
The application can talk to a SQL or Oracle server using ODBC. And it requires you to enter the "ODBC Driver Name" it will use in its configuration settings.
Yesterday we needed to scale out this application over four machines. The application was to connect to an Oracle database server, using 32 bit Oracle ODBC driver. However we hit a problem...in a couple of machines there were existing installations of Oracle ODBC drivers...but WITH SLIGHTLY DIFFERENT NAMES. That obviously caused a problem for this application since as you remember...the configuration settings were centralized...thus requiring that the ODBC driver names be identical across all machines.
Uninstalling and Re-installing the drivers were not good options for us at the moment...nor did we have any time for that.
There is an easy 2 minutes solution for this problem: Modify the Oracle ODBC Driver name in windows registry. And in our particular case 32 bit ODBC Driver Name.
In my particular workstation this registry key could be found at:
In the above-mentioned path, I find two things:
1) A key called "Oracle in OraClient11g_home1_32bit"
2) A sub-folder called the same.
Both of these need to be renamed to match the name your application requires.
Written by Montreal DBA Team