Re: How to recover InnoDB tables if I only have idb files (innodb_file_per_table = 1)

[gaurav jain]

Hi all,
When I am trying to start mysql using "mysqld --console" I am getting the following trace

080627 12:58:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080627 12:58:19 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 2 2646831040.
InnoDB: Doing recovery: scanned up to log sequence number 2 2646948380
080627 12:58:21 InnoDB: Starting an apply batch of log records to the database.
..
InnoDB: Progress in percents: 4 5 6 7 8 9 10 11 12 13 14 15 16 080627 12:58:21In
noDB: Error: trying to access a stray pointer 00000000
InnoDB: buf pool start is at 01214000, end at 01A14000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery,
InnoDB: you can look from section 6.1 at http://www.innodb.com/ibman.html
InnoDB: how to force recovery.
080627 12:58:22InnoDB: Assertion failure in thread 4076 in file e:\build\mysql-4
.1.19-build\mysql-4.1.19\innobase\include\buf0buf.ic line 262
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
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: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 920 stopped in file .\os\os0sync.c line 309

Anyone who has faced this problem?
And the solution to recover my database.

This is really urgent.

Thanks