MySQL Forums
Forum List  »  Data Recovery

Error encountered during recovery
Posted by: Onjie Ambrocio
Date: May 26, 2008 02:37PM

Anyone encountered this error before:

InnoDB: ##########################################################
InnoDB: WARNING!
InnoDB: The log sequence number in ibdata files is higher
InnoDB: than the log sequence number in the ib_logfiles! Are you sure
InnoDB: you are using the right ib_logfiles to start up the database?
InnoDB: Log sequence number in ib_logfiles is 1 3642756760, log
InnoDB: sequence numbers stamped to ibdata file headers are between
InnoDB: 0 0 and 128 514916352.
InnoDB: ##########################################################
080527 3:50:05 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...
080527 3:50:06 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 3642756760.
InnoDB: Doing recovery: scanned up to log sequence number 1 3642769681
080527 3:50:06 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Error: page n:o stored in the page read in is 167776600, should be 283195!
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 283195.
InnoDB: You may have to recover from a backup.
080527 3:50:06 InnoDB: Page checksum 693858286, prior-to-4.0.14-form checksum 2860587123
InnoDB: stored checksum 1518102542, prior-to-4.0.14-form stored checksum 808596272
InnoDB: Page lsn 842609209 964713350, low 4 bytes of lsn at page end 808857984
InnoDB: Page number (if stored to page already) 167776600,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 808529970
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 283195.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.


We have a replication server that encountered this error and we cannot start the database properly because it keeps on restarting. What we did was refresh the data in the replication server even deleting the InnoDB files (logfile and datafiles) to make sure that the datafiles we will be using is not corrupted. But during the restoration, same error messages was seen on our ERR logfile. Kindly please shed light on this issue. Thanks.

Onjie Ambrocio

Options: ReplyQuote


Subject
Views
Written By
Posted
Error encountered during recovery
4593
May 26, 2008 02:37PM


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.