Checking Whether Destination Contains the Configured Database

**Table 1** Checking whether destination contains the configured database
Check Item	Whether the destination contains the configured database.
Description	Databases and schemas cannot be migrated. You need to manually create databases and schemas on the destination database. Otherwise, the migration will fail.
Failure Cause and Handling Suggestion	Failure cause: Databases cannot be migrated from MySQL to PostgreSQL. Handling suggestion: In the destination database, manually create databases and schemas with the same names as those of the source database.
Failure Cause and Handling Suggestion	Failure cause: The objects to be synchronized already exist in the destination database. Handling suggestions: Delete the tables to be synchronized from the destination database or select the tables that do not exist in the destination database for synchronization.

**Table 2** Checking whether destination contains the configured database
Check Item	Whether the destination contains the configured database.
Description	In the MySQL to GaussDB(for openGauss) synchronization scenario, the mapped database must exist in the destination database. Otherwise, the synchronization fails.
Failure Cause and Handling Suggestion	Failure cause: The destination database does not contain the configured database. Handling suggestion: Before the synchronization, manually create a mapped database in the destination database.

**Table 3** Checking whether destination contains the configured database
Check Item	Whether the destination contains the configured database.
Description	In the GaussDB(for openGauss) to GaussDB(for openGauss) synchronization scenario, the mapped database must exist in the destination database. Otherwise, the synchronization fails.
Failure Cause and Handling Suggestion	Failure cause: The configured database does not exist in the destination. Handling suggestion: Before the synchronization, manually create a configured database in the destination.