Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Interactive Data Preparation Service
  11. Enterprise Data Preparation Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Configuring ODBC Connectivity

Configuring ODBC Connectivity

You can configure ODBC connectivity to a Teradata database.
The following steps provide a guideline for configuring ODBC connectivity. For specific instructions, see the database documentation.
  1. To configure connectivity for the integration service process, log in to the machine as a user who can start a service process.
  2. Set the TERADATA_HOME, ODBCHOME, and PATH environment variables.
    TERADATA_HOME
    . Set the variable to the Teradata driver installation directory. The defaults are as follows:
    Using a Bourne shell:
    $ TERADATA_HOME=/opt/teradata/client/<version>; export TERADATA_HOME
    Using a C shell:
    $ setenv TERADATA_HOME /opt/teradata/client/<version>
    ODBCHOME
    . Set the variable to the ODBC installation directory. For example:
    Using a Bourne shell:
    $ ODBCHOME=$INFA_HOME/ODBC<version>; export ODBCHOME
    Using a C shell:
    $ setenv ODBCHOME $INFA_HOME/ODBC<version>
    PATH
    . To run the
    ddtestlib
    utility, to verify that the DataDirect ODBC driver manager can load the driver files, set the variable as follows:
    Using a Bourne shell:
    PATH="${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin"
    Using a C shell:
    $ setenv PATH ${PATH}:$ODBCHOME/bin:$TERADATA_HOME/bin
  3. Set the shared library environment variable.
    The Teradata software contains multiple shared library components that the integration service process loads dynamically. Set the shared library environment variable so that the services can find the shared libraries at run time.
    The shared library path must also include installation directory of the Informatica service
    (server_dir)
    .
    Set the shared library environment variable based on the operating system.
    The following table describes the shared library variables for each operating system:
    Operating System
    Variable
    Solaris
    LD_LIBRARY_PATH
    Linux
    LD_LIBRARY_PATH
    AIX
    LIBPATH
    For example, use the following syntax for Solaris and Linux:
    • Using a Bourne shell:
      $ LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$ODBCHOME/lib: $TERADATA_HOME/lib64:$TERADATA_HOME/odbc_64/lib"; export LD_LIBRARY_PATH
    • Using a C shell:
      $ setenv LD_LIBRARY_PATH "${LD_LIBRARY_PATH}:$HOME/
      server_dir
      :$ODBCHOME/lib:$TERADATA_HOME/lib64: $TERADATA_HOME/odbc_64/lib"
    For AIX
    • Using a Bourne shell:
      $ LIBPATH=${LIBPATH}:$HOME/
      server_dir
      :$ODBCHOME/lib:$TERADATA_HOME/lib64:$TERADATA_HOME/odbc_64/lib; export LIBPATH
    • Using a C shell:
      $ setenv LIBPATH ${LIBPATH}:$HOME/
      server_dir
      :$ODBCHOME/lib:$TERADATA_HOME/lib64: $TERADATA_HOME/odbc_64/lib
  4. Edit the existing odbc.ini file or copy the odbc.ini file to the home directory and edit it.
    This file exists in $ODBCHOME directory.
    $ cp $ODBCHOME/odbc.ini $HOME/.odbc.ini
    Add an entry for the Teradata data source under the section [ODBC Data Sources] and configure the data source.
    For example, for Teradata Parallel Transporter utilities, version 15.10:
    MY_TERADATA_SOURCE=Teradata Driver [MY_TERADATA_SOURCE] Driver=/opt/teradata/client/15.10/lib64/tdata.so Description=NCR 3600 running Teradata V1R5.2 DBCName=208.199.59.208 DateTimeFormat=AAA SessionMode=ANSI DefaultDatabase= Username= Password=
    For example, for Teradata Parallel Transporter utilities, version 16.20:
    MY_TERADATA_SOURCE=Teradata Driver [dwtera] Driver=/opt/teradata/client/16.20/lib64/tdataodbc_sb64.so Description=NCR 3600 running Teradata V1R5.2 DBCName=tdvbe1510 LastUser= Username= Password= Database= DefaultDatabase= UseNativeLOBSupport=Yes CharacterSet=UTF8 SessionMode=ANSI
  5. Set the DateTimeFormat to AAA in the Teradata data ODBC configuration.
  6. Optionally, set the SessionMode to ANSI. When you use ANSI session mode, Teradata does not roll back the transaction when it encounters a row error.
    If you choose Teradata session mode, Teradata rolls back the transaction when it encounters a row error. In Teradata mode, the integration service process cannot detect the rollback, and does not report this in the session log.
  7. To configure connection to a single Teradata database, enter the DefaultDatabase name. To create a single connection to the default database, enter the user name and password. To connect to multiple databases, using the same ODBC DSN, leave the DefaultDatabase field empty.
    For more information about Teradata connectivity, see the Teradata ODBC driver documentation.
  8. Verify that the last entry in the odbc.ini is InstallDir and set it to the odbc installation directory.
    For example:
    InstallDir=<Informatica installation directory>/ODBC<version>
  9. Edit the .cshrc or .profile to include the complete set of shell commands.
  10. Save the file and either log out and log in again, or run the source command.
    Using a Bourne shell:
    $ source .profile
    Using a C shell:
    $ source .cshrc
  11. For each data source you use, make a note of the file name under the Driver=<parameter> in the data source entry in odbc.ini. Use the
    ddtestlib
    utility to verify that the DataDirect ODBC driver manager can load the driver file.
    For example, if you have the driver entry:
    Driver=/u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
    run the following command:
    ddtestlib /u01/app/teradata/td-tuf611/odbc/drivers/tdata.so
  12. Test the connection using BTEQ or another Teradata client tool.