Question

MySql版本：5.5.24

注意： 每当我复制旧的“数据”文件夹时，MySql服务停止并将Wamp图标从绿色变为橙色。

解决方案我试过但没有运气：

等。

之前，我收到错误＃2002

服务器没有响应（或者没有正确配置本地MySQL服务器的套接字）

我确实尝试过搜索并应用了一些解决方案，但仍然没有运气。我仍然无法访问PhpMyadmin。我可以看到，而不是绿色，wampserver图标是橙色，因为MySql没有运行。

几天之后，我重新安装我的wampserver（相同版本）和phpmyadmin工作 ..但是当我复制mysql数据文件夹和文件（ibdata1，iblogfile0和iblogfile1）并重新启动服务我回到我的问题＃2002。

我的问题：

我想创建一个我的数据库的sql转储但我无法访问我的phpmyadmin因为MySql服务没有运行

问题：

如何通过复制必要的文件夹或文件将MySql数据库从wampserver数据恢复到新安装？
如果＃1不可能，是否可以通过控制台或其他任何方式创建 sql dump 而无需转到phpmyadmin？

注意：

在重新安装服务器之前，我有原始文件夹的完整备份。
我没有旧的sql转储来恢复。

MySQL日志：

141209 21:54:40 [Note] Plugin 'FEDERATED' is disabled.
141209 21:54:40 InnoDB: The InnoDB memory heap is disabled
141209 21:54:40 InnoDB: Mutexes and rw_locks use Windows interlocked functions
141209 21:54:40 InnoDB: Compressed tables use zlib 1.2.3
141209 21:54:40 InnoDB: Initializing buffer pool, size = 128.0M
141209 21:54:40 InnoDB: Completed initialization of buffer pool
141209 21:54:40 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 52664174
141209 21:54:40  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 56879679
141209 21:54:41  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 2383366, file name .\mysql-bin.000115
141209 21:54:42  InnoDB: Waiting for the background threads to start
141209 21:54:43  InnoDB: Assertion failure in thread 636 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
141209 21:54:43 InnoDB: 1.1.8 started; log sequence number 56879679
InnoDB: Thread 5328 stopped in file ibuf0ibuf.c line 3165

MySql wampserver恢复数据库

0 个答案: