Hello.
If you're not using per-file tablespace, the OPTIMIZing of the table
most probably won't decrease the size of ibdata files. See:
http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html
about how to decrease the size of the tablespace. OPTIMIZE table
is mapped to ALTER TABLE for InnoDB, and it recreates the whole table,
and most probably it will need a lot of space in the directory where
MySQL stores temporary files. In case this table is in a separated file,
you can dump it to another machine with mysqldump through the network,
drop it, and restore from the dump.
Rithish Saralaya wrote:
Hello.
We had an INNoDB table of very large size of 47 GB. Recently we deleted a
lot of rows from the table in order to reduce the size. The number of rows
now stands at 164,000+, however, the disk usage remains the same. I tried
OPTIMIZEing the table; but the optimize fails after running for about an
hour and a half.
We have 15 GB of free space left in /var/lib/mysql/ and about 14GB in /tmp/
The MySQL server is running on a 2*3.00 GHz linux box of 4 GB ram and 140 GB
HDD.
How will we able to regain the free space?
Comments/suggestions/flamings solicited.
Regards,
Rithish.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
