How to prepare a database account for change tracking-Data Transmission Service(DTS)-阿里云帮助中心

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 permissions	Creation and authorization methods
RDS for MySQL	A read-only account, or a custom account with the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions.	Create an account and modify account permissions.
Self-managed MySQL database	The SELECT permission on the objects for change tracking. The REPLICATION CLIENT, REPLICATION SLAVE, and SHOW VIEW permissions. The permissions to create databases and tables. These permissions allow DTS to create a database named `test` to advance the binary log position.	Create an account for a self-managed MySQL database and configure binary logging.
RDS for PostgreSQL	A privileged account that is the owner of the selected database.	Create an account and create a database.
PolarDB for MySQL	A read-only account, or a custom account with the REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and SELECT permissions.	Create and manage database accounts.
PolarDB-X 1.0	Read permission on the object to be subscribed.	Manage database accounts
Self-managed Oracle database	DBA permissions. Important If DBA permissions cannot be granted, you can grant fine-grained permissions to the database account. For more information, see Fine-grained authorization.	CREATE USER and GRANT.