Skip to main content
A
Anonymous
September 11, 2011
Answered

Question On How to Install Teradata ODBC on CF9 64-bit?

  • September 11, 2011
  • 1 reply
  • 3693 views

Need to install Teradata drivers on 2 different servers:  A Windows 7 64-bit, and a Windows Server 2008 R2, both running IIS 7.5 and CF 9.0.1 64-bit.  Am fairly sure this needs to be set up as an ODBC Socket in CF Admin.  I've downloaded both the 32 and 64-bit Teradata drivers from Teradata web site (version 13, latest ones).   But have not installed or done anything yet.

First, is it correct with CF9 64-bit, in CF Admin, that the ODBC Socket drop-down will only display 64-bit drivers?  Thus only allowing ODBC connections using 64-bit drivers?   For example, I've been unable to get a 32-bit IBM DB2/UDB ODBC driver to appear in the drop-down.  However, the same 64-bit DB2 driver shows up in the drop-down, but when I test the connection in CF Admin, I get a "type mismatch" error message.  Have not been able to resolve.  Am hoping I don't experience the same issue with Teradata.

On a development Windows 7 server at work, I successfully installed the 32-bit Teradata drivers, but on a Windows 7 32-bit server, and CF9.0.1 32-bit.  After installing and configuring the Teradata 32-bit driver in Control Panel/ODBC Data Sources, the driver DID show up in ODBC Socket drop-down, and tested fine.

But not sure what to do on 64-bit servers, and 64-bit CF9?   If anyone has been able to successfully install and configure a Teradata ODBC-Socket connection on either Win 7 or Windows Server 2008 R2, 64-bit, using CF9 64-bit and IIS, would greatly appreciate any help/advice on what you did to create a successful connection in CF Admin.  Thank you,

Gary

This topic has been closed for replies.
Correct answer

Problem solved.  Finally found out for sure, that CF9 64-bit does not support 64-bit ODBC Socket connections.  You'll get an "architecture mis-match" error when you try to verify the DSN.  But you can create a JDBC connection for Teradata, which I successfully did.   Prior to this, I've never added a JDBC connection, so had to do some research, reading, to find out how this is done.  Actually, it's not too bad once you understand the process.

Keep in mind, when adding a new JDBC DSN, if you don't do it exactly right, and know exactly what you are doing, you could corrupt the file used to start CF Administrator.  That's what happened to me the first time.  I could not start CF Admin, and lost access to all my DSN's, and could not run any .CFM files.

Before making any changes to DSNs in CF Administrator, be sure to back up your "neo-datasource.xml" file in your C:\ColdFusion9\lib folder.  You'll also lose your .BAK copy of this file, if the CF Admin cannot start.  Fortunately, I had a good copy of this file on another computer, and copied it to my workstation, and CF Admin was able to start. 

I was then able to add the JDBC driver, and the DSN verified successfully.  I now have my home-office workstation (CF9 x64 and Win7 x64) in Chicago, able to connect to our Teradata Data Warehouse in Houston, over a VPN connection.  Ran some test queries, and all worked fine. 

Hope this helps anyone else who is trying to do something similar.

Gary

1 reply

A
Anonymous
September 24, 2011

No luck.  After installing Teradata 64-bit ODBC drivers, and successfully configuring them in Windows 7 64-bit, <Control Panel, ODBC Data Sources>, and IIS 7.5, I got the same architechture mis-match when trying to add them as an ODBC-Socket DSN. 

After running into same problem with IBM's UDB/DB2 64-bit drivers, and after reading additional posts, I've come to the conclustion that CF9 64-bit does not support 64-bit drivers in an ODBC-Socket connection.  And if you install/configure 32-bit drivers, they won't appear in CF9's drop-down list of available ODBC-Socket connections.  It appears to only display 64-bit drivers, including the built-in ones (which I believe are mostly JDBC drivers).  If anyone disagrees, please advise.

Yet, on a test server with 32-bit Windows 7 and 32-bit CF9, and 32-bit DB2 and Teradata drivers, everything works fine.  Don't understand why this doesn't work on 64-bit platforms.

At work, we are upgrading our production servers from Win2K 32-bit to Win Server 2008 R2 64-bit.  And upgrading our testing servers at our desks to Win7 64-bit.  And switching the main database from Oracle and SQL Server to Teradata.  (We do have about 4 Oracle DSNs, and 1 SQL Server DSN, and they all work fine using native Oracle/SQL Server drivers that come with CF9 64-bit).  If I can't get the DB2 and Teradata (particularly the Teradata drivers) to work on this new Win Server 2008 R2 64-bit production server, we won't be able to run any of our ColdFusion programs. 

Here are some options I've come up with, and would appreciate advice/recommendations from anyone who may have some experience with this:

OPTIONS:

1.  Un-install CF9 64-bit and and install CF9 32-bit on both Win Server 2008 R2 64-bit and Win 7 64-bit.  Not sure if either of these 64-bit OS will run a 32-bit CF9 installation normally, without problems or errors.  If this is the best way, will all existing Oracle and SQL Server DSNs need to be re-configured, and will those work properly?

2. Run CF9 64-bit in 32-bit mode.  Can this be done?  If so, where do you find out how to do this?  And how does this impact current DSNs using Oracle and SQL Server, that are already configured and running normally? 

3. Leave all "as is" and install Teradata JDBC Drivers.  They are available from their web site.  If this is best solution:

   A. Do you need to un-install the Teradata 64-bit ODBC drivers, or is it OK to just leave them there? 

   B.  I've never installed 64-bit JDBC drivers.  After install, how are these added as a CF DSN? Do they just show up on the main DSN driver drop-down list in CF Admin?  Or do you have to use OTHER?    I've looked at doing a CF "OTHER" configuration, and it asks some questions I don't have the answers to off-hand, and our Teradata DBAs aren't familiar with ColdFusion, so no help there.  So am hoping Teradata will just "show up" as an available driver when adding new DSNs in CF Admin. And I won't need to use OTHER.  Anyone know?

Appreciate any help/advice.  I cannot ask my company to purchase additional licenses of CF9, until I know:


1.  Whether I can get, and how I can get, a Win Server 2008 R2 64-bit server to use CF9 to connect to our Teradata Data Warehouse.

2.  Which version of CF9 to purchase and install on these 64-bit servers (32 or 64 bit)

Really appreciate any help/advice.  Thank you.

Gary

A
Anonymous
Correct answer
October 1, 2011

Problem solved.  Finally found out for sure, that CF9 64-bit does not support 64-bit ODBC Socket connections.  You'll get an "architecture mis-match" error when you try to verify the DSN.  But you can create a JDBC connection for Teradata, which I successfully did.   Prior to this, I've never added a JDBC connection, so had to do some research, reading, to find out how this is done.  Actually, it's not too bad once you understand the process.

Keep in mind, when adding a new JDBC DSN, if you don't do it exactly right, and know exactly what you are doing, you could corrupt the file used to start CF Administrator.  That's what happened to me the first time.  I could not start CF Admin, and lost access to all my DSN's, and could not run any .CFM files.

Before making any changes to DSNs in CF Administrator, be sure to back up your "neo-datasource.xml" file in your C:\ColdFusion9\lib folder.  You'll also lose your .BAK copy of this file, if the CF Admin cannot start.  Fortunately, I had a good copy of this file on another computer, and copied it to my workstation, and CF Admin was able to start. 

I was then able to add the JDBC driver, and the DSN verified successfully.  I now have my home-office workstation (CF9 x64 and Win7 x64) in Chicago, able to connect to our Teradata Data Warehouse in Houston, over a VPN connection.  Ran some test queries, and all worked fine. 

Hope this helps anyone else who is trying to do something similar.

Gary

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices