List:General Discussion« Previous MessageNext Message »
From:Dan Nelson Date:February 7 2001 11:38pm
Subject:Re: table too big to dump?
View as plain text  
In the last episode (Feb 07), Brian Reichert said:
> I apologize if this has been discussed already, but I quick poke
> at the archives didn't reveal anything.
> 
> We have a table that iamchk says is fine.  We are trying to get an
> SQL dump of this table.  But, we keep getting out-of-memory errors.
> I've tried several things, all to no avail, and I'm looking for
> advice/suggestions.
> 
>   # ls -l audit_trail_271.*
>   -rw-rw----  1 root  wheel  1486838307 Nov 10 05:26 audit_trail_271.ISD
>   -rw-rw----  1 root  wheel    84807680 Nov 10 05:26 audit_trail_271.ISM
>   -rw-rw----  1 root  wheel        9060 Oct 25 05:06 audit_trail_271.frm
> 
> When I try to do a mysqldump on the localhost, I get an out-of-memory
> error:
> 
>   # mysqldump -uroot -proot customer audit_trail_271
>   mysqldump: Out of memory (Needed 8164 bytes)
>   mysqldump: Got error: 2008: MySQL client run out of memory

It's probably trying to read the whole table into memory.  Try adding
"--opt" to the mysqldump commandline.

-- 
	Dan Nelson
	dnelson@stripped
Thread
table too big to dump?Brian Reichert7 Feb
  • Re: table too big to dump?Brian Reichert8 Feb
  • Re: table too big to dump?Peter Skipworth8 Feb
  • Re: table too big to dump?Dan Nelson8 Feb
    • Re: table too big to dump?Brian Reichert8 Feb
  • Re: table too big to dump?Steve Ruby8 Feb
  • Re: table too big to dump?Vivek Khera8 Feb