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 User Privileges for Oracle Sources

Configuring User Privileges for Oracle Sources

Data Replication requires certain user privileges to read the Oracle online redo logs and archive logs and to perform other functions that involve database access. Grant the required user privileges to the user ID that Data Replication uses to connect to the Oracle source.
  1. To retrieve the table structure of the source tables, grant the following privileges:
    GRANT CREATE SESSION TO DATAREP_USER; GRANT RESOURCE TO DATAREP_USER; GRANT SELECT ANY TABLE TO DATAREP_USER; GRANT SELECT ANY DICTIONARY TO DATAREP_USER; GRANT ALTER SESSION TO DATAREP_USER; GRANT EXECUTE ON DBMS_FLASHBACK TO DATAREP_USER;
    You must grant EXECUTE on DBMS_FLASHBACK as the SYS user.
  2. For Amazon RDS for Oracle, grant the following privileges:
    GRANT EXECUTE ON rdsadmin.rds_file_util TO DATAREP_USER; EXEC rdsadmin.rdsadmin_util.grant_sys_object('ARCHIVELOG_DIR', 'DATAREP_USER', 'READ'); EXEC rdsadmin.rdsadmin_util.grant_sys_object('ONLINELOG_DIR', 'DATAREP_USER', 'READ');
  3. If you plan to replicate change data from encrypted Oracle 12
    c
    tables, grant SELECT on the SYS.ENC$ table.
    • For regular Oracle 12
      c
      database installations, execute the following SQL statement:
      GRANT SELECT ON SYS.ENC$ TO DATAREP_USER;
    • For Amazon RDS for Oracle 12
      c
      , execute the following SQL statement:
      EXEC rdsadmin.rdsadmin_util.grant_sys_object('ENC$', 'DATAREP_USER', 'SELECT');
  4. To capture transactional data when running the InitialSync, grant the following privilege:
    GRANT FLASHBACK ANY TABLE TO DATAREP_USER;
  5. To add supplemental log groups for source tables from the Data Replication Console, grant the following privilege:
    GRANT ALTER ANY TABLE TO DATAREP_USER;
  6. If the Oracle database is in a RAC environment and your replication jobs do not read data from online redo logs, grant the following privilege:
    GRANT ALTER SYSTEM TO DATAREP_USER;
    This privilege enables the Extractor to force a log file switch on the RAC instances to get consistent log file data.
  7. For InitialSync operations that use database links (dblinks) to synchronize Oracle sources and Oracle targets, grant the following privilege:
    GRANT CREATE VIEW TO DATAREP_USER; GRANT CREATE DATABASE LINK TO DATAREP_USER;
    InitialSync creates a view for each source table or for each part of a source table that is processed on a separate thread. These views use the AS OF SCN clause to ensure data consistency. These views also include any WHERE clauses that are defined for the source columns to filter source data. After initial synchronization processing finishes, InitialSync drops these views.

0 COMMENTS

We’d like to hear from you!