Keith, When you copied the database, you need recreate de logfiles and the sequences. Then, startup the database. 1) clean your actually log files ( backup to another side) 2) When the database startup automatically recreate the log files and sequence.
Send feedback about it. Regards, Juan On 6/5/07, Keith Murphy <[EMAIL PROTECTED]> wrote:
This: 070605 15:07:27 InnoDB: Error: page 170144 log sequence number 71 2823728422 InnoDB: is in the future! Current system log sequence number 71 452597657. InnoDB: Your database may be corrupt. 070605 15:07:28 InnoDB: Error: page 61253 log sequence number 71 910331446 InnoDB: is in the future! Current system log sequence number 71 452599188. InnoDB: Your database may be corrupt. 070605 15:07:29 InnoDB: Error: page 56830 log sequence number 71 3280625836 InnoDB: is in the future! Current system log sequence number 71 452601958. InnoDB: Your database may be corrupt. shows up in the error log on a new server we are setting up. This system had the data copied to it from another db server. On the old server we locked the tables (flush tables with read lock), did a "show slave status" to get the bin log position and copied the relevant directories (50gigs) to the new server. Then we started up the new server. Everything appears to be going fine. Replication status showed that it was roughly 5000 seconds behind, but it synced up so that it is now 0 seconds behind. However, the same error message is still being written to the error log. I am not familiar with it at all. There is some mention of it in google but the answers really don't make any sense to me. Any ideas? Thanks, Keith -- Database Administrator iContact 2635 Meridian Parkway, 2nd Floor Durham, North Carolina 27713 (o) 910-433-0786 (c) 850-637-3877
