MySQL Forums :: InnoDB :: innodb_log_file_size parameter


Advanced Search

Re: innodb_log_file_size parameter
Posted by: Jay Pipes ()
Date: June 28, 2005 01:51PM

When changing the innodb_log_file_size variable in my.cnf, first shut down the server, then rename your current ib_logfiles (you can just rename them with .BAK extensions. Then, make the configuration variable change in my.cnf. Then restart server. At this point, you can delete the old backup files if you need to or archive them away.

The reason you need to rename the current files is because, as the error log states, InnoDB expected the file to be 100MB, but it was 10MB. By renaming the ib_logfiles, you force InnoDB to create a new log file at your new specified size.

Since you stopped the server gracefully, and restarted, the new logfiles will contain all instructions InnoDB would need to restore your database back to a consistent state should another outage occur. This is why the old ib_logfiles can be chucked or archived.

Does this answer all your questions?

Jay Pipes
Community Relations Manager, North America, MySQL Inc.

Got Cluster? http://www.mysql.com/cluster
Personal: http://jpipes.com

Options: ReplyQuote


Subject Views Written By Posted
innodb_log_file_size parameter 8616 Mark Rigney 06/28/2005 01:07PM
Re: innodb_log_file_size parameter 15680 Jay Pipes 06/28/2005 01:51PM
Re: innodb_log_file_size parameter 4844 Mark Rigney 06/28/2005 01:53PM
Re: innodb_log_file_size parameter 4644 vishal thakkar 11/23/2008 03:30AM


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.