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 2025-08-07 GMT+08:00
View PDF
Share

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

In MySQL migration and synchronization scenarios, if the value of max_allowed_packet of the destination database is less than 100 MB, data cannot be written to the destination database. As a result, the full migration fails.

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 Suggestion

Set the max_allowed_packet value greater than 100 MB in the destination database.

  • For a self-managed database, run the following command to change the value. 
    SET GLOBAL max_allowed_packet=Size;
  • For an RDS for MySQL instance, change the parameter by referring to "Modifying Parameters of an RDS for MySQL Instance".
Parent topic: Database Parameters