Accessing Teradata data sources after upgrading

Before you can access Teradata data sources on AIX®, you must check the environment variables, run the djxlink script, recycle the Db2® instance, and verify wrapper option settings. On Windows, you must verify that the wrapper option settings are correct.

Before you begin

If you already use the Teradata wrapper, you can upgrade to Teradata release V2R5 and above by modifying your existing Teradata wrapper configuration or by recreating your entire Teradata wrapper configuration of servers, user mappings, type mappings, function mappings, and nicknames.

About this task

Use this procedure if you upgraded the instance and database or only the database.

If you upgraded only the database, follow all of the steps in this procedure.

If you upgraded the instance and the database, you might need to perform only some of the steps in this procedure. You might need to perform these steps:
  • Run the djxlink script or the djxlinkTeradata script.
  • Recycle the Db2 instance.
  • Verify the upgrade.
If you upgraded the instance and database, you might need to perform these steps if the djxlink script or the djxlinkTeradata script did not run when you installed Federation component.

To access Teradata data sources after you upgrade to Federation component:

Procedure

  1. Check the settings of the environment variables for the Teradata data sources:
    1. Locate the db2dj.ini file.
      The db2dj.ini file is located in the file that is specified by Db2 registry variable, DB2_DJ_INI. When this variable is not set, the default is as follows:
      UNIX
      instancehome/sqllib/cfg/db2dj.ini, where instancehome is the home directory of the instance owner.
      Windows
      DB2PATH\cfg\db2dj.ini, where DB2PATH is the directory where the Db2 database system is installed, for example, C:\Program Files\IBM\SQLLIB.
    2. Set the environment variables in db2dj.ini file as necessary:
      COPLIB
      The directory in which the Teradata shared library file, libcliv2.so, resides. For example: 
      COPLIB=coplib_directory
      COPERR
      The directory in which the errmsg.cat file resides. For example:
      COPERR=coperr_directory
      The libcliv2.so file and the errmsg.cat are usually in the same directory. The default directory is /usr/lib on AIX.
  2. If the djxlink script or the djxlinkTeradata script did not run during installation, run the djxlink script or the djxlinkTeradata script.
  3. If you changed any environment variables in the db2dj.ini file in step 1 or if you ran the djxlink script or the djxlinkTeradata script in step 2, recycle the Db2 instance:
    1. Issue the db2stop command.
    2. If you ran the djxlink script or the djxlinkTeradata script, issue the db2iupdt command.
    3. Issue the db2start command.
      By recycling the Db2instance, you ensure that the environment variable changes are properly set on the federated server.
  4. AIX and Windows: verify the wrapper option settings:
    Query the SYSIBM.SYSWRAPOPTIONS catalog table to verify the DB2_FENCED wrapper option is set to Y. If necessary, change the value of the wrapper option by issuing the ALTER WRAPPER statement.
  5. Use the Teradata BTEQ query tool to test your connection to the Teradata server.
  6. Verify that the upgrade is successful:
    1. Connect to the database.
    2. Issue SELECT, INSERT, UPDATE, and DELETE statements on the nicknames to verify that you can view and modify the data.
      You can also open a passthrough session to the remote database and issue a SELECT statement on a remote table.