[MySQL] Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd

실행환경
Desktop	조립식
CPU	Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz 3.40GHz
Memory	8.00 GB
OS	Windows 7 Professional K 64bit
Java	1.8.0_05
MySQL	Ver 14.14 Distrib 5.6.19, for Win64

문제점

컴퓨터 강제종료시 발생하는 것 같다. 

error log

2014-07-09 11:01:56 2280 [Note] Plugin 'FEDERATED' is disabled.
2014-07-09 11:01:56 1248 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.
2014-07-09 11:01:56 2280 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-07-09 11:01:56 2280 [Note] InnoDB: The InnoDB memory heap is disabled
2014-07-09 11:01:56 2280 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-07-09 11:01:56 2280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-07-09 11:01:56 2280 [Note] InnoDB: Not using CPU crc32 instructions
2014-07-09 11:01:56 2280 [Note] InnoDB: Initializing buffer pool, size = 165.0M
2014-07-09 11:01:56 2280 [Note] InnoDB: Completed initialization of buffer pool
2014-07-09 11:01:56 2280 [Note] InnoDB: Highest supported file format is Barracuda.
2014-07-09 11:01:56 2280 [Note] InnoDB: The log sequence numbers 1810266 and 1810266 in ibdata files do not match the log sequence number 1810276 in the ib_logfiles!
2014-07-09 11:01:56 2280 [Note] InnoDB: Database was not shutdown normally!
2014-07-09 11:01:56 2280 [Note] InnoDB: Starting crash recovery.
2014-07-09 11:01:56 2280 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-07-09 11:01:56 2280 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bis/busstop uses space ID: 2 at filepath: .\bis\busstop.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.

해결방안

C:\Program Files\MySQL\MySQL Server 5.6\data\mysql 이나 data가 저장되는 폴더의 mysql폴더로 이동한다.

폴더를 하나 생성하고 아래와 같은 파일 이동시킨다. 즉 백업하고서 mysql 을 다시 실행 시킨다.

innodb_index_stats.frm 
innodb_index_stats.ibd 
innodb_table_stats.frm 
innodb_table_stats.ibd 
slave_master_info.ibd 
slave_relay_log_info.frm 
slave_relay_log_info.ibd 
slave_worker_info.frm 
slave_worker_info.ibd

참고사이트 링크1, 링크2, 링크3