Checking Whether the Source and Destination Database Table Names Are Consistent in Case Sensitivity
During MySQL migration, the value of lower_case_table_names of the source database is inconsistent with that of destination database. If the value of lower_case_table_names is 0, the database is case sensitive. If the value of lower_case_table_names is 1, the database is case insensitive and all uppercase letters are converted to lowercase letters for storage. If the lower_case_table_names values of the source and destination databases are different, and a database or table is named using uppercase letters, the task may fail.
Failure Cause
The lower_case_table_names values of the source and destination databases must be the same.
Handling Suggestion
- If the database is an RDS for MySQL instance, change the value of lower_case_table_names by referring to Tables Failed to Be Found After Case-Sensitivity Setting Changes for RDS for MySQL.
- If the database is an on-premises MySQL database, perform the following steps:
- Log in to the server where the MySQL source database is located.
- Add lower_case_table_names=n under [mysqld] in the my.cnf file.
- After the modification, restart the source database during a non-service period.
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
