Assigning Credentials to Oracle GoldenGate
Oracle GoldenGate processes require a database user to capture and deliver data to a PostgreSQL database and it is recommended to create a dedicated PostgreSQL database user for Extract and Replicat.
Privilege | Extract | Replicat | Purpose |
---|---|---|---|
Database Replication Privileges |
|||
|
Yes |
Yes |
Required for database connectivity.
|
|
Yes |
NA |
Required for the user to register Extract with a replication slot.
|
WITH SUPERUSER |
Yes |
NA |
Required to enable table level
supplemental logging (
SUPERUSER
authority and is the only user that can enable
TRANDATA .
|
|
Yes |
Yes |
For metadata access to tables in the schema to be replicated.
|
|
Yes |
Yes |
Grant select access on tables to be replicated. GRANT SELECT ON ALL TABLES IN SCHEMA
tableschema TO gguser; |
|
NA |
Yes |
Apply replicated DML to target objects. GRANT INSERT, UPDATE, DELETE, TRUNCATE ON
TABLE tablename TO gguser; |
Heartbeat and Checkpoint Table Privileges |
|||
|
Yes |
Yes |
Required by the Extract and Replicat user to add an Oracle GoldenGate schema for heartbeat and checkpoint table creation. GRANT CREATE ON DATABASE
dbname TO gguser; Alternatively, if |
|
Yes |
Yes |
For heartbeat and checkpoint table creation/deletion if the Extract or Replicat user does not own the objects.
|
|
Yes |
Yes |
For heartbeat update and purge function execution if the user calling the functions does not own the objects. GRANT EXECUTE ON ALL FUNCTIONS IN
SCHEMA ggschema TO gguser; |
|
Yes |
Yes |
For heartbeat and checkpoint table inserts, updates and deletes if the user does not own the objects. GRANT SELECT, INSERT, UPDATE, DELETE, ON ALL
TABLES IN SCHEMA ggschema TO
gguser; |