Setting Up QueryGrid T2T Utility - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
The QueryGrid T2T utility is supported in Teradata Data Mover 16.00 or later. In order to use the QueryGrid T2T utility, both the source and target system must have Teradata 15.00.01 or later and QueryGrid installed.
  1. Follow the instructions in the Teradata QueryGrid Teradata Database-to-Teradata Database Installation Guide, B035-5982 to install and configure QueryGrid.
    1. Configure the same proxy user and physical user on both the source and target system to run T2T tasks.
    2. Create a foreign server on the source system, ensuring that the source user has insert and select permissions on the foreign server.
  2. Grant source user permissions on either dbc.serverinfoV or dbc.serverInfoVX – depending on your system view.
  3. [Optional] Group pool is available with the T2T utility as long as all users are configured properly on both source and target systems. If you need to configure a group pool, follow these steps:
    1. Create a list of physical users on both the source and target system.
    2. Connect the physical users to the same proxy users created on the foreign server for both the source and target system.
    3. Grant the physical users insert and select permissions to the foreign server on source system.
    4. Grant the physical users permissions on dbc.serverinfoV or dbc.serverInfoVX on source system.
    5. Add the source users to a group pool in the source system. The same set of users created on the target system do not necessarily need to be added to the group pool on target system.
  4. Define a job using T2T as a force_utility using the use_foreign_server tag in the job definition. See Creating a Job Using the T2T Utility for more information. Note: If force_utility is not specified, but a valid foreign server is, Data Mover automatically selects T2T to move the data. T2T is not selected if the job consists of entire databases being copied or the tables contain T2T data restrictions.