1) Max allowed packet is usually a replication not an important error. It
can be described as a "I can not find the information it is looking for
inside my search window" error.
2) It is more often associated with corruption then a true packet size
error. It also occasionally manifests when moving from 64 to 32 bit.  But
it is possible that it is just a max packet problem
3) using the client is more direct and less prone to error then using PHP
my admin
On Dec 4, 2014 2:34 PM, "Keith Smith" <techlists@phpcoderusa.com> wrote:

>
> Hi,
>
> I'm trying to import a file into MySql on CentOS 6.6 and mysql Server
> version: 5.1.73.
>
> Un compressed the file is 611,285,457b or about 610MB.  This is a
> production server and I am concerned about setting PHP upload_max_filesize
> that large.
>
> I tried to import via the command line and that failed.  Tried uploading
> as a gz via PhpMyAdmin... that failed also.  And I surely do not want to
> increase the memory allotted to PHP...
>
> I tried this:
>
> mysql --max_allowed_packet=650M -u root -p database < data.sql
>
> And received this error :  ERROR 1153 (08S01) at line 1370225: Got a
> packet bigger than 'max_allowed_packet' bytes
>
> Thanks in advance!!  Any suggestions?
>
> Keith
>
> --
> Keith Smith
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>