Table of Contents

Search

  1. Preface
  2. Introduction to ODBC Connector
  3. Connections for ODBC
  4. Synchronization tasks with ODBC Connector
  5. Mappings and mapping tasks with ODBC Connector
  6. SQL ELT optimization
  7. Data type reference

ODBC Connector

ODBC Connector

Connection details

Connection details

The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
ODBC
Runtime Environment
The name of the runtime environment where you want to run tasks.
Select a Secure Agent, Hosted Agent, or serverless runtime environment.
For more information about how to configure a serverless environment, see Use the serverless runtime environment.
ODBC Subtype
The ODBC connection subtype that you need to select to connect to a specific database. For information on the supported subtypes and their capabilities, see .
Authentication Mode
The authentication method to connect to DB2 or SAP Sybase ASE.
This property appears only if you select the ODBC subtype as
DB2
or
SAP Sybase ASE
.
Select one of the following authentication modes from the list:
  • Database. Uses the user name and password to connect to the selected ODBC subtype.
  • Kerberos. Uses Kerberos authentication to connect to the selected ODBC subtype.
    When you choose this option on Windows, ensure that the user account that starts the Secure Agent service is available in the endpoint of the selected ODBC subtype. You don't need to enter your credentials to access the database.
    You can't configure Kerberos authentication when you use a Hosted Agent or serverless runtime environment.
    Default is Database.
Kerberos Connection Properties
Additional connection properties to use Kerberos authentication to connect to DB2 or SAP Sybase ASE.
This property appears only if you select the ODBC subtype as
DB2
or
SAP Sybase ASE
and authentication mode as
Kerberos
.
If you specify more than one property, separate each key-value pair with a semicolon.
For example, if you don't set the required environment variables on the Secure Agent machine before you use Kerberos authentication, add the
KRB5_CONFIG
and
KRB5CCNAME
properties in the following format:
KRB5_CONFIG=<Absolute path of the Kerberos configuration file>\krb5.conf;KRB5CCNAME=<Absolute path of the credential cache file>/<File name>
User Name
The user name to connect to the required database.
Password
The password to connect to the required database.
The password cannot contain a semicolon.
Data Source Name
The data source name of the ODBC object.
Schema
The schema name of the ODBC object.
Code Page
The code page of the database server or flat file defined in the connection.
Select one of the following code pages:
  • MS Windows Latin 1. Select for ISO 8859-1 Western European data
  • UTF-8. Select for Unicode data
  • Shift-JIS. Select for double-byte character data
  • ISO 8859-15 Latin 9 (Western European)
  • ISO 8859-2 Eastern European
  • ISO 8859-3 Southeast European
  • ISO 8859-5 Cyrillic
  • ISO 8859-9 Latin 5 (Turkish)
  • IBM EBCDIC International Latin-1
  • Japanese Extended UNIX Code (incl. JIS X 0212)
  • Japanese EUC (with \<-> Yen mapping)
  • Japanese EUC (Packed Format)
  • IBM EBCDIC Japanese
  • IBM EBCDIC Japanese CP939
  • Japanese EBCDIC Fujitsu
  • HITACHI KEIS Japanese
  • NEC ACOS JIPSE Japanese
  • UNISYS Japanese
  • MITSUBISHI MELCOM Japanese
  • Japanese EBCDIC-Kana Fujitsu
  • HITACHI KEIS-Kana Japanese
  • NEC ACOS JIPSE-Kana Japanese
  • UNISYS-Kana Japanese
  • MITSUBISHI MELCOM-Kana Japanese
  • EBCDIC Japanese
  • EBCDIK Japanese
  • PC Japanese SJIS-78 syntax (IBM-942)
  • PC Japanese SJIS-90 (IBM-943)
  • EBCDIC Japanese Katakana SBCS
  • EBCDIC Japanese Katakana (w/ euro)
  • EBCDIC Japanese Latin-Kanji (w/ euro)
  • EBCDIC Japanese Extended (DBCS IBM-1390 combined with DBCS IBM-1399)
  • EBCDIC Japanese Latin (w/ euro update)
  • EBCDIC Japanese Katakana SBCS (w/ euro update)
  • MS Taiwan Big-5 w/ HKSCS extensions
  • MS Windows Traditional Chinese, superset of Big 5
  • Taiwan Big-5 (w/ euro update)
  • Taiwan Big-5 (w/o euro update)
  • PC Chinese GBK (IBM-1386)
  • Chinese EUC
  • Simplified Chinese (GB2312-80)
  • Hong Kong Supplementary Character Set
  • ISO 8859-8 Hebrew
  • PC Hebrew (old)
  • PC Hebrew (w/o euro update)
  • PC Hebrew (w/ euro update)
  • MS Windows Hebrew (older version)
  • MS Windows Hebrew (w/o euro update)
  • Lotus MBCS encoding for Windows Hebrew
  • EBCDIC Hebrew (updated with sheqel, control characters)
  • EBCDIC Hebrew (w/ euro)
  • EBCDIC Hebrew (updated w/ euro and new sheqel, control characters)
  • Israeli Standard 960 (7-bit Hebrew encoding)

Advanced settings

The following table describes the advanced connection properties:
Property
Description
Driver Manager for Linux
When you create a new ODBC connection on Linux platform, you can select a driver manager for the Linux Secure Agent. Select one of the following driver managers:
  • Data Direct
  • unixODBC2.3.0
  • unixODBC2.3.4
The default driver manager is UnixODBC2.3.0.
To connect to Teradata, you can use only Data Direct as the driver manager on Linux.

0 COMMENTS

We’d like to hear from you!