为什么 MySql 服务无法在 WAMP 上启动？答案

【问题标题】：Why MySql service doesn't start on WAMP?为什么 MySql 服务无法在 WAMP 上启动？
【发布时间】：2014-02-04 17:55:04
【问题描述】：

wamp 有问题，昨天还好，今天服务不启动。我得到以下文件日志。

2014-02-04 11:49:26 944 [Note] Plugin 'FEDERATED' is disabled.
2014-02-04 11:49:26 944 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-04 11:49:26 944 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-04 11:49:26 944 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-04 11:49:26 944 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-04 11:49:26 944 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-04 11:49:26 944 [Note] InnoDB: Completed initialization of buffer pool
2014-02-04 11:49:26 944 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-04 11:49:28 1594  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:28 944 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/contacto'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:28 944 [ERROR] InnoDB: Tablespace open failed for '"bjc"."contacto"', ignored.
2014-02-04 11:49:28 1594  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:28 944 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/equipo'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:28 944 [ERROR] InnoDB: Tablespace open failed for '"bjc"."equipo"', ignored.
2014-02-04 11:49:28 1594  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:28 944 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/sidebar'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:28 944 [ERROR] InnoDB: Tablespace open failed for '"bjc"."sidebar"', ignored.
2014-02-04 11:49:28 1594  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:28 944 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/slider'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:28 944 [ERROR] InnoDB: Tablespace open failed for '"bjc"."slider"', ignored.
2014-02-04 11:49:29 944 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-04 11:49:29 944 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 965 in the data dictionary
InnoDB: but in file .\bjc\contenido_hijo.ibd it is 944!
2014-02-04 11:49:29 bcc  InnoDB: Assertion failure in thread 3020 in file fil0fil.cc line 794
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2014-02-04 11:49:53 5768 [Note] Plugin 'FEDERATED' is disabled.
2014-02-04 11:49:53 5768 [Note] InnoDB: The InnoDB memory heap is disabled
2014-02-04 11:49:53 5768 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-02-04 11:49:53 5768 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-02-04 11:49:53 5768 [Note] InnoDB: Not using CPU crc32 instructions
2014-02-04 11:49:53 5768 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-02-04 11:49:53 5768 [Note] InnoDB: Completed initialization of buffer pool
2014-02-04 11:49:53 5768 [Note] InnoDB: Highest supported file format is Barracuda.
2014-02-04 11:49:55 87c  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/contacto'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Tablespace open failed for '"bjc"."contacto"', ignored.
2014-02-04 11:49:55 87c  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/equipo'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Tablespace open failed for '"bjc"."equipo"', ignored.
2014-02-04 11:49:55 87c  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/sidebar'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Tablespace open failed for '"bjc"."sidebar"', ignored.
2014-02-04 11:49:55 87c  InnoDB: Operating system error number 2 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Could not find a valid tablespace file for 'bjc/slider'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2014-02-04 11:49:55 5768 [ERROR] InnoDB: Tablespace open failed for '"bjc"."slider"', ignored.
2014-02-04 11:49:56 5768 [Note] InnoDB: 128 rollback segment(s) are active.
2014-02-04 11:49:56 5768 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 965 in the data dictionary
InnoDB: but in file .\bjc\contenido_hijo.ibd it is 944!
2014-02-04 11:49:56 540  InnoDB: Assertion failure in thread 1344 in file fil0fil.cc line 794
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

我不知道这意味着什么。这是第一次发生在我身上，我还没有找到原因，或者可能没有找到足够的原因。希望您能够帮助我。谢谢

【问题讨论】：

你试过重启机器了吗？
@Scrooj 你是指电脑还是服务？
我的意思是 PC..通常这应该是解决方案..可能您的 PC 已经运行了几天
@Scrooj 没用。但我猜是因为一个表InnoDB: Could not find a valid tablespace file for 'bjc/contacto'. 但是如果我无法访问mysql，我该如何修复它？

标签： mysql wamp innodb

【解决方案1】：

我找不到解决此问题的方法。幸运的是，我有一个 sql 脚本作为导致此问题的数据库的备份，因此我删除了目录 C:\wamp\bin\mysql\mysql5.6.12\data 中具有数据库名称的文件夹，然后重新启动服务，并使用不同的名称恢复了数据库。我猜是操作系统损坏了这个文件导致我之前遇到了麻烦，我认为我最好的选择是备份并重新安装。谢谢您的帮助。建议：当您认为它们已准备好时，备份您的所有数据库。

【讨论】：