Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Matthias L. (sc2gmx.at)
Date: Fri Jan 11 2008 - 08:37:21 CST
I searched google, find alot of tips, but none of the them was
After a db move with ibdata files, which cannot be dumped (cause of a table
failure) we made a hardcopy of the files and moved it onto the new server.
Eg. we copy ibdatafiles, the original my.cnf to the new server, we did NOT
copy the ib_logfiles (2) and the old bin files like hostname.0001 ..(we
tough its only for slave/master)
After starting the new mysql server, this follows in *.err log all the time.
The Database is runnning fine, but the log is to full after few seconds.
Re-dumping is not possible
Any ideas how i can fix it?
Check Tables means all is ok.
080111 14:42:20 InnoDB: Error: page 158199 log sequence number 3 974369182
InnoDB: is in the future! Current system log sequence number 0 3271712681.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
http://dev.mysql.com/doc/mysql/en/backing-up.html for more information.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql