Create Connection

This article explains how to set up the connection between Teradata and Exasol.

Before you begin the migration procedure, you must upload the Teradata JDBC driver to your Exasol system and configure a connection between the databases. 

Teradata JDBC driver

Download the Teradata JDBC Driver

Download the compatible JDBC driver for your version of Teradata from Maven Central .

Add the JDBC driver in Exasol

Create a configuration file called settings.cfg with the following settings:

Copy
DRIVERNAME=Teradata
PREFIX=jdbc:teradata:
FETCHSIZE=100000
INSERTSIZE=-1

The driver jar files and the configuration file must be uploaded to BucketFS in Exasol. By default, the database is configured to use the following path for all JDBC drivers:

/buckets/bfsdefault/default/drivers/jdbc/ 
Examples:

The following examples use curl on a Linux terminal, but you can also use other interfaces and tools.

Placeholder values in the examples are styled as Bash variables, for example: $NODE_IP. Replace these placeholders with your own values.

Copy
curl -v --insecure -X PUT -T settings.cfg https://w:$WRITE_PW@$DATABASE_NODE_IP:2581/default/drivers/jdbc/exasol/settings.cfg
Copy
curl -v --insecure -X PUT -T terajdbc-$VERSION.jar https://w:$WRITE_PW@$DATABASE_NODE_IP:2581/default/drivers/jdbc/exasol/terajdbc-$VERSION.jar

The option --insecure or -k tells curl to bypass the TLS certificate check. This option allows you to connect to a HTTPS server that does not have a valid certificate. Only use this option if certificate verification is not possible and you trust the server.

Create and test the connection

  1. Open a SQL client and create the connection from Exasol to Teradata:
    Copy
    CREATE OR REPLACE CONNECTION TERADATA_DB 
    TO 'jdbc:teradata://192.168.99.105/CHARSET=UTF16' 
    USER 'dbc' IDENTIFIED BY 'dbc';
  2. Test the connection by performing a small dummy import:
    Copy
    IMPORT FROM JDBC AT TERADATA_DB
    STATEMENT 'SELECT ''Connection to Teradata works''';

If the connection fails, try disabling the security manager by adding the line NOSECURITY=YES to the settings.cfg file.