You’ve probably had some troubles with the shared InnoDB tablespace stored in the ibdata file. Especially when it has grown for some reasons and reached a critical size.
This behavior occurs in some cases, due to excessive rollback segments growth or during a migration from a unique shared tablespace to a file-per-table configuration for example.
In this post, I would like to explain how to shrink the ibdata
file after an unwanted file growth in a file-per-table
Note that the process could be done without Trite but the tool avoids to write the script used to transport tables yourself.
Here is a sample of the InnoDB configuration:
innodb_data_file_path = ibdata1:100M:autoextend innodb_file_per_table
And the status of your datafiles in the datadir directory:
drwx------ 2 mysql mysql 4,0K déc. 20 2012 …[Read more]