My Oracle Support Banner

Various InnoDB Corruption or Crash After Restoring Physical Backup (including MEB) Into Non-Empty Data Directory (Doc ID 1998624.1)

Last updated on JANUARY 28, 2020

Applies to:

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


InnoDB Engine relies on logical consistency of data and log files.

InnoDB may experience unpredictable behavior including crashes and errors related to corruption in case if those files are mixed from different environments.

Example of an error:

2015-03-18 11:24:44 11904 [Note] InnoDB: Database was not shutdown normally!
2015-03-18 11:24:44 11904 [Note] InnoDB: Starting crash recovery.
2015-03-18 11:24:44 11904 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-03-18 11:24:44 11904 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace test/t uses space ID: 3695 at filepath: ./test/t.ibd. Cannot open tablespace test/#sql2-1ab0-5 which uses space ID: 3695 at filepath: ./test/#sql2-1ab0-5.ibd
2015-03-18 11:24:44 7fe914a04720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./test/#sql2-1ab0-5.ibd


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.