最新案例
mysql数据库
mysql数据库无法启动恢复 mysql数据库崩溃恢复 mysql数据库恢复
2018-05-12 23:27:26
mysql数据库无法启动恢复 mysql数据库崩溃恢复 mysql数据库恢复
客户名称 保密
数据类型 mysql 5.5 innodb
数据容量 1500 MB
故障类型 服务器断电导致mysql无法启动。客户自己尝试innodb崩溃恢复从参数1-6无效、
InnoDB: for more information.
InnoDB: Error: trying to access page number 805281720 in space 0,
InnoDB: space name .\ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
InnoDB: Assertion failure in thread 11500 in file fil0fil.c line 4578
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.
修复结果 数据库文件发来后 分析文件发现有垃圾事务,直接屏蔽之 ,mysql直接启动OK。导出备份完成恢复。
InnoDB: highest supported file format is Barracuda.
InnoDB: Waiting for the background threads to start
InnoDB: 5.5.46 started; log sequence number 50311840278
[Note] Server hostname (bind-address): '0.0.0.0'; port: 3307
[Note] - '0.0.0.0' resolves to '0.0.0.0';
[Note] Server socket created on IP: '0.0.0.0'.
[Note] Event Scheduler: Loaded 0 events
[Note] D:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: ready for connections.
Version: '5.5.46-log' socket: '' port: 3307 MySQL Community Server (GPL)
客户满意 是 耗时半小时。
深圳极佳数据救援中心友情提醒：重要数据一定要勤备份，遇到数据丢失 数据损坏 等问题，要第一时间联系专业人士。
对于各类主流数据库，我们可以做最底层的数据恢复及数据修复，对于数据库的某些特定故障我们保证数据库100%原模原样恢复，无论多大的数据库都立等可取。
