天天看點

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)

繼續閱讀