Checking Whether the Index Length of the Source Database Exceeds the Limit
Oracle -> MySQL/Oracle -> GaussDB(for MySQL) Migration and Synchronization
Check Item |
Whether the index length of the source database exceeds the limit |
---|---|
Description |
The migration fails because the index length of the source database exceeds the column length limit of the destination database. |
Failure Cause and Handling Suggestion |
Failure cause: There are indexes in the source database exceed the column length limit of the destination database. Handling suggestion: 1. Delete the tables from the migration object. 2. Modify the index length. |
MySQL Migration, Synchronization, and Disaster Recovery
Check Item |
Whether the index length of the source database exceeds the limit |
---|---|
Description |
The migration fails because the index length of the source database exceeds the column length limit of the destination database. |
Failure Cause and Handling Suggestion |
Failure cause: There are indexes in the source database exceed the column length limit of the destination database. Handling suggestion: Set innodb_large_prefix of the destination database to ON, or return to the previous step and select the table to be migrated again. |
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