mysql不会工作easyphp xampp

Question

我试图用EasyPHP或XAMPP创建本地Web服务器。当我第一次运行XAMPP或EasyPHP时，一切正常。在PhpMyAdmin中，我创建了一个数据库并执行我所需要的操作。但是当我下次尝试运行程序时，MySQL将无法工作。 我发现只有一种方法可以让MySQL再次工作 - 删除ibdata1文件，但通过这样做，我松了我的MySQL数据。

对不起，我的英文，谢谢你的回答！

P.S. 有我的MySQL错误日志文件。

>  2013-11-23 14:46:58 1092 [Note] Plugin 'FEDERATED' is disabled. 
>  2013-11-23 14:46:58 1814 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. 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: The InnoDB memory heap is disabled 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Compressed tables use zlib 1.2.3 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Not using CPU crc32 instructions 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Initializing buffer pool, size = 16.0M 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Completed initialization of buffer pool 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Highest supported file format is Barracuda. 
>  2013-11-23 14:46:58 1092 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the 
> ib_logfiles! Are you sure you are using the right ib_logfiles to start 
> up the database. Log sequence number in the ib_logfiles is 1600607, 
> logsequence numbers stamped to ibdata file headers are between 1600617 
> and 1600617. 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: The log sequence numbers 1600617 and 1600617 in ibdata files do not match the log sequence 
> number 1600607 in the ib_logfiles! 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Database was not shutdown normally! 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Starting crash recovery. 
>  2013-11-23 14:46:58 1092 [Note] InnoDB: Reading tablespace information from the .ibd files... 
>  2013-11-23 14:46:58 1092 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace 
> mysql/slave_relay_log_info uses space ID: 3 at filepath: 
> .\mysql\slave_relay_log_info.ibd. Cannot open tablespace 
> wordpress/wp_terms which uses space ID: 3 at filepath: 
> .\wordpress\wp_terms.ibd 
>  InnoDB: Error: could not open single-table tablespace file .\wordpress\wp_terms.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. 

Answer 1

我不知道这个问题的原因，但这里是我如何解决它。

我已经通过将innodb_file_per_table = OFF添加到我的MySQL配置文件中来禁用每个表的innodb文件。

然后对于每个被破坏的表：

[ERROR] InnoDB: Could not find a valid tablespace file for '<base>/<table>'

我创造我的MySQL安装文件夹data一个文件夹<base>。并在一个名为<table>.frm的空文件中。

然后连接您的数据库并做DROP TABLE <base>.<table>。

的DROP应该是成功的，即使错误日志显示一个错误：

InnoDB: Failed to find tablespace for table '"<base>"."<table>"' in the cache. Attempting to load the tablespace with space id 255.

[编辑]如果你在一个基地有很多表，你还可以创建只有文件夹<base>在data/目录中，并发行DROP DATABASE <base>。 ！

/\你将失去一个没有被损坏