MySQL Forums
Forum List  »  InnoDB

How to restore innoDB tables without ibdata1 with innodb_file_per_table=1
Posted by: Olag Ulga
Date: September 13, 2011 01:04AM


We backed up the database directory with .frm and .ibd files. The ibdata1 file is lost. In the config there is innodb_file_per_table=1. This means the data should be in the directory... Copy the directory and start mysql didn't work (see the log at the end).

Is there a possibility to restore the database?

Thank for your help

Working with: 5.1.40 (5.1.40-community-log, Win32)

110913 8:41:44 [Note] Plugin 'FEDERATED' is disabled.
110913 8:41:46 InnoDB: Started; log sequence number 0 1698675883
110913 8:41:46 [Note] Event Scheduler: Loaded 0 events
110913 8:41:46 [Note] C:\M2011\MySQL-Prog\bin32\mysqld.exe: ready for connections.
Version: '5.1.40-community-log' socket: '' port: 3306 MySQL Community Server (GPL)
InnoDB: Error: tablespace id is 941 in the data dictionary
InnoDB: but in file .\fib00001\d_lsvlauf_pos.ibd it is 161!
110913 8:42:09 InnoDB: Assertion failure in thread 6132 in file .\fil\fil0fil.c line 603
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: about forcing recovery.
110913 8:42:09 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 444647 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xbd04db0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
005E214D mysqld.exe!?check_next_symbol@Gis_read_stream@@QAE_ND@Z()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0BD53D60=SHOW TABLE STATUS FROM `fib00001`
The manual page at contains
information that should help you find out what is causing the crash.
InnoDB: Thread 448 stopped in file .\os\os0sync.c line 574
InnoDB: Thread 3804 stopped in file .\os\os0sync.c line 271

Options: ReplyQuote

Written By
How to restore innoDB tables without ibdata1 with innodb_file_per_table=1
September 13, 2011 01:04AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.