MySQL Enterprise Backup (MEB) Fails; ERROR: Log scan was only able to reach to; InnoDB: log sequence number is in the future
Last updated on DECEMBER 14, 2017
Applies to:MySQL Enterprise Backup - Version 3.6 and later
Information in this document applies to any platform.
After restoring a backup made with MySQL Enterprise Backup, you see the following symptoms:
- When looking in the MySQL error log, InnoDB complains about the log sequence number being in the future:
111114 10:43:35 InnoDB: Error: page 9 log sequence number 6658378663
InnoDB: is in the future! Current system log sequence number 6658376936.
- When attempting to make a backup using MySQL Enterprise Backup using the restored database, the backup fails with an error like:
mysqlbackup: ERROR: Log scan was only able to reach to 6658377150,
but a copied database page was modified at 6658382845.
The database has been restored from a previous backup made with MySQL Enterprise Backup.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms