On Tue, Jan 13, 2009 at 6:06 PM, Dan wrote:
> On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
> wrote:
>
>> This sounds like you need to raise max_allowed_packet for mysqldump
>> (and possibly mysqld) - these are separate settings for both the
>> client and the server. You can do this via the
On Tue, 13 Jan 2009 18:34:44 -0600, Andrew Garner
wrote:
> This sounds like you need to raise max_allowed_packet for mysqldump
> (and possibly mysqld) - these are separate settings for both the
> client and the server. You can do this via the my.cnf (or ~/.my.cnf)
> or specify it as an option on
This sounds like you need to raise max_allowed_packet for mysqldump
(and possibly mysqld) - these are separate settings for both the
client and the server. You can do this via the my.cnf (or ~/.my.cnf)
or specify it as an option on the command line "mysqldump --opt ...
--max_allowed_packet=1G dbna
I'm also having a similar issue with some tables I've been trying to dump
(total data set is around 3TB). I'm dumping directly from one host to
another (mysqldump -hSOURCE DATABASE | mysql -hLOCALHOST DATABASE) using
mysql 4.1.22. One system is Solaris 10 SPARC, while the other is Solaris 10
x64
On Mon, 12 Jan 2009 16:25:12 +0530, Chandru wrote:
> Hi,
>
> please increase your interactive_timeout variable to some big number and
> also try to log the erros if any thing by using the command:
>
> mysqldump --opt db_name > db_name.sql -p 2>>bkp.err
>
> check if you get some thing in the b
Hi,
please increase your interactive_timeout variable to some big number and
also try to log the erros if any thing by using the command:
mysqldump --opt db_name > db_name.sql -p 2>>bkp.err
check if you get some thing in the bkp.err file.
Regards,
Chandru,
www.mafiree.com
On Mon, Jan 12, 20
