Not the answer you need?
Register and ask your own question!

InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace

shrenikp7shrenikp7 EntrantCurrent User Role Beginner
Why every time getting following message during --prepare? Is there any way to fix it and get clean prepare?

InnoDB: Starting crash recovery.
InnoDB: Page [page id: space=0, page number=2] log sequence number 2615513 is in the future! Current system log sequence number 2610831.
InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.

Comments

  • timurehtimureh Entrant Current User Role Novice
    I have the same problem...
    Did you solve this problem?
  • lorraine.pocklingtonlorraine.pocklington Percona Community Manager Legacy User Role Patron
    Hi tumureh

    Could you take a look at this blog post and see if that helps you resolve your issue? https://www.percona.com/blog/2013/09/11/how-to-move-the-innodb-log-sequence-number-lsn-forward/

    Let me know if you still need more assistance, thanks!
  • timurehtimureh Entrant Current User Role Novice
    Thanks Iorraine!

    I am using a percona xtradb cluster 5.7, master - master replication, maybe in my case it is normal to receive such messages?
    I also started initialize a cluster from the backup made by the innobackupex without the use apply-logs flag. Could this affect the occurrence of such errors?

    Regards.
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.