Check Item |
Whether the source database user has sufficient permissions |
---|---|
Description |
The source database user must have the required permissions.
If the permissions are insufficient, the migration will fail. |
Failure Cause and Handling Suggestion |
Failure cause: In a full migration, the source database user must have the SELECT, SHOW VIEW, and EVENT permissions. Handling suggestions: Grant the source database user the corresponding permissions. |
Failure cause: In an incremental migration, the source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, In the DR scenario, the following permissions are required: CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, and INDEX. Handling suggestions: Grant the source database user the corresponding permissions. |
|
Failure cause: Insufficient user permissions Handling suggestion: Check whether the database user permissions meet the migration requirements. NOTE:
For details about the required MySQL permissions and authorized operations, see Which MySQL Permissions Are Required for DRS? |
|
Failure cause: An internal error occurs. Handling suggestion: Contact technical support. |
Check Item |
Whether the source database user has sufficient permissions |
---|---|
Description |
Check whether the source database user permissions meet the migration requirements. If the permissions are insufficient, the migration will fail. |
Failure Cause and Handling Suggestion |
Failure cause: This item cannot be checked because the source database fails to be connected. Handling suggestion: Check whether the source database is connected. |
Failure cause: The source database user does not have the required permissions. Handling suggestion: Check whether the source database user permissions meet the migration requirements. |
|
Failure cause: An internal error occurs. Handling suggestion: Contact technical support. |