Checking Whether the Names of the Source and Destination Databases Are the Same
MySQL Migration
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:
|
|
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. |
Migration from Redis to GeminiDB Redis
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: The destination instance cannot contain databases with the same names as those in the source. Handling suggestion: Determine whether to retain these databases in the destination instance or specify another destination instance. |
Oracle -> MySQL/Oracle -> GaussDB(for MySQL) Synchronization
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: Source database names are the same except for letter cases. Handling suggestion: Change the table name or return to the object selection page and deselect the tables with the same name. Statement for changing the table name: ALTER TABLE old_table_name RENAME TO new_table_name; |
Failure cause: The destination database contains a table to be synchronized. The table name is the same as the mapping name of the table to be synchronized in the source database. Handling suggestion: Delete the destination database table. Statement for deleting a table: DROP TABLE table_name; |
Oracle -> PostgreSQL Synchronization
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. |
|
Failure cause: The destination database contains a table to be synchronized. The table name is the same as the mapping name of the table to be synchronized in the source database. Handling suggestion: Delete the destination database table. Statement for deleting a table: DROP TABLE table_name; |
PostgreSQL > PostgreSQL Synchronization
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
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
Check Item |
Whether the names of the source and destination databases are the same |
---|---|
Description |
To synchronize data from DDM to Oracle, you need to create the corresponding database (user) in the destination database in advance. Otherwise, the synchronization fails. |
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 databases or users in the destination database or do not migrate these databases. Statement for creating a user: CREATE USER user_name IDENTIFIED BY password; |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot