MySQL Forums :: InnoDB :: All Innodb tables using seperate ibd, but ibdata1 still being modified?


Advanced Search

All Innodb tables using seperate ibd, but ibdata1 still being modified?
Posted by: Kyle Bresin ()
Date: August 12, 2011 01:33PM

I've inherited a large MySQL 5.1 installation with 1000+ InnoDB tables in use across multiple databases.

I pulled out a list of all InnoDB tables from information_schema, and checked to see if those tables had an .ibd file.

Every single one has one. Yet every time there is an update to any of the InnoDB tables the shared ibdata1 still has it's mtime advanced?

Also, md5sums take of ibdata1 over the course of the day show that the values inside the file *are* changing (not the size obviously).

I'd really like to delete the ibdata1 file, but the fact that it is still being touched by MySQL makes me nervous.

Is there a way to proceed that doesn't involve me re-importing all my InnoDB tables "just to be sure"?

Some logical explanation why MySQL is touching the file perhaps?

Thanks for reading!



Edited 3 time(s). Last edit at 08/12/2011 01:55PM by Kyle Bresin.

Options: ReplyQuote


Subject Views Written By Posted
All Innodb tables using seperate ibd, but ibdata1 still being modified? 3261 Kyle Bresin 08/12/2011 01:33PM
Re: All Innodb tables using seperate ibd, but ibdata1 still being modified? 1396 Rick James 08/13/2011 02:50PM
Re: All Innodb tables using seperate ibd, but ibdata1 still being modified? 1165 Kyle Bresin 08/18/2011 07:53AM
Re: All Innodb tables using seperate ibd, but ibdata1 still being modified? 1585 Rick James 08/19/2011 07:57AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.