Recreating Teradata configurations

To upgrade to Teradata release V2R5 and above, you can recreate your entire Teradata wrapper configuration of servers, user mappings, type mappings, function mappings, and nicknames.

1. Use the db2look command to get the correct syntax for each data source configuration statement.
   The db2look command generates DDL statements from the metadata in the Db2® catalog.
2. In the db2look command output file, make the following modifications:
   1. Change all references to the Teradata product version to the required release for all server objects.
   2. For AIX®: update all CREATE WRAPPER statements for the Teradata wrapper by setting the DB2_FENCED wrapper option. For example:

      CREATE WRAPPER teradata OPTIONS (DB2_FENCED 'Y')

3. Drop the Teradata wrapper.
   When you drop a wrapper, all server definitions, user-defined function mappings, and user-defined data type mappings that are dependent on the wrapper are dropped. All user-defined function mappings, nicknames, user-defined data type mappings, and user mappings that are dependent on the dropped server definitions are also dropped. All packages dependent on the dropped objects and inoperative views are invalidated.
4. If necessary, drop the type and function mappings that are associated with the type or version of the servers that you dropped. The DROP WRAPPER statement drops only the objects that are explicitly associated with a wrapper or its servers. If other objects are associated with the type or version of the servers that you dropped, you must manually drop those objects.
5. Issue the SQL statements in the db2look output file to reconfigure access to Teradata. For example, if the name of the output file is teradata.sql, issue the following command:

   db2 -tvf teradata.sql

6. Bind any application packages that were invalidated when you dropped the wrapper.