MySQL database failed to start recovery MySQL database crash recover MySQL database recovery

MySQL database failed to start recovery MySQL database crash recover MySQL database recovery

  Customer Name confidentiality   data type MySQL 5.5 innodb  data capacity mb  failure type Server power loss causes MySQL to fail to boot. The customer tries InnoDB crash recovery from parameter 1-6 invalid, 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 on Mysqld startup, please check Thatinnodb:yo ur my.cnf matches the ibdata files, which you had in Theinnodb:mysql server. Innodb:assertion failure in thread 11500 on file fil0fil.c line 4578innodb: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, E Veninnodb:immediately after the mysqld startup, there could beinnodb:corruption in the InnoDB tablespace. Please refer toinnodb:http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlinnodb:about forcing recovery.   Repair Results Database file after the analysis file found a garbage transaction, directly shielded, MySQL directly start oK. Export the backup to complete the recovery. Innodb:highest supported file format is Barracuda.InnoDB:Waiting for the background threads to startinnodb:5.5.46 start Ed 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)

MySQL database failed to start recovery MySQL database crash recover MySQL database recovery