MySQL Forums
Forum List  »  InnoDB

Re: The ibdata1 file grows too large with innodb_file_per_table
Posted by: Rick James
Date: October 10, 2012 09:33PM

Some possibilities...

1. Have .ibd files been created since you set file_per_table? (A restart is needed to make it take effect.)

2. Are there tables that have not been converted to their own tablespace? (That requires an ALTER TABLE foo ENGINE=InnoDB, after the setting.)

3. Certain operations still use ibdata1 as a scratch area. Did you do a huge transaction? The "undo" or "redo" might have built up in ibdata1. (I forget the details.)

4. I recommend against using autocommit = 0. It can lead to long running transactions that you forget to COMMIT.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: The ibdata1 file grows too large with innodb_file_per_table
1295
October 10, 2012 09:33PM


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.