Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-154

Install EXASolution ODBC driver on AIX, HP-UX, Linux, MacOS, Solaris (Version 4.2)

    Details

    • Type: How To
    • Status: Obsolete
    • Affects Version/s: EXASolution 4.2.0
    • Fix Version/s: None
    • Component/s: ODBC
    • Labels:
      None
    • Solution:
      Hide

      If you have no special requirement for an EXASolution 4.2 ODBC driver, please use EXASolution 5.0 ODBC driver as described in SOL-153. It is downward compatible and the configuration program is more convinient.

      Overview

      The correct configuration of ODBC on non-Windows systems is inherently complex due to the number of components and required workarounds. The EXASolution ODBC driver package provides a program to do the hard work for you.

      Installation

      Download the EXASolution ODBC driver package for your system.
      Always unpack on the target system.

      Linux (all distributions)
      tar -xzf EXASolution_ODBC-4.2.*-Linux.tar.gz
      
      Solaris 10 and Solaris 11
      gtar -xzf EXASolution_ODBC-4.2.*-Solaris_10.tar.gz
      
      Mac OS X 10.7 and Max OS X 10.8
      tar -xzf EXASolution_ODBC-4.2.*-MacOS_10.7.tar.gz
      
      HP-UX 11.31
      uncompress -c EXASolution_ODBC-4.2.*-HPUX_11.31_IA64.tar.Z | tar -xf -
      
      AIX 5.3
      uncompress -c EXASolution_ODBC-4.2.*-AIX_5.3.tar.Z | tar -xf -
      
      AIX 6.1 and AIX 7.1
      uncompress -c EXASolution_ODBC-4.2.*-AIX_6.1.tar.Z | tar -xf -
      

      It's not important where the package is unpacked, but after configuration (next step) the install directory can not be changed without reconfiguration.

      Required packages

      Have a look at the included README file for the list of required packages. This applies only to AIX.

      Configuration

      Change into the install directory and start the configuration program:

      cd  EXASolution_ODBC-*
      ./config_odbc --host=10.0.0.1 --port=1234 --user=doe --password=test --odbcini=odbc.ini
      

      None of the options are mandatory, but usually required. Have a look at the defaults and other options with

      ./config_odbc --help
      

      The program performs the following steps:

      • Scan the system for available ODBC driver managers
      • Create an odbc.ini config file
      • Create a wrapper script to start applications
      • Test database connectivity

      Running Programs

      What is the correct DSN?

      config_odbc can guess the correct DSN for an application if that application has loaded the ODBC data manager (but not the ODBC driver).

      Just start your application and load the driver manager:

      • GUI applications: open the data source configuration dialog (or similar)
      • Scripting languages: import the ODBC module

      Then run config_odbc again in guessing mode:

      Example: Python
      python -c 'import time, pyodbc; sleep(10)' &
      ./config_odbc --mode=guess
      
      Example: Perl
      perl -e 'use DBI; DBI->data_sources("ODBC", \%attr); sleep 10' &
      ./config_odbc --mode=guess
      

      How to set the environment

      In almost all cases it is required that several environment variables are set, and sometimes compatibility soft links are necessary. To simplify this task, config_odbc generates a wrapper script for each DSN to start applications:

      ./drivers/DSN/exec MyApp with some args
      

      "DSN" has to be replaced by the correct DSN for this application.

      Troubleshooting

      config_odbc does not start

      Some operating system have no or only a crippled Perl installation. Install a full Perl system and try again.

      Fix: minimal Debian
      apt-get install perl
      
      Fix: minimal CentOS 7
      yum install perl-Digest-MD5
      

      Configuration went well but applications can not connect

      Make sure EXASolution is reachable and the ODBC driver manager / ODBC driver combination works in principle. Use the test scripts in the drivers directory (the second part of the path must be a valid DSN) for this purpose:

      Example: connection testing
      ./drivers/exasolution_uo2214lv2_64/test
      

      Everything else

      Please call EXASOL support and don't forget to provide the file config_odbc.log.

      Even if you want to use EXASolution 4.2 ODBC driver for production, try EXASolution 5.0 ODBC driver as described in SOL-153. The diagnostic capabilities of 5.0's config_odbc are superior and therefore it's easier to pinpoint the cause of trouble. Attach the file support.tar generated by 5.0's config_odbc to the support call.

      Show
      If you have no special requirement for an EXASolution 4.2 ODBC driver, please use EXASolution 5.0 ODBC driver as described in SOL-153 . It is downward compatible and the configuration program is more convinient. Overview The correct configuration of ODBC on non-Windows systems is inherently complex due to the number of components and required workarounds. The EXASolution ODBC driver package provides a program to do the hard work for you. Installation Download the EXASolution ODBC driver package for your system. Always unpack on the target system. Linux (all distributions) tar -xzf EXASolution_ODBC-4.2.*-Linux.tar.gz Solaris 10 and Solaris 11 gtar -xzf EXASolution_ODBC-4.2.*-Solaris_10.tar.gz Mac OS X 10.7 and Max OS X 10.8 tar -xzf EXASolution_ODBC-4.2.*-MacOS_10.7.tar.gz HP-UX 11.31 uncompress -c EXASolution_ODBC-4.2.*-HPUX_11.31_IA64.tar.Z | tar -xf - AIX 5.3 uncompress -c EXASolution_ODBC-4.2.*-AIX_5.3.tar.Z | tar -xf - AIX 6.1 and AIX 7.1 uncompress -c EXASolution_ODBC-4.2.*-AIX_6.1.tar.Z | tar -xf - It's not important where the package is unpacked, but after configuration (next step) the install directory can not be changed without reconfiguration. Required packages Have a look at the included README file for the list of required packages. This applies only to AIX. Configuration Change into the install directory and start the configuration program: cd EXASolution_ODBC-* ./config_odbc --host=10.0.0.1 --port=1234 --user=doe --password=test --odbcini=odbc.ini None of the options are mandatory, but usually required. Have a look at the defaults and other options with ./config_odbc --help The program performs the following steps: Scan the system for available ODBC driver managers Create an odbc.ini config file Create a wrapper script to start applications Test database connectivity Running Programs What is the correct DSN? config_odbc can guess the correct DSN for an application if that application has loaded the ODBC data manager (but not the ODBC driver). Just start your application and load the driver manager: GUI applications: open the data source configuration dialog (or similar) Scripting languages: import the ODBC module Then run config_odbc again in guessing mode: Example: Python python -c ' import time, pyodbc; sleep(10)' & ./config_odbc --mode=guess Example: Perl perl -e 'use DBI; DBI->data_sources( "ODBC" , \%attr); sleep 10' & ./config_odbc --mode=guess How to set the environment In almost all cases it is required that several environment variables are set, and sometimes compatibility soft links are necessary. To simplify this task, config_odbc generates a wrapper script for each DSN to start applications: ./drivers/DSN/exec MyApp with some args "DSN" has to be replaced by the correct DSN for this application. Troubleshooting config_odbc does not start Some operating system have no or only a crippled Perl installation. Install a full Perl system and try again. Fix: minimal Debian apt-get install perl Fix: minimal CentOS 7 yum install perl-Digest-MD5 Configuration went well but applications can not connect Make sure EXASolution is reachable and the ODBC driver manager / ODBC driver combination works in principle. Use the test scripts in the drivers directory (the second part of the path must be a valid DSN) for this purpose: Example: connection testing ./drivers/exasolution_uo2214lv2_64/test Everything else Please call EXASOL support and don't forget to provide the file config_odbc.log . Even if you want to use EXASolution 4.2 ODBC driver for production, try EXASolution 5.0 ODBC driver as described in SOL-153 . The diagnostic capabilities of 5.0's config_odbc are superior and therefore it's easier to pinpoint the cause of trouble. Attach the file support.tar generated by 5.0's config_odbc to the support call.
    • Category 1:
      Clients, Interfaces & Drivers - ODBC

      Attachments

        Issue Links

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: