Before you configure a change tracking task, create and authorize a source database account with the required permissions. Permission requirements vary by database type.
Source database account permissions
Database | Required permissions | Account setup |
RDS for MySQL | A read-only account, or a custom account with the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions. | |
Self-managed MySQL database | The SELECT permission on the objects for change tracking The REPLICATION CLIENT, REPLICATION SLAVE, and SHOW VIEW permissions Permissions to create databases and tables. The permissions allow DTS to create a database named dts to record heartbeat data during change tracking. | Create an account for a self-managed MySQL database and configure binary logging. |
RDS for PostgreSQL | A privileged account that owns the selected database. | |
PolarDB for MySQL | A read-only account, or a custom account with the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions. | |
DRDS | Read permission on the subscribed object. | |
Self-managed Oracle database | DBA permissions. Important If you cannot grant DBA permissions, use Fine-grained authorization instead. | CREATE USER and GRANT. |