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 and migration types 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 permissions Topics about how to create and authorize a database account
ApsaraDB RDS for MySQL The SELECT permission on the required objects, the REPLICATION CLIENT permission, the REPLICATION SLAVE permission, and the SHOW VIEW permission 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 required objects, the REPLICATION CLIENT permission, the REPLICATION SLAVE permission, and the SHOW VIEW permission Create an account for a user-created MySQL database and configure binary logging
PolarDB for MySQL The SELECT permission on the required objects, the REPLICATION CLIENT permission, the REPLICATION SLAVE permission, and the SHOW VIEW permission Create a database account
The SELECT permission on the required objects, the REPLICATION CLIENT permission, and the REPLICATION SLAVE permission DTS automatically authorizes the database account.
Self-managed Oracle database The DBA permission
Notice If the DBA permission cannot be granted to the database account, you can grant fine-grained permissions to the account. For more information, see Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance.
CREATE USER and GRANT