Not sure about the size of your dump, but, have you tried to set the new
value on the server and client side? you can increase max_allowed_packet up
to 1G. Let us know after you tried that, and maybe other guys have another
solution to share...
--
*Wagner Bianchi, +55.31.8654.9510*
Oracle ACE Director
https://apex.oracle.com/pls/otn/f?p=19297:4:105567988301604::NO:4:P4_ID:4541,
MySQL Certified Professional
Percona MySQL Forum http://www.percona.com/forums/ Community V.I.P.
Email: m...@wagnerbianchi.com
Skype: wbianchijr
2015-06-16 10:28 GMT-03:00 Manivannan S manivanna...@spanservices.com:
Hi,
When we are trying to restore the dump file, we got an error like Got a
packet bigger than max_allowed_packet. Then we increased
max_allowed_packet variable size and passed along with MySQL restore
command.
mysql -max_allowed_packet=128M -uusername -p /path/file.sql
After increasing the variable size also we got same error. Later we
converted the value from 128M to 134217728 Bytes, then restore done
successfully.
In case my.cnf, when we pass the value for MySQL variables its accepting
either in bytes, K, M or G.
Why it doesn't consider128M in MySQL prompt while restoring the dump file?
Regards
Manivannan S
DISCLAIMER: This email message and all attachments are confidential and
may contain information that is Privileged, Confidential or exempt from
disclosure under applicable law. If you are not the intended recipient, you
are notified that any dissemination, distribution or copying of this email
is strictly prohibited. If you have received this email in error, please
notify us immediately by return email to mailad...@spanservices.com and
destroy the original message. Opinions, conclusions and other information
in this message that do not relate to the official of SPAN, shall be
understood to be nether given nor endorsed by SPAN.
