Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Configuring Database User Account Privileges for Teradata Targets

Configuring Database User Account Privileges for Teradata Targets

Informatica Data Replication requires certain user privileges to read and apply changes to Teradata target databases. Target tables and the related log tables may be located in different databases. In that case, you must grant privileges on each database.
Grant the following privileges to the user accounts that Data Replication uses to connect to the Teradata target:
  1. To retrieve the structure of the tables, grant the following privileges:
    GRANT SELECT ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT SELECT ON LOG_DATABASE TO DATAREP_USER/ROLE;
  2. To create new tables for replication or logging, grant the following privileges:
    GRANT CREATE TABLE ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT CREATE TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE;
    Optionally, grant the following privileges if you want the user who created a table to also be able to drop the table:
    GRANT DROP TABLE ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT DROP TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE;
  3. To insert or apply change data to target tables during InitialSync in Merge Apply mode, grant the following privileges:
    GRANT INSERT ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT UPDATE ON TARGET_DATABASE TO DATAREP_USER; GRANT DELETE ON TARGET_DATABASE TO DATAREP_USER;
    GRANT INSERT ON LOG_DATABASE TO DATAREP_USER/ROLE; GRANT UPDATE ON LOG_DATABASE TO DATAREP_USER/ROLE; GRANT DELETE ON LOG_DATABASE TO DATAREP_USER/ROLE;
    GRANT CREATE TABLE ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT DROP TABLE ON TARGET_DATABASE TO DATAREP_USER/ROLE;
    GRANT CREATE TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE; GRANT DROP TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE;
    GRANT CREATE MACRO ON LOG_DATABASE TO DATAREP_USER/ROLE; GRANT DROP MACRO ON LOG_DATABASE TO DATAREP_USER/ROLE;
    GRANT CREATE VIEW ON TARGET_DATABASE TO DATAREP_USER/ROLE; GRANT DROP VIEW ON TARGET_DATABASE TO DATAREP_USER/ROLE;
    The CREATE VIEW privilege is required only for handling long column names when log tables are created automatically. The corresponding DROP VIEW privilege is optional unless the user who created a view also needs privileges to drop the view. Data Replication does not perform any DROP VIEW actions.
  4. To insert change data to log tables in Audit Apply mode, grant the following privileges:
    GRANT INSERT ON LOG_DATABASE TO DATAREP_USER/ROLE;
    GRANT CREATE TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE; GRANT DROP TABLE ON LOG_DATABASE TO DATAREP_USER/ROLE;
    CREATE TABLE and DROP TABLE privileges are required to automatically create the error, work, and trace tables that Teradata Parallel Transporter uses.

0 COMMENTS

We’d like to hear from you!