Destination Database Same Name Check
MySQL to Oracle Synchronization
Check Item |
Destination database same name check |
---|---|
Description |
For synchronization from MySQL to Oracle, check whether there is a database table with the same name in the destination database.
|
Failure Cause and Handling Suggestion |
Failure cause: The table structure synchronization is selected, and there are tables to be synchronized in the destination database. Handling suggestion: To synchronize table structures, delete existing tables from the destination database. |
Failure cause: The table structure synchronization is not selected, and there are no tables to be synchronized in the destination database. Handling suggestion: Select Table structure in the previous step or create the corresponding tables in the destination database. |
|
Failure cause: The source table columns are not a subset of the destination columns. Handling suggestion: Return to the Set Synchronization Task page, select the tables that meet the requirements. Alternatively, create columns required in the destination table. |
|
Failure cause: Some databases cannot be synchronized because the databases with the same names do not exist in the destination databases. For synchronization tasks, you need to create the corresponding database (user) in the destination database in advance. Handling suggestion: Create these databases or users in the destination database or do not synchronize 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