的Windows 8.1 Wampserver MySQL將無法運行

Question

我安裝了Windows 8.1，然後我重新安裝wampserver和一切工作..直到我得到一個橙色的是，由於沒有運行我的MySQL服務器....

Wampserver 2.4

的MySQL 5.6.12

PHP 5.4.12

的Apache 2.4.4

這是日誌文件

2013-12-18 10:00:00 904 [Note] Plugin 'FEDERATED' is disabled. 
2013-12-18 10:00:00 904 [Note] InnoDB: The InnoDB memory heap is disabled 
2013-12-18 10:00:00 904 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
2013-12-18 10:00:00 904 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2013-12-18 10:00:00 904 [Note] InnoDB: Not using CPU crc32 instructions 
2013-12-18 10:00:00 904 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2013-12-18 10:00:00 904 [Note] InnoDB: Completed initialization of buffer pool 
2013-12-18 10:00:00 904 [Note] InnoDB: Highest supported file format is Barracuda. 
2013-12-18 10:00:00 904 [Note] InnoDB: The log sequence numbers 2283844 and 2283844 in ibdata files do not match the log sequence number 2484632 in the ib_logfiles! 
2013-12-18 10:00:00 904 [Note] InnoDB: Database was not shutdown normally! 
2013-12-18 10:00:00 904 [Note] InnoDB: Starting crash recovery. 
2013-12-18 10:00:00 904 [Note] InnoDB: Reading tablespace information from the .ibd files... 
2013-12-18 10:00:00 904 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace airbnb/amenities uses space ID: 6 at filepath: .\airbnb\amenities.ibd. Cannot open tablespace webotrip/amenities which uses space ID: 6 at filepath: .\webotrip\amenities.ibd 
InnoDB: Error: could not open single-table tablespace file .\webotrip\amenities.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. 

Answer 1

我找到了解決辦法

1. 備份您的\ WAMP \ BIN \ mysql的\ mysql5.6.12 \ data文件夾，以防萬一。

2. 左擊wampmanager圖標 - >的MySQL - >的my.ini（編輯MySQL的配置文件中）

並添加以下行到wampmysqld部[wampmysqld]（或[mysqld的]如果您不必[wampmysqld]）

innodb_force_recovery = 1

然後保存的my.ini

LEF t點擊wampmanager圖標 - > MySQL - >服務 - >重新啓動服務

給它一分鐘做它的恢復，然後再次檢查mysql錯誤日誌，看它是否恢復了數據庫。

左擊wampmanager圖標 - >的MySQL - >的my.ini（編輯MySQL的配置文件中）

現在除去innodb_force_recovery = 1個參數預先加入你。