MySQL Forums
Forum List  »  MySQL Workbench

Re: InnoDB corrupt
Posted by: Peter Brawley
Date: January 31, 2018 03:37PM

> I would like to forcing recovery without interrupt website.

innodb force-recovery needs a restart

But first, is the answer to the log's question "you may have copied the InnoDB tablespace but not the InnoDB log files" yes? If not, you'll need to look in the log for any errors that preceded this one.

Did you take a shortcut upgrading from 5.5 to 5.6?

While we wait for those answers, for a way to fix the innodb_table_stats problem, I;d suggest running mysql_upgrade, and if it's still there then see See https://dba.stackexchange.com/questions/54608/innodb-error-table-mysql-
innodb-table-stats-not-found-after-upgrade-to-mys

Options: ReplyQuote


Subject
Views
Written By
Posted
157
January 31, 2018 01:24PM
Re: InnoDB corrupt
49
January 31, 2018 03:37PM


Sorry, only registered users may post in this forum.

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.