Posted By: tidus on October 22, 2013, 7:56 am | Post: 4 |
Hi,
Take a backup of Ampps\mysql\data folder before doing anything. The workaround/solution can be found here itself in log. Quote 2013-10-19 06:50:53 3712 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace gazelle/api_applications uses space ID: 5 at filepath: .\gazelle\api_applications.ibd. Cannot open tablespace mysql/slave_worker_info which uses space ID: 5 at filepath: .\mysql\slave_worker_info.ibd InnoDB: Error: could not open single-table tablespace file .\mysql\slave_worker_info.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.
----------------------- Follow AMPPS on, Twitter : https://twitter.com/AMPPS_Stack Facebook : http://www.facebook.com/softaculousampps Google+ : https://plus.google.com/+AmppsStack |