寻找错误日志，日志默认在： c:\programdata\mysql\mysql server 5.6\data\li-pc.err 错误日志如下： innodb: error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdinnodb: we do not continue the crash recovery, because
寻找错误日志，日志默认在：
c:\programdata\mysql\mysql server 5.6\data\li-pc.err
错误日志如下：
innodb: error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdinnodb: we do not continue the crash recovery, because the table may becomeinnodb: 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 cannotinnodb: 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 normalinnodb: crash recovery and ignore that table.innodb: 3) if the file system or the disk is broken, and you cannot removeinnodb: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfinnodb: and force innodb to continue crash recovery here.140424 9:34:06 [note] plugin 'federated' is disabled.140424 9:34:06 innodb: warning: using innodb_additional_mem_pool_size is deprecated. this option may be removed in future releases, together with the option innodb_use_sys_malloc and with the innodb's internal memory allocator.140424 9:34:06 innodb: the innodb memory heap is disabled140424 9:34:06 innodb: mutexes and rw_locks use windows interlocked functions140424 9:34:06 innodb: compressed tables use zlib 1.2.3140424 9:34:06 innodb: cpu does not support crc32 instructions140424 9:34:06 innodb: initializing buffer pool, size = 49.0m140424 9:34:06 innodb: completed initialization of buffer pool140424 9:34:06 innodb: highest supported file format is barracuda.innodb: the log sequence number in ibdata files does not matchinnodb: the log sequence number in the ib_logfiles!140424 9:34:06 innodb: database was not shut down normally!innodb: starting crash recovery.innodb: reading tablespace information from the .ibd files...140424 9:34:06 [error] innodb: innodb: error: attempt to open a tablespace previously opened.previous tablespace hibernate/teacher uses space id: 2 at filepath: .\hibernate\teacher.ibdcannot open tablespace mysql/innodb_index_stats which uses space id: 2 at filepath: .\mysql\innodb_index_stats.ibdinnodb: error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibdinnodb: we do not continue the crash recovery, because the table may becomeinnodb: 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 cannotinnodb: 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 normalinnodb: crash recovery and ignore that table.innodb: 3) if the file system or the disk is broken, and you cannot removeinnodb: the .ibd file, you can set innodb_force_recovery > 0 in my.cnfinnodb: and force innodb to continue crash recovery here.
解决方案：仅从上述信息看，是innodb 的数据文件损坏，在我安装mysql的数据目录：c:\programdata\mysql\mysql server 5.6\data下,一般来说，直接删除ibdata1, ib_logfile0, .. 等innodb的文件，让mysql自动重建即可。