Help Center> Data Replication Service> Troubleshooting> Solutions to Failed Check Items> Conflicts> Checking Whether the Names of the Source and Destination Databases Are the Same
Updated on 2022-09-21 GMT+08:00

Checking Whether the Names of the Source and Destination Databases Are the Same

MySQL Migration

Table 1 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the names of the source and destination databases are the same.

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: This item cannot be checked because the destination database fails to be connected.

Handling suggestion: Check whether the destination database is connected.

Failure cause: Insufficient user permissions

Handling suggestion: Check whether the database user permissions meet the migration requirements.

Handling suggestion:
  • If you are migrating data to the cloud, determine whether to delete the databases with the same names as the source databases or specify a new destination DB instance based on site requirements.
  • If you are migrating data out of the cloud, determine whether to use the original destination database or specify a new destination DB instance based on site requirements.

Failure cause: During an incremental migration, the source and destination databases cannot have the same names.

Handling suggestion: Determine whether to retain these databases in the destination RDS DB instance or specify another destination RDS DB instance.

Failure cause: An internal error occurs.

Handling suggestion: Contact Huawei technical support.

Oracle -> MySQL/Oracle -> GaussDB(for MySQL) Migration and Synchronization

Table 2 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the source and destination databases have the same names to prevent existing databases from being overwritten. If the source and destination databases have the same name, the migration cannot be performed.

Failure Cause and Handling Suggestion

Failure cause: Source database names are the same except for letter cases.

Handling suggestion: Change table names or do not migrate the tables with the same names.

Failure cause: Source database names are the same except for letter cases.

Handling suggestion: Select only one database among the databases whose names are the same except for letter cases.

Failure cause: The source and destination databases cannot have the same names.

Handling suggestion: Determine whether to retain these databases in the destination RDS DB instance or specify another destination RDS DB instance.

Oracle -> MySQL/Oracle -> GaussDB(for MySQL) Synchronization

Table 3 Checking Whether the Names of the Source and Destination Databases Are the Same

Check Item

Whether the names of the source and destination databases are the same

Description

The mapping names of the tables to be synchronized in the source databases are the same as the names of the destination database tables.

Failure Cause and Handling Suggestion

Failure cause: The names of the tables to be synchronized are already mapped to the destination database.

Handling suggestion: Select other tables to migrate or change the mapping names of the tables to be synchronized.

Oracle -> PostgreSQL Migration

Table 4 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

The migration fails when the names of the source and destination databases are different.

Failure Cause and Handling Suggestion

Failure cause: The source and destination databases must have the same names, except that the destination database must use only lowercase letters.

Handling suggestion: Create a database with name in lowercase letters in the destination database.

Failure cause: The names of the objects to be migrated are the same except for letter cases.

Handling suggestion: Select only one database among the databases whose names are the same except for letter cases.

Failure cause: The names of the tables to be migrated are the same except for letter cases.

Handling suggestion: Change table names or do not migrate the tables with the same names.

Failure cause: The names of the tables to be migrated are the same as those in the destination database and use only lowercase letters.

Handling suggestion: Change table names or do not migrate the tables with the same names.

Oracle -> GaussDB T Migration

Table 5 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

The migration fails when the names of the source and destination databases are different.

Failure Cause and Handling Suggestion

Failure cause: Some tables cannot be migrated because tables with the same names already exist in the destination database.

Handling suggestion: Select the tables that do not contain same table names or rename these tables. Command example: alter table old_name rename to new_name

Failure cause: Some databases or users cannot be migrated because the destination databases do not have the databases or users with the same name.

Handling suggestion: Create these databases or users before the migration, or do not migrate these databases or users.

PostgreSQL to PostgreSQL Migration and Synchronization

Table 6 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the source and destination databases have the same names to prevent existing databases from being overwritten. If the source and destination databases have the same name, the migration cannot be performed.

Failure Cause and Handling Suggestion

Failure cause: The destination database names cannot be the same.

Handling suggestion: Change the destination database names to prevent the database from being overwritten.

PostgreSQL to GaussDB(DWS) Synchronization

Table 7 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Check whether the source and destination databases have the same names to prevent existing databases from being overwritten. If the source and destination databases have the same name, the migration cannot be performed.

Failure Cause and Handling Suggestion

Failure cause: The destination database names cannot be the same.

Handling suggestion: Change the destination database names to prevent the database from being overwritten.

DDM -> Oracle Synchronization

Table 8 Checking whether the names of the source and destination databases are the same

Check Item

Whether the names of the source and destination databases are the same

Description

Before synchronization from DDM to Oracle, databases or users with the same names must be created in the destination database.

Failure Cause and Handling Suggestion

Failure cause: Some databases cannot be synchronized because the databases with the same names do not exist in the destination databases.

Handling suggestion: Create these database or users in the destination databases or do not migrate these databases.