Database Privileges for Oracle GoldenGate for PostgreSQL
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.
The following database user privileges are required for Oracle GoldenGate to capture from and apply to a PostgreSQL database.
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.
|
|
Yes |
NA |
Required to enable table level supplemental logging (
For Azure Database for PostgreSQL, only the Admin user has 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.
|
|
NA |
Yes |
Apply replicated DML to target objects.
|
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.
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.
|
|
Yes |
Yes |
For heartbeat and checkpoint table inserts, updates and deletes if the user does not own the objects.
|