By default, 64 bit Windows versions use a 64 bit ODBC Administrator utility. How do I install a 32 bit version of ODBC to work with IBM Informix Dynamic Server, when I am using a 64 bit Windows version? ![]() Last modified: May 15, 2018 Informix Client SDK and Informix Connect run on most systems that have a UNIX, Linux, or Windows operating system and, starting with version 3.5, also on the Mac OS X operating system. System requirements are listed by operating system (OS). In this document: • • • • • • • • • • • For more information about the system requirements for each client API, see the following machine notes: • • Platform: AIX Hardware: IBM POWER (System p, System i, POWER Blades) Note: These codes are used in the following table: F = 64-bit U = 32-bit. Operating System Version Client SDK/Informix Connect 4.10 Client SDK/Informix Connect 3.70 RHEL 7 4.10.FC10 Additional OS requirements: - Base kernel version 3.10.0 - Glibc version 2.17 - Compiler 4.8.3 SuSE SLES 12 4.10.FC10 Additional OS requirements: - Base kernel version 3.12.28 - Glibc version 2.19 - Compiler 4.8.3 Ubuntu 14.04 4.10.FC10 Additional OS requirements: - Base kernel version 3.16.0 - Glibc version 2.19 - Compiler 4.8.4 Platform: Linux - IBM System z Hardware: System z Note: This code is used in the following table: U = 32-bit F = 64-bit. Operating System Version Client SDK/Informix Connect 4.10 Client SDK/Informix Connect 3.70 Windows 10 4.10.FC11 Windows 8 4.10.TC11 4.10.FC11 Windows 7 4.10.TC11 4.10.FC11 3.70.TC9 3.70.FC9 Windows Vista 4.10.TC8 4.10.FC8 3.70.TC8 3.70.FC8 Windows XP 4.10.TC5 4.10.FC5 3.70.TC8 3.70.FC8 Windows 2016 4.10.TC11 4.10.FC11 Windows 2012 R2 4.10.TC11 4.10.FC11 Windows 2012 4.10.TC11 4.10.FC11 Windows 2008 R2 (64-bit) 4.10.TC11 4.10.FC11 3.70.TC9 3.70.FC9 Windows 2008 4.10.TC9 4.10.FC9 3.70.TC9 3.70.FC9 Windows 2003 4.10.TC5 4.10.FC5 3.70.TC9 3.70.FC9 Related information. Currently trying to setup a development environment which can handle both 32-bit and 64-bit ODBC Informix Drivers. I'm was unsuccessful at finding any sort of guide or walk through online, however I did find bits and pieces which could lead to the solution. I'd just like a little more advice to ensure I'm on the correct path. Driver Versions Version 3.70.TC3, Windows (32 bit) Version 3.70.FC3, Windows x64 I can't seem to find versions 3.70.TC3 or 3.70.FC3, but I did find and directly from the IBM website, which I assume are just slightly updated versions. Informix Driver Installations The drivers are installed at the following locations (based on the registry entries) • 32-bit: C: Program Files (x86) IBM Informix Client-SDK • 64-bit: C: Program Files IBM Informix Client-SDK Registry Entries From what I can see, the registry entries for the drivers are located at: • 32-bit: HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node ODBC ODBC.INI • 64-bit: HKEY_LOCAL_MACHINE SOFTWARE ODBC ODBC.INI This essentially lists all of the data sources and their connection details. Both locations have the same number of data sources with the same names and same key/value pairs, with the exception of the Driver key which points to it's respective driver location; C: Program Files or C: Program Files (x86). ODBC Administrator The 32-bit ODBC Administrator is found at%systemdrive%/Windows/ SysWoW64/odbcad32.exe Counterintuitively, the 64-bit ODBC Administrator is found at%systemdrive%/Windows/ System32/odbcad32.exe ODBC.INI The ODBC.INI file is located at C: Windows where the contents of that file lists the same data sources as those displayed in ODBC Administrator, and includes the key/value pair of the 32-bit drivers for each of those data sources; Driver32=C: Program Files IBM Informix Client-SDK bin iclit09b.dll. Now what's interesting here is that although the key Driver32 is used, the value points to the C: Program Files path as opposed to the C: Program Files (x86) path, thereby associating the Driver32 to the 64-bit drivers. I found the following to explain this irregularity. The WOW64 registry redirector intercepts calls made to certain portions of the registry and redirects them to another portion of the registry. Registry redirection affects the HKEY_LOCAL_MACHINE SOFTWARE key. Registry calls made to this key by 32-bit applications are redirected to HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node. So, for example, when a 32-bit application calls SQLDataSources, the resultant registry call is redirected from HKEY_LOCAL_MACHINE SOFTWARE ODBC ODBC.INI to HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node ODBC ODBC.INI, and the only system data sources that are returned are ones for 32-bit ODBC drivers. Simply put, a 32-bit application which connects to the 64-bit ODBC drivers will automatically be redirected to the 32-bit drivers based on the registry entries, whereas a 64-bit application will need no such redirection. If a 32-bit application attempts to connect to a valid user data source for a 64-bit ODBC driver, the connection will succeed if a 32-bit version of the driver is installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2018
Categories |