MySQL Migration Wizard results in 'Found record bigger than max_allowed_packet'

Question

I am trying to migrate a database from MSSQL 2014 to MySQL 5.7 using Workbench 6.3 (CE) on a Windows machine. I have already set the value of max_allowed_packet to 1G in my.ini file. However, I'm still getting the error while trying to migrate the data. The table for which I am getting this error has only one record, and even the field, which I suspect is causing the issue, doesn't have that big of a value <results><result documentId="1" queryCode="AZ100" queryValue="I"/></results>. The field has nvarchar(max) as its data type in MSSQL which gets converted to LONGTEXT by MySQL wizard.

EDIT: I am not using any client here, just using the Workbench for migration. Also, in the migration log it indicates that it has detected the new max_allowed_packet value copytable]: Detected max_allowed_packet=1073741824

Thanks, Pratik

Possible duplicate of [MySQL Error 1153 - Got a packet bigger than 'max\_allowed\_packet' bytes](http://stackoverflow.com/questions/93128/mysql-error-1153-got-a-packet-bigger-than-max-allowed-packet-bytes) — Eric, Jun 29 '16 at 17:41

score 0 · Answer 1 · edited May 23 '17 at 12:32

0

Duplicate of MySQL Error 1153 - Got a packet bigger than 'max_allowed_packet' bytes

Please check the answer in the link and see if it solves your issue.

You probably have to change it for both the client (you are running to do the import) AND the daemon mysqld that is running and accepting the import.

edited May 23 '17 at 12:32

Community

1
1

answered Jun 29 '16 at 17:42

Eric

673
5
18

nvarchar(max) can take up to 2 GB. Maybe that's the issue? – Eric Jun 29 '16 at 23:02

MySQL Migration Wizard results in 'Found record bigger than max_allowed_packet'

1 Answers1