InnoDB Storage Engine-FAQ fix

Error 1: InnoDB:Error:page Log Sequence Number 2363194248

Innodb:is in the future! Current system log sequence number 78250719.

Innodb:your database may corrupt or we have copied the InnoDB

Innodb:tablespace but not the InnoDB log files.

WORKAROUND: If the server does not have any backups, you can only force InnoDB to restore itself

You can add the following line to the section of [mysqld] your option file before restarting the server:

[Mysqld]innodb_force_recovery = 1

Innodb_force_recovery has 0-6 six values, different values have different functions

0 By default (normal startup without forced recovery).

• lets the server run even if it detects a corrupt page. Tries to Make 

• prevents the master Thread and any purge threads from running. If a crash would occur during the purgeoperation, this recovery value prevents it.

• does not run Transaction rollbacks after crash recovery.

• prevents insert buffer merge operations. If they would cause a crash, does not do them. Does not calculate tablestatistics. This value can permanently corrupt data files. After using the this value, is prepared to drop and recreate all secondary indexes.

• does not look At undo Logs when starting the Database: 

• Does not does the redo log roll-forward in connection with recovery. This value can permanently corrupt data files. Leaves database pages in a obsolete state, which in turn could introduce more corruption to b-trees and other database St Ructures.

These are the official explanations from MySQL. Http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

It is said that MySQL third-party Percona has a more efficient recovery tool

Percona has a Data Recovery Toolkit That would does all this to efficiently than I am saying it.

Error 2: How to safely change MySQL innodb variable ' innodb_log_file_size '?

Edit/ETC/MY.CNF content as follows

innodb_buffer_pool_size=2g

innodb_log_file_size=100m

Then restart MySQL with the following error:

110216 9:48:41 innodb:initializing buffer pool, size = 128.0M
110216 9:48:41 innodb:completed initialization of buffer pool
InnoDB:Error:log file./ib_logfile0 is of different size 0 5242880 bytes
Innodb:than specified in the. cnf file 0 33554432 bytes!
110216 9:48:41 [ERROR] Plugin ' InnoDB ' init function returned ERROR.
110216 9:48:41 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.

Workaround:           

2. mysql -uroot -p... -e"SET GLOBAL innodb_fast_shutdown = 0"

4. service mysql stop

6. rm -f /var/lib/mysql/ib_logfile[01]

8. service mysql start

See some articles on the internet, said it is best to add this option

SET GLOBAL innodb_max_dirty_pages_pct = 0; (Dirty page Listen to my colleague explaining that it is memory data)

by default,innodb_max_dirty_pages_pctis (MySQL 5.5+) or prior (MySQL 5.5). Setting this to zero keeps the number of dirty pages under 1% of the InnoDB Buffer Pool. performingservice mysql stop, does this anyway. In addition, a shutdown would finish up any remaining items in the Redo log.

I am using Google search, found the following link, there are a lot of MySQL problem summary http://dba.stackexchange.com/search?q=ib_logfile0

This article is from the "The-way-to-cloud" blog, make sure to keep this source http://iceyao.blog.51cto.com/9426658/1559645

InnoDB Storage Engine-FAQ fix