Cannot open tablespace resdb/t_wlkj_data_dict which uses space ID: 15 at filepath: ./resdb/t_wlkj_da

在启动mysql的时候报了如下错：

2019-06-05 14:07:16 28463 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-06-05 14:07:16 28463 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-05 14:07:16 28463 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-05 14:07:16 28463 [Note] InnoDB: Memory barrier is not used
2019-06-05 14:07:16 28463 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-06-05 14:07:16 28463 [Note] InnoDB: Using Linux native AIO
2019-06-05 14:07:16 28463 [Note] InnoDB: Using CPU crc32 instructions
2019-06-05 14:07:16 28463 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-06-05 14:07:16 28463 [Note] InnoDB: Completed initialization of buffer pool
2019-06-05 14:07:16 28463 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-05 14:07:16 28463 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do nothe log sequence number 1749012 in the ib_logfiles!
2019-06-05 14:07:16 28463 [Note] InnoDB: Database was not shutdown normally!
2019-06-05 14:07:16 28463 [Note] InnoDB: Starting crash recovery.
2019-06-05 14:07:16 28463 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-06-05 14:07:16 28463 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Preblespace xinyu2/aclass uses space ID: 15 at filepath: ./xinyu2/aclass.ibd. Cannot open tablespa/t_wlkj_data_dict which uses space ID: 15 at filepath: ./resdb/t_wlkj_data_dict.ibd
2019-06-05 14:07:16 7fa5d655e740  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./resdb/t_wlkj_data_dict.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.
190605 14:07:16 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysql/localhost.pid end

解决方法：
在配置文件my.cnf文件中增加如下配置

innodb_force_recovery = 1

然后重启mysql服务
重启完毕之后，删除新增加的那个配置，再次重启mysql服务。