MySQL Forums
Forum List  »  Data Recovery

How to recover
Posted by: nicolas penel
Date: January 26, 2016 08:07AM


My mysql engine on xampp installation on windows machine doesn't start.

Here is the message found in the log file.

Any idea how to recover ?

2016-01-26 14:57:47 212 [Note] InnoDB: The log sequence numbers 170475919 and 170475919 in ibdata files do not match the log sequence number 180194948 in the ib_logfiles!
2016-01-26 14:57:47 212 [Note] InnoDB: Database was not shutdown normally!
2016-01-26 14:57:47 212 [Note] InnoDB: Starting crash recovery.
2016-01-26 14:57:47 212 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-26 14:57:47 212 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace osclass/oc_t_user uses space ID: 27 at filepath: .\osclass\oc_t_user.ibd. Cannot open tablespace phpmyadmin/pma__central_columns which uses space ID: 27 at filepath: .\phpmyadmin\pma__central_columns.ibd
InnoDB: Error: could not open single-table tablespace file .\phpmyadmin\pma__central_columns.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Thank you for any help



Options: ReplyQuote

Written By
How to recover
January 26, 2016 08:07AM
January 26, 2016 10:08AM
January 26, 2016 11:12AM
January 29, 2016 04:34PM

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.