mysql數據庫無法啟動恢復 mysql數據庫崩潰恢復 mysql數據庫恢復


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)


免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM