Registering the Teradata wrapper

Federated servers use wrappers to communicate with and retrieve data from data sources. Wrappers are implemented as a set of library files. A wrapper is created implicitly when a CREATE SERVER statement is run.

Procedure

Issue the CREATE WRAPPER statement from the command line and specify the default name for the Teradata wrapper.

For example:

CREATE WRAPPER TERADATA;

Remember: When you register the wrapper by using the default name, TERADATA, the federated server automatically uses the appropriate Teradata wrapper library for the operating system that your federated server is running on.

If the default wrapper name conflicts with an existing wrapper name in the federated database, you can substitute the default wrapper name with a name that you choose. When you use a name that is different from the default name, you must include the LIBRARY parameter in the CREATE WRAPPER statement.

For example, to register a wrapper with the name tera_wrapper on a federated server that uses AIX®, issue the following statement:

CREATE WRAPPER tera_wrapper 
  LIBRARY 'libdb2teradata.a' 
  OPTIONS (DB2_FENCED 'Y');

The wrapper library file that you specify depends on the operating system of the federated server.

Mandatory options for AIX and Solaris

Note: The DB2_FENCED wrapper option in the CREATE WRAPPER statement are mandatory for AIX because the Teradata wrapper supports only 32-bit clients.

For example:

CREATE WRAPPER TERADATA 
  OPTIONS (DB2_FENCED 'Y')

What to do next

After you complete this task, you can register the server definition.