Teradata Database Access Privileges - Parallel Transporter

Teradata® Parallel Transporter User Guide

Product
Parallel Transporter
Release Number
16.20
Published
August 2020
Language
English (United States)
Last Update
2020-08-27
dita:mapPath
uah1527114222342.ditamap
dita:ditavalPath
Audience_PDF_product_tpt_userguide_include.ditaval
dita:id
B035-2445
lifecycle
previous
Product Category
Teradata Tools and Utilities
The user represented by the value of the UserName attribute in an operator definition must have the Teradata Database access privileges required for the actions that the operator will execute. Refer to the following list and make sure all users referenced in your job script have the access privileges necessary for job to run:
  • Load operator:
    • SELECT and INSERT privileges on the Load target table.
    • SELECT and INSERT privileges on the error tables, and DROP privileges on the database that contains the error tables.
    • SELECT, INSERT, and DELETE privileges on the restart log table, and DROP privileges on the database that contains the restart log table.
  • DDL operator:
    • The DDL operator requires all privileges necessary to execute the SQL that it submits as part of a Teradata PT job, for example, CREATE TABLE privileges.
    • REPLCONTROL privilege to set the ReplicationOverride attribute.
  • Export operator:
    • SELECT privileges on the Export target table.
  • SQL Inserter operator:
    • REPLCONTROL privilege to set the ReplicationOverride attribute.
  • Stream operator:
    • SELECT and INSERT privileges on the error tables, and CREATE and DROP privileges on the database that contains the error tables.
    • SELECT, INSERT, and DELETE privileges on the restart log table, and CREATE and DROP privileges on the database that contains the restart log table.
    • REPLCONTROL privilege to set the ReplicationOverride attribute.

    The Stream operator does not have any special protections on the database objects it creates. Therefore, administrators and users must establish the following privileges on the databases used by the Stream operator:

    • CREATE TABLE privileges on the database where the restart log table is placed.
    • CREATE TABLE privileges on the database where the error table is placed.
    • CREATE/DROP MACRO privileges on the database where macros are placed.
    • EXECUTE MACRO privileges on the database where the macros are placed.

      Macros slightly complicate privileges. The remaining privileges necessary to run the Stream operator have two scenarios:

      When a Stream operator macro is placed in the same database as the table that it affects, the required privileges are INSERT/UPDATE/DELETE on the table affected by the DML executed.

      When a Stream operator macro is placed in a different database from the table it affects, the required privileges for the database where the macro is placed are INSERT/UPDATE/DELETE WITH GRANT OPTION in the table affected by the DML executed. You must also have EXECUTE MACRO rights on the database where the macro is placed.

    To change a table, you must have the corresponding INSERT, UPDATE, or DELETE privileges for that table.

  • Update operator:
    • SELECT and INSERT privileges on the Update target table
    • SELECT and INSERT privileges on the error tables, and DROP privileges on the database that contains the error tables.
    • SELECT, INSERT, and DELETE privileges on the restart log table, and DROP privileges on the database that contains the restart log table.
    • REPLCONTROL privilege to set the ReplicationOverride attribute.

For detailed information on how to GRANT such privileges to users, see the Teradata Database Administration book (B035-1093), available from https://docs.teradata.com/.