My Oracle Support Banner

InnoDB Error: "log sequence number is in the future" (Doc ID 1416063.1)

Last updated on APRIL 05, 2018

Applies to:

MySQL Server - Version 4.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to use InnoDB after a recovery, the following error occurs.

ERROR
-----------------------
120207 13:30:29 InnoDB: Error: page 573441 log sequence number 22 697197707
InnoDB: is in the future! Current system log sequence number 5 2916730276.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-recovery.html
InnoDB: for more information.

Changes

This issue will usually happen after one of the following changes:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 1. Restoring the Original Log Files
 2. Re-Initializing InnoDB Using Transportable Tablespaces
 3. Reloading the Data
 4. Convert to MyISAM
 5. Work Table
 6. Advanced Methods
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.