Download Ibm Informix Odbc Driver 64 Bit
Maggie Schnair
and then launch the setup from the command line and it should go through. The same technique will work for Windows 8 installs, however you have to run the setup in Windows 7 compatibility mode because the Install Anywhere package IBM uses does not work with Windows 8. Here is ashort training video showing me setting up the drivers on Windows 8 (5 minute Flash video).
hello Beautiful people as the topic says i want to install IBM INFORMIX ODBC DRIVER 64 Bits version but i cant find it anywhere i even uninstalled my ibm informix odbc driver package from my pc and re-installed it again to check if i missed something to checkmark at the installation process, but even that i can only install the 32 bit version as the picture shows:
Note: For Solaris and Solaris on SPARC, the 32-bit driver installers work only on 64-bit platforms. Please contact Technical Support if you want to use the driver on the 32-bit platforms.
Until now i have uninstalled and installed the drivers several times with no effect. I've reinstalled Visual Studio. I've also changed some permissions of some registry keys told here ERROR : [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
The CData ODBC drivers include powerful fully-integrated remote access capabilities that makes IBM Informix data accessible from virtually anywhere. The drivers include the CData SQL Gateway, which can the optional ability to accept incoming SQL and MySQL client connections and service standard database requests.
With the CData SQL Gateway, users can interact with IBM Informix data from any client that supports SQL Server or MySQL: from Web & mobile applications, to CRM and CMS systems, BI tools like SQL Server Analysis Services, and even through popular management applications like MySQL Workbench.Access IBM Informix data from virtually any application that can access external data. Applications that can access SQL Server or MySQL data can now connect to IBM Informix with this driver.
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)\.
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.
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.
Add the following to $HOME/.odbc.ini (of the user that the service is running as e.g. /home/sqdr/.odbc.ini). This must exist even if you are using a connection string. Adding it to /etc/odbci.ini does not work.
I'm working with a connection to Informix, having trouble with a DBLink from Toad, I noticed this error (ORA-28500: ORACLE connection to non-Oracle system returned this message: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application IM014), I noticed that the driver is 32 bits (it says 32/64 but doesn't show in ODBC 64bits), I downloaded it from here: but seems that needs the 64 bits driver, because I have another DBLink to Teradata that is working but the driver is 32/64 bits and I configure it in ODBC 64bits.
Now I want to try the Informix connection with 64bits driver (IBM Informix ODBC Connector for 64-bits (for Windows)), but I couldn't find it anywhere, I found this but needs license: -informix so the real support requested is where to find and download IBM Informix ODBC Connector for 64-bits (for Windows), thanks in advance.
Within the ODBC Data Source Administrator software, I can confirm the connection to the database is active with all the configuration options set (server name, host name, service, protocol, database name, user ID, password, environment variables, etc.). However when I attempt to connect Power BI to the database (Get Data -> Other -> ODBC), I'll choose my DSN as the ODBC driver I confirmed to connect within ODBC Data Source Administrator, then use the following connection string:
I haven't found much useful info after googling around for some time, so any help or ideas would be greatly appreciated. I think it might have something to do with needing to specify the path to the actual driver in the connection string? Not entirely sure though...
I try to connect to Informix 11 db using 64bit ODBC driver v 4.50.00.18020. I get data correctly but query folding does not work after any filter applied. If I run diagnostics on the step with simple equal filter like
I can't get an ADO SQLv2 sensor to work with an Informix DB through ODBC on a Windows Server 2012. Tests through Windows odbcad32 work without any errors. The sensor ist setup with default settings and the connection string is a simple "Provider=MSDASQL;Dsn=_name_of_system_dsn;" This triggers the following driver error:
I was able to solve it thanks to your quick answer. I was using the wrong provider (MSDASQL instead of IFXOLEDBC). Additionally, I thought it's be enough to provide only the system DSN name. Turns out, to use IFXOLEDBC you need to set additional parameters in your connection string according to the examples listed here: -informix-ole-db-provider.
df19127ead