Troubleshoot database access issues

Available in VPC

In using Database Migration Service, you may encounter the following problems. View the causes and solutions of problems and take proper action:

Source DB and Target DB server communication error

Source DB and Target DB servers are not communicating.

Cause

You need to set the connection information to connect the Source DB server and the Target DB server before migration.

Solution

Inspect the Inbound ACG policy of the Source DB and the Outbound ACG policy of the Target DB. For more information on connection settings by migration scenario, see Source DB and Target DB connection settings.

Source DB access error

Attempted Test Connection but cannot access Source DB.

Cause

You must set the firewall for the Source DB Server (ACG) for access from the Target DB.

Solution

Edit ACG's Inbound rules applied to the Source DB server to allow the following traffic:

• Protocol: TCP
• Access source: Public domain IP address allocated to Target DB (example: 101.101.220.246/32)
• Allowed port: Target DB access port

Display DB ACL check message

When trying Test Connection, DB ACL check message displays.

Cause

For Source DB backup and replication, you need Target DB access, backup, and replication permissions for the account created in mysql_native_password format.

Solution

Assign Target DB access, backup, and replication permissions for the account created in mysql_native_password format. For more information, see creating Source DB account and setting ACL.

BACKUP_ADMIN / RELOAD permission

I want to use mydumper method, but I get a message saying that I need BACKUP_ADMIN / RELOAD permissions.

Cause

BACKUP_ADMIN permissions are granted only to DDL accounts on cluster with version 8.0.23 or later.

Solution

If you need this permission for other versions, request with Source DB information through customer inquiry. This is only possible if the Source DB is the Cloud DB for MySQL cluster.