Help Center/ Data Replication Service/ Troubleshooting/ Solutions to Failed Check Items/ Database Parameters/ Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters

Updated on 2024-11-30 GMT+08:00

View PDF

Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters

During MySQL migration, if the source database contains trigger names with non-ASCII characters, the migration will fail.

Failure Cause

The source database cannot contain trigger names with non-ASCII characters.

Handling Suggestion

Method 1: Click Previous to return to the Select Migration Type page. Do not select triggers whose names contain non-ASCII characters.
Method 2: Change the trigger name in the source database and perform the pre-check again.

Parent topic: Database Parameters

Previous topic: Checking Whether the lc_monetary Values of the Source and Destination Databases Are the Same

Next topic: Checking Whether the Source Database Collections Contain More Than 10 Indexes

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.