When you configure a change tracking task, you must specify the account of the source database. The database account is used for change tracking. Different databases require different permissions. You must create and authorize a database account before you configure a change tracking task.

Permissions required for the source database account

Database Required permission References
ApsaraDB RDS for MySQL instance A database account that has read-only permissions, or a custom account that has the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions Create an account on an ApsaraDB RDS for MySQL instance and Modify the permissions of a standard account on an ApsaraDB RDS for MySQL instance
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 user-created MySQL database and configure binary logging
ApsaraDB RDS for PostgreSQL instance Permissions of a privileged account. The account must be the owner of the database. Create an account on an ApsaraDB RDS for PostgreSQL instance and Create a database on an ApsaraDB RDS for PostgreSQL instance
PolarDB for MySQL cluster A database account that has read-only permissions, or a custom account that has the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions Create a database account
PolarDB-X 1.0 instance Read permissions on the objects for change tracking Manage database accounts
Self-managed Oracle database Permissions of the database administrator (DBA)
Notice If the permissions of DBA cannot be granted to the database account, you can grant fine-grained permissions to the account. For more information, see Track data changes from a self-managed Oracle database.
CREATE USER and GRANT