UC知道mysql崩溃
来源：百度知道 编辑：UC知道 时间：2024/05/15 08:30:38
今天换服务器了，把以前服务器的data文件夹拷了出来，新服务器上安装了原版本的mysql,把data目录放进去，可以启动服务，但无法链接
服务器系统:Windows2000
Mysql版本:5.0.22
LOG
091025 11:58:11 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 49 MB
InnoDB: Database physically writes the file full: wait...
091025 11:58:12 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 49 MB
InnoDB: Database physically writes the file full: wait...
091025 11:58:13 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...
091025 11:58:14 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 440954380.
InnoDB: Doing recovery: scanned up to log sequence numb
服务器系统:Windows2000
Mysql版本:5.0.22
LOG
091025 11:58:11 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 49 MB
InnoDB: Database physically writes the file full: wait...
091025 11:58:12 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 49 MB
InnoDB: Database physically writes the file full: wait...
091025 11:58:13 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...
091025 11:58:14 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 440954380.
InnoDB: Doing recovery: scanned up to log sequence numb
masql没升级吧？ 要是没升级这样出错了就你COPY文件的错误 一般数据库的文件都是自动生成 默认的 COPY是无效的
你这日志也就一些innodb的日志恢复信息，没显示出来到底为啥连接不了，你如果一直开着bin-log的话，在新系统里面直接导入bin-log日志应该就行了把
这真的很难》。。。。