Comments on: MySQL: ibdata files do not shrink on database deletion [innodb]

By: Starting Gate Solutions

Starting Gate Solutions — Thu, 11 Aug 2011 05:21:04 +0000

Just delete all your ib* files (after you backup of course) then restart and you’ll be good

By: Karl Schmidt

Karl Schmidt — Sun, 08 May 2011 00:02:58 +0000

This has me looking at postgresql

By: Karl Schmidt

Karl Schmidt — Sun, 08 May 2011 00:00:57 +0000

There is another way — kind of sketchy, but it works for me YMMV.

Change all the table types to myisam

Verify there are no innodb tables left.

turn of innodb with skip-innodb

remove innodb files

turn innodb back on

Change table types back to innodb

It is a real mess, but can be done on a working server with a short term risk due to the lack of ACID ..

This has me looking at

By: Marco Frattola

Marco Frattola — Mon, 06 Sep 2010 15:32:51 +0000

How about performances?
Is there any (public) comparison ?

tnx in advance
marco f.

By: MySQL: ibdata files do not shrink on database deletion [innodb] | Technology: Learn and Share « Tech Notes of Kevin Duane

Mon, 02 Aug 2010 20:38:58 +0000

[...] via MySQL: ibdata files do not shrink on database deletion [innodb] | Technology: Learn and Share. [...]

By: ibdata1 has grown to nearly 1GB. I need some solid advice here. - cPanel Forums

ibdata1 has grown to nearly 1GB. I need some solid advice here. - cPanel Forums — Mon, 17 May 2010 10:18:49 +0000

[...] I found a basic step-by-step for taking care of this here: MySQL: ibdata files do not shrink on database deletion [innodb] | Technology: Learn and Share And at some other forums I also found that it is probably safe to move and symlink ibdata1, but it [...]

By: joe

joe — Mon, 21 Sep 2009 10:28:27 +0000

Hi,
I follow all the instructions: I have now the database directory with .idb files, but… I still have the idbdata1 big and growing, now is about 5 time the data. How is it possible that exists both idbdata1 and *.idb files, working together?
REgards,
JS

By: vlastikw

vlastikw — Wed, 16 Sep 2009 19:07:29 +0000

Seems to be even easier: just add that option to my.cnf(my.ini) and run “mysqlcheck -u root –optimize –all-databases” and all your InnoDB tables should be converted to .idb files. Next, I’ll try to remove/unconfigure the ibdata file(s).

By: Mike

Mike — Fri, 11 Sep 2009 18:11:55 +0000

So what if I copied or moved all my .ibd files, then

ALTER TABLE tbl_name DISCARD TABLESPACE;

then did a full mysqldump, erased the huge innodb data file, then restored from the dump, then tried to import the .ibd files with

ALTER TABLE tbl_name IMPORT TABLESPACE;

By: maria

maria — Mon, 15 Jun 2009 16:12:38 +0000

How to obtain the data from ibdata1, ib_logfile0 and ib_logfile1?

By: Shahryar Ghazi

Shahryar Ghazi — Thu, 11 Jun 2009 14:17:09 +0000

after deleting large number of records or dropping tables you should optimize the tables (to defrag)

any new inserts will be inserted in the empty space made available by the previous drop/delete statements, so I guess there is not need to worry about data file size

By: adejo joseph

adejo joseph — Thu, 08 Jan 2009 12:06:55 +0000

good day sir/ma.i am joseph adejo from nigeria. a student of aptech world wide .i will love to know more about D.B.A becouse i have an interest to pursue it as a career.
please i will need guide lines from you to know how and what to be doing as an upcoming D.B.A.
THANKS ADEJO JOSEPH

By: colnector

colnector — Tue, 02 Sep 2008 18:31:37 +0000

Read Cory’s note above.
If you use phpMyAdmin you can easily mark the tables you want and choose to optimize them. This’ll clear the extra space abused by the ibd file.
Don’t forget to add innodb_file_per_table in your my.cnf file under [mysqld] section and restart the server.

By: Earnie

Earnie — Fri, 30 May 2008 14:45:26 +0000

Thank-you; a life saver. The only issue I has was I needed to add the -p on the import step and enter an empty password. Well, that, and I nearly ran out of disk space trying to backup the DB. I’m down from 65% use to 20% used; again thanks for the powerfully helpful page.

Good success to all,
Earnie – http://livingeasynetwork.com

By: Brill Pappin

Brill Pappin — Fri, 29 Feb 2008 23:27:32 +0000

It may be the transaction log. See:
http://dev.mysql.com/doc/refman/5.1/en/innodb-multi-versioning.html

By: carl

carl — Fri, 23 Nov 2007 15:09:35 +0000

you can’t delete the ibdata* files because they include innodb’s shared resources, in addition to any tables that might be stored there. if you delete those files, then your tables that you moved to their own files will no longer work.

By: Cory

Cory — Sat, 27 Oct 2007 00:44:17 +0000

Along the lines of what “Me” said… Make the change to my.cnf, restart mysql, but then run a query similar to:
OPTIMIZE NO_WRITE_TO_BINLOG TABLE [table1, table2 ... etc]

This will optimize all your tables and recreate the ibd files under their respective db directories.

I’m not sure at this point if you could just delete the main ibdata file because I didn’t try. Anyone else care to give it a shot?

By: Marijorge

Marijorge — Fri, 26 Oct 2007 16:30:41 +0000

Hi,
I´ve understood about the procedure above. But I have a question. Can I change the directory of creation .ibd files?
Thanks

By: Me

Me — Tue, 09 Oct 2007 08:12:20 +0000

Seems to be even easier: just add that option to my.cnf and run “mysqloptimize –all-databases” and all your InnoDB tables should be converted to .idb files. Next, I’ll try to remove/unconfigure the ibdata file(s).

By: Dario Souza

Dario Souza — Wed, 19 Sep 2007 04:16:13 +0000

Better yet, do an ALTER TABLE ENGINE=InnoDB; directly without converting it to/from myisam. That prevents you from losing foreign key constraints and some datatype conversions (int(12) to int(10) for instance) when you convert it to myisam.

By: hiutopor

hiutopor — Mon, 17 Sep 2007 08:31:24 +0000

Hi all!

Very interesting information! Thanks!

G’night

By: Chris Wiegand

Chris Wiegand — Fri, 07 Sep 2007 18:41:21 +0000

You can also do a ‘ALTER TABLE blah ENGINE=MyISAM; ALTER TABLE blah ENGINE=InnoDB;’ and it will effectively recreate the table in InnoDB (although you’ll need to script out any InnoDB features that aren’t supported in MyISAM like foreign keys and reapply then).

By: Chris Barber

Chris Barber — Tue, 26 Jun 2007 18:33:02 +0000

Worked pretty awesomely! After restoring the data, I had some issues with authenticating to the server, so I logged in to MySQL and flushed the privileges, then restarted MySQL:

$ mysql -u root -p
Enter password:
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
mysql> quit
Bye
$ /etc/init.d/mysql restart

Thanks for the help!