mysql错误InnoDB:Attemptedtoopenapreviouslyopenedtablespace.

冷不防 2022-07-11 08:19 197阅读 0赞

2017-01-20 21:14:53 32 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2017-01-20 21:14:53 32 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-01-20 21:14:53 32 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2017-01-20 21:14:53 32 [Note] InnoDB: Memory barrier is not used
    2017-01-20 21:14:53 32 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-01-20 21:14:53 32 [Note] InnoDB: Using generic crc32 instructions
    2017-01-20 21:14:53 32 [Note] InnoDB: Initializing buffer pool, size = 256.0M
    2017-01-20 21:14:53 32 [Note] InnoDB: Completed initialization of buffer pool
    2017-01-20 21:14:53 32 [Note] InnoDB: Highest supported file format is Barracuda.
    2017-01-20 21:14:53 32 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1755003 in the ib_logfiles!
    2017-01-20 21:14:53 32 [Note] InnoDB: Database was not shutdown normally!
    2017-01-20 21:14:53 32 [Note] InnoDB: Starting crash recovery.
    2017-01-20 21:14:53 32 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2017-01-20 21:14:53 32 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace medicalsale/salesman uses space ID: 13 at filepath: .\medicalsale\salesman.ibd. Cannot open tablespace phpmyadmin/pma__history which uses space ID: 13 at filepath: .\phpmyadmin\pma__history.ibd
    InnoDB: Error: could not open single-table tablespace file .\phpmyadmin\pma__history.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.

出现这个问题好几次了，每次的解决问题都是重新弄下Mysql.  
我用的是XAMPP 3.2.2,今天终于找到解决办法了  
在D:\\xampp\\mysql\\bin下面的my.ini中添加  
**innodb\_force\_recovery = 1**