Help Center/ Data Replication Service/ User Guide (Kuala Lumpur Region)/ Troubleshooting/ Solutions to Failed Check Items/ Database Parameters/ Checking Whether the max_allowed_packet Value of the Destination Database Is too Small

Updated on 2022-08-16 GMT+08:00

View PDF

Checking Whether the max_allowed_packet Value of the Destination Database Is too Small

MySQL

**Table 1** Checking whether the max_allowed_packet value of the destination database is too small
Check Item	Whether the max_allowed_packet value of the destination database is too small
Description	A large amount of data cannot be written to the destination database during the migration because the max_allowed_packet value is smaller than 100 MB. As a result, the full migration failed.
Failure Cause and Handling Suggestion	Failure cause: The max_allowed_packet value of the destination database is too small, which may cause data fails to be written during the migration. Handling suggestions: Set the max_allowed_packet value greater than 100 MB

Parent topic: Database Parameters

Previous topic: Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database

Next topic: Checking Whether the Databases and Tables Exist

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.