Informix 32 Bit Odbc Download

1. Ibm Informix 32 Bit Odbc Driver Download
2. Informix Odbc Driver Windows 7 32 Bit Download

1. If you are installing the 32 bit version onto a 64 bit OS you might need to prepend the SysWOW64 path temporarily to your%PATH% variable or the install may bark at you. To do this open a comand prompt - be sure to run 'as administrator', go to the folder where the Informix SDK install is at and type: set PATH=C: WINDOWS SysWOW64;%PATH%.
2. Informix Driver Installations The drivers are installed at the following locations based on the registry entries bit: Simply put, a bit application which connects to obdc bit ODBC drivers will automatically be redirected to the bit drivers based on the registry entries, whereas a bit application will need no such redirection.

The IBM Informix 32 bit ODBC option will not be visible when using this utility. Answer In order to use a 32 bit ODBC driver on a 64 bit Windows machine, it has to be configured using a 32 bit ODBC Administrator which is not visible through normal Windows menu options. Progress DataDirect’s ODBC Driver for IBM Informix offers a high-performing, secure and reliable connectivity solution for ODBC applications to access IBM Informix data. Our ODBC driver can be easily used with all versions of SQL and across all platforms - Unix / Linux, AIX, Solaris, Windows and HP-UX. Download trial version of ODBC IBM Informix Connector for Windows 32-bit and test a unique data connectivity solution used by enterprises worldwide. Download trial version of ODBC IBM Informix Connector for Windows 32-bit and test a unique data connectivity solution used by enterprises worldwide. Download iclit09b.dll IBM Informix ODBC Driver version 3.70.0.14669 32bit.

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 3.70.TC7 and 3.70.FC7 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)IBMInformixClient-SDK
• 64-bit: C:Program FilesIBMInformixClient-SDK

Registry Entries

From what I can see, the registry entries for the drivers are located at:

• 32-bit: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.INI
• 64-bit: HKEY_LOCAL_MACHINESOFTWAREODBCODBC.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 FilesIBMInformixClient-SDKbiniclit09b.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 page 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_MACHINESOFTWARE key. Registry calls made to this key by 32-bit applications are redirected to HKEY_LOCAL_MACHINESOFTWAREWow6432Node. So, for example, when a 32-bit application calls SQLDataSources, the resultant registry call is redirected from HKEY_LOCAL_MACHINESOFTWAREODBCODBC.INI to HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBC.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. Otherwise, the connection will fail with the 'architecture mismatch' error. For example, Microsoft’s SQL Server ODBC driver installs both a 64-bit library (%WINDIR%System32sqlsrv32.dll) and a 32-bit library (%WINDIR%SysWOW64sqlsrv32.dll) on 64-bit Windows platforms.

In the case of Informix, the driver for each architecture MUST be installed separately.

Questions

What is the importance of the ODBC.INI file, and can I simply modify the Driver32 key to Driver64 or maybe have both in conjunction?

When executing the 32-bit ODBC Administrator and opening a data source I am able to modify the connection settings, however when executing the 64-bit version I receive the following error.

How can I change the system's current ODBC Administrator to the 64-bit version in order to avoid this error?

1 Answer

The issue was that I had installed the 3.50 version initially. This version is no longer supported and also does not have a 64-bit counterpart.

The resolution was to install the latest 4.1 drivers.

Not the answer you're looking for? Browse other questions tagged driversodbcinformix or ask your own question.

I am trying to create a linked table in a 64-bit SQL Server to Informix, and the SQL server does not list Informix ODBC in the DSN list. I have downloaded the 64-bit Informix Client SDK, however, despite the fact that it states 64-bit Informix Client SDK, it only appears in the 32-bit ODBC DSN. I tried to create a linked table in a 32-bit SQL Server and I was then able to see Informix ODBC DDN.

I was just wondering that if there is an Informix Client SDK that would show in the 64-ODBC DSN, not the 32-bit?

Also is there a way of linking a 64-bit SQL Server to Informix please?Thanks.

TallTed

4 Answers

Create a DB Link in SQL Server to Informix

I used the following Software environment:

• SQL Server 2012
• Informix SDK 4.10 FC2
• Informix 11.5

First Set some Properties for Ifxoledbc Driver:

Then Create Linked Server:

General Settings - Datasource is your DB and your Server Name

Security Settings - Add valid Informix Database Credentials

Server Options - Set RPC and RPC Out to True

I use the db link for calling a stored Procedure in Informix and writing the data to SQL Server.

Did you use the 64 bit version of ODBCAD32.EXE to create the DSN?

There are two versions of the ODBC administrator.

This one is the 32 bit version:

Ibm Informix 32 Bit Odbc Driver Download

It can only see 32 bit drivers, and only 32 bit processes can see it's DSN's

This one is the 64 bit version:

It can only see 64 bit drivers, and only 64 bit processes (i.e. SQL Server 64 bit) can see it's DSN's

Even better you could define a DNS-less connection which doesn't use a DSN, it uses the driver directly. Then you can avoid this confusing step altogether.

Nick.McDermaidNick.McDermaid

I would have used the Comment feature, but I do not have enough 'Reputation Points' to do so.

The answer of SGeis, above, is on the money. It was hard for me to find such a clear, straightforward answer. Snapshots of the dialog boxes help immensely.

Let me add to his answer the following:

1. The Data Source fill-in (YourDatabaseName@YourInformixServerName) could be something as simple as Fred@Barney, rather than what I tried, namely, Fred@199.188.77.66 or Fred@199.188.77.66:32002 (the latter specifies a port/service number).

2. Once you create the linked server, if you go back into its General properties page, you will see that you cannot edit what you typed for Linked Server, Product Name (Why isn't this called 'Provider Name,' since Ifxoledbc is listed under Linked Servers/Providers in the Object Explorer tree?), Data Source, etc. So, if your connection fails because you mistyped something, it is unclear how to fix it.

Here is what you may do:

1. Right-click the linked server.

2. Beneath 'Test Connection,' look for 'Script Linked Server as.'

3. Click the latter, and, then, each of the following: 'DROP And CREATE To'and 'New Query Editor Window.'

4. In the script text that appears, type replacement info for those settings that were grayed-out and uneditable.

5. Press F5 to run the script and thereby apply your changes. In doing so, the existing linked server is dropped, and a new one is created.

6. Open up your linked server's Security properties page and re-enter any connection password (even though asterisks -- suggesting that the password is filled and correct -- may appear in the corresponding entry). Also, examine the General properties page. Make sure that your changes stuck. Even though you ran the script and received no error, SQL Server will blank out fill-ins such as 'Linked Server,' 'Product Name,' and 'Data Source' if, for example, you, as I did, had a brain aneurism and chose the wrong drop-down item for 'Provider.'

7. As noted above, click 'Test Connection,' to verify that your changes work.

   Automatically recognizes and selects the best compression method. Download free version of winrar. The special compression algorithm compresses multimedia files, executables and object libraries particularly well. It is ideal for multimedia files. Allows you to split archives into separate volumes easily, making it possible to save them on several disks for example.

I was able to set up a linked server without Ifxoledbc. Once my System DSN for the 64-bit ODBC driver was set up (and tested OK), I set up a linked server using the Microsoft OLE DB Provider for ODBC Drivers.

Linked Server: UCCX
Provider: Microsoft OLE DB Provider for ODBC Drivers
Product name: IBM Informix ODBC Driver (probably could be anything but I named it the same as the ODBC Driver and it worked).
Data Source: UCCX (the name of your System DSN).

Informix Odbc Driver Windows 7 32 Bit Download

On the security tab I mapped a local login to the same remote user/password as the one set up in the System DSN itself.

And another way to consume the System DSN is via OPENROWSET. This works even without setting up a linked server:

Not the answer you're looking for? Browse other questions tagged sql-serverinformix or ask your own question.