Configure access to Teradata configure-access-to-teradata
Use Campaign Federated Data Access (FDA) option to process information stored in an external databases. Follow the steps below to configure access to Teradata.
- Install and configure Teradata drivers
- Configure the Teradata external account in Campaign
- Set up additional configuration for Teradata and Campaign server
Teradata configuration teradata-config
You need to install drivers for Teradata to have connection to Campaign implemented.
-
Install the ODBC driver for Teradata.
It is made up of three packages that can be installed on Red Hat (or CentOS)/Suse in the following order:
- TeraGSS
- tdicu1510 (install it using setup_wrapper.sh)
- tdodbc1510 (install it using setup_wrapper.sh)
-
Configure the ODBC driver. The configuration can be carried out in the standard files: /etc/odbc.ini for general parameters and /etc/odbcinst.ini for declaring drivers:
-
/etc/odbc.ini
code language-none [ODBC] InstallDir=/etc/“InstallDir” corresponds to the location of the odbcinst.ini file.
-
/etc/odbcinst.ini
code language-none [ODBC DRIVERS] teradata=Installed [teradata] Driver=/opt/teradata/client/17.10/lib64/tdataodbc_sb64.so APILevel=CORE ConnectFunctions=YYY DriverODBCVer=3.51 SQLLevel=1
-
-
Specify the environment variables of the Adobe Campaign server:
- LD_LIBRARY_PATH: /opt/teradata/client/15.10/lib64 and /opt/teradata/client/15.10/odbc_64/lib.
- ODBCINI: location of the odbc.ini file (for example /etc/odbc.ini).
- NLSPATH: location of the opermsgs.cat file (https://experienceleague.adobe.com/opt/teradata/client/15.10/msg/opermsgs.cat?lang=en)
Teradata external account teradata-external
The Teradata external account allows you to connect your Campaign instance to your Teradata external database.
-
From Campaign Explorer, click Administration / Platform / External accounts.
-
Click New and select External database as Type.
-
To configure the Teradata external account, you must specify:
-
Type: Choose the Teradata type.
-
Server: URL or name of your Teradata server
-
Account: Name of the account used to access the Teradata database
-
Password: Password used to connect to the Teradata database
-
Database: Name of the database (optional)
-
Options: Options to be passed through Teradata. Use the following format: ‘parameter=value’. Use a semicolon as separator between values.
-
Timezone: Timezone set in Teradata. Learn more
-
The connector supports the following options:
For more on this, refer to this page.
For more on this, refer to this page
Add additional ODBC external accounts add-external
The Teradata driver provides its own ODBC library but this library may not be compatible with other ODBC external accounts.
If you want to configure another external account that also uses ODBC, e.g. Snowflake, you will need to add an ODBCLib option set to the path of the default ODBC library (/usr/lib/x86_64-linux-gnu/libodbc.so on Debian and /usr/lib64/libodbc.so on RHEL/CentOS).
Query banding
When multiple Adobe Campaign users connect to the same FDA Teradata external account, the Query banding tab allows you to set a query band, i.e. a set of key/value pairs, on a session.
When this option is configured, each time a Campaign user performs a query on the Teradata database, Adobe Campaign will send meta data, which consists of a list of keys, associated to this user. This data can then be used by Teradata administrators for audit purposes or to manage access rights.
To configure Query banding, follow the steps below:
-
Use the Default to enter a default query band that will be used if a user has no associated query band. If this field is left empty, the users with no query band will not be able to use Teradata.
-
Use the Users field to specify a query band for each user. You can add as many key/value pairs as you need e.g. priority=1;workload=high. If the user has no query band assigned, the Default field will be applied.
-
Check the Active box to activate this feature
External account troubleshooting external-account-troubleshooting
If the following error appears while testing the connection TIM-030008 Date ‘2’: missing character(s) (iRc=-53) make sure that the ODBC driver is correctly installed and that the LD_LIBRARY_PATH (Linux) / PATH (Windows) is set for the Campaign server.
The error ODB-240000 ODBC error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. occurs with Windows if you use a 16.X driver. Adobe Campaign expects the teradata to be named ‘{teradata}’ in odbcinst.ini.
-
Starting Campaign 18.10, you can add ODBCDriverName=“Teradata Database ODBC Driver 16.10” in the options of the external account. The version number can change, the exact name can be found by running odbcad32.exe and accessing to the Drivers tab.
-
If you are using an older Campaign version, you will have to copy the Teradata section of odbcinst.ini created by the driver installation to a new section called Teradata. Regedit can be used in this case. If your base is in latin1, you will have to add APICharSize=1 in the options.
Additional configurations teradata-additional-configurations
User configuration user-configuration
The following rights are required on the external database: create/drop/execute custom procedures, create/drop/insert/select tables. You may also have to create user mode functions if you want to use md5 and sha2 function on your Adobe Campaign instance.
Make sure to configure the correct time zone. It should match what will be set in the external account created in the Adobe Campaign instance.
Adobe Campaign will not set a protection mode (fallback) on the objects it will create in the database. You might need to set a default on the user that Adobe Campaign will use to connect to the Teradata database using the following query:
MODIFY USER $login$ AS NO FALLBACK;MD5 installation md5-installation
If you want to use md5 functions in your Adobe Campaign instance, you will have to install the user mode function on your Teradata database from this page (md5_20080530.zip).
The sha1 of the downloaded file is as follows 65cc0bb6935f72fcd84fef1ebcd64c00115dfd1e.
To install md5:
-
Unzip the md5_20080530.zip file.
-
Go to the md5/src directory.
-
Connect to your Teradata database using bteq.
-
Run the following bteq command:
code language-none .run file = hash_md5.btq
SHA2 installation sha2-installation
If you want to use sha2 functions in your Adobe Campaign instance, you will have to install the user mode function on your Teradata database from this page (teradata-udf-sha2-1.0.zip).
The sha1 of the downloaded file is as follows e87438d37424836358bd3902cf1adeb629349780.
To install sha2:
-
Unzip the teradata-udf-sha2-1.0.zip file.
-
Go to the teradata-udf-sha2-1.0/src directory.
-
Connect to your Teradata database using bteq.
-
Run the two following bteq commands:
code language-none .run file = hash_sha256.sql .run file = hash_sha512.sql
UDF_UTF16TO8 installation UDF-UTF16TO8-installation
If you want to use udf_utf16to8 functions in your Adobe Campaign instance, install the user mode function on your Teradata database from the Teradata unicode tool kit.
The sha1 of the downloaded file is as follows e58235f434f52c71316a577cb48e20b97d24f470.
To install udf_utf16to8:
-
Unzip the utk_release1.7.0.0.zip file.
-
Look for the udf_utf16to8.o in the extracted files and navigate to the directory that contains the file. It should be named utk_release1.7.0.0/utk_release1.7.0.0/04 TranslationUDFs/01 Teradata UDFs/suselinux-x8664/udf_installation/.
-
Connect to your Teradata database using bteq.
-
Type in the following bteq command:
code language-none REPLACE FUNCTION udf_utf16to8 ( inputString VARCHAR(8000) CHARACTER SET UNICODE ) RETURNS VARCHAR(16000) CHARACTER SET LATIN LANGUAGE C NO SQL EXTERNAL NAME 'CO!i18n103!udf_utf16to8.o!F!udf_utf16to8' PARAMETER STYLE SQL; -- Test: should return 410042 SELECT CAST(Char2HexInt(UDF_UTF16to8(_UNICODE'004100000042'XC)) AS VARCHAR(100));
Campaign server configuration for Linux campaign-server-linux
The following is required for the driver installation:
File names and sha1:
-
tdodbc1620__linux_indep.16.20.00.00-1.tar.gz 121fdd978b56fe1304fc5cb7819741b0847f44fd
-
TeradataToolsAndUtilitiesBase__linux_indep.16.20.01.00.tar.gz b 29d0af5ffd8dcf68a9dbbaa6f8639387b19c563
If there is no package for your Linux distribution, you can install as explained on a CentOS 7 (for example using docker) and then copy the content of the /opt/teradata on your Adobe Campaign server.
ODBC driver installation odbc-installation
To install ODBC driver:
-
Extract the tdodbc1620__linux_indep.16.20.00.00-1.tar.gz file.
-
Go to the tdodbc1620 directory.
-
You might need to fix the setup script:
code language-none "sed -i s/16.10/16.20/ setup_wrapper.sh". -
Run the setup_wrapper.sh.
Teradata tools and utilities installation teradata-tools-installation
To install Tools:
-
Extract the TeradataToolsAndUtilitiesBase__linux_indep.16.20.01.00.tar.gz file.
-
Go to the TeradataToolsAndUtilitiesBase/Linux/i386-x8664/tdicu directory.
-
Run the setup_wrapper.sh.
-
Go to the TeradataToolsAndUtilitiesBase/Linux/i386-x8664/cliv2 directory.
-
Run the setup_wrapper.sh.
-
Go to the TeradataToolsAndUtilitiesBase/Linux/i386-x8664/tptbase directory.
-
Run the setup_wrapper.sh.
-
A libtelapi.so file should be available in /opt/teradata/client/16.20/lib64.
Campaign server configuration for Windows campaign-server-windows
You first need to download Teradata Tools and utilities for Windows. You can download it from this page
Make sure to install the ODBC driver and the Teradata Parallel Transporter Base. It will install telapi.dll used to do bulk load on Teradata database.
Make sure the path of the driver and the utilities is in the PATH variable that nlserver will have during execution. By default the path is C:\Program Files (x86)\Teradata\Client\15.10\bin on Windows 32 bits or C:\Program Files\Teradata\Client\15.10\bin on 64 bit).
Time zone timezone
Teradata uses time zone name that are not standard, you can find the list on the Teradata site. Adobe Campaign will try to convert the time zone given in the external configuration to something Teradata understand. If a correspondence is not found, the closet GMT+X (or GMT-X) time zone will be found for the session, with a warning in the log.
The conversion is done reading a file called teradata_timezones.txt that should be in the following datakit directory: /usr/local/neolane/nl6/datakit under linux. If you edit this file, make sure to contact the Adobe Campaign team to make the change in the source code otherwise this file will be overwritten during next Campaign update.
The time zone used to connect will be indicated when running nlserver with the -verbose switch, for example:
15:04:04 > ODB-240007 Teradata: will use 'Europe Central' as session time zone.
If the time zone used is not the correct one, an option named “TimeZoneName” can be added on the external account. In that case, use the Teradata Value, for example “TimeZoneName=Europe Central”.
When using bulk load, or “fast load” in Teradata documents, Campaign can’t indicate the time zone. Therefore, it is recommended to set the default time zone of the user that Campaign will use to connect:
MODIFY USER $login$ AS TIME ZONE = 'Europe Central';