Luke Vanderfluit wrote:
Hi.
I've got mysql 4.0.18 installed on a sun X4100 running solaris.
This is just a 32 bit version of mysql.
I've reverted back to this version after trying mysql 5, 4.0.26 and
4.0.18 64bit.
Those versions were all unstable on 64bit, that is, the server would
just go away for no apparent reason.
This would ofter rear it's head when importing a dump file, the dump
file I need to import is around 10 GIG, but also at other unpredictable
times.
I have this same database running on another machine running solaris,
with no problems, except speed/performance.
This other machine is the one that produces the dump file I'm trying to
import.
It does that with the following command:
/usr/local/bin/mysqldump --opt --complete-insert
--max_allowed_packet=32M rt3 | bzip2 -9 > rt3.out-`date +\%Y\%m\%d-\%H`.bz2
I'm trying to restore the file on the new machine and I'm getting a
'max_allowed_packet' error:
ERROR 1153 at line 162: Got a packet bigger than 'max_allowed_packet
I've tried different settings for this in my.cnf, from 32 up to 1024M,
and I still get the error.
Is there anything I can do to remedy this?
Kind regards.
Yes in principle rules are:
http://www.mysql.com/news-and-events/newsletter/2003-08/a0000000216.html
but you *must* enforce them on server too (not just on mysqldump):
http://dev.mysql.com/doc/refman/4.1/en/packet-too-large.html
so either run second mysql with: mysqld --max_allowed_packet=32M
or edit your my.cnf and restart mysqld:
You can also use an option file to set max_allowed_packet. For
example, to set the size for the server to 16MB, add the following lines
in an option file:
[mysqld]
max_allowed_packet=32M
Before MySQL 4.0, use this syntax instead:
[mysqld]
set-variable = max_allowed_packet=32M
or (if you're trying from mysql console then run it with)
mysql --max_allowed_packet=32M
HTH
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
