… bitmap file name could stop the server starting if the innodb_data_home_dir variable didn’t have the path separator at… occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040. The INNODB_CHANGED_PAGES… issues. Bug fixed #1186831. Reduced the overhead from the Handle Corrupted Tables check as it was missing branch predictor annotations. Bug…
Post: Migrating between MySQL schemas with Percona Xtrabackup
June 10, 2013 By 2 Comments
… turn, load that data into and pollute the buffer pool. Note that this can be somewhat mitigated using innodb_old_blocks_time, but that is outside the scope of this post. Similarly, reloading the data will be…. This will allow you to compare and restore values (potentially corrupted via user error or other issues) with SQL rather than…
Post: How to recover table structure from InnoDB dictionary
April 22, 2013 By 4 Comments
To recover a dropped or corrupt table with Percona Data Recovery Tool for InnoDB you need two things: media with records(ibdata1, *.ibd… not an option: Table was dropped and innodb_file_per_table is ON Frm file corrupt, zeroed out, lost or SHOW CREATE TABLE crashes MySQL There is yet another source of information about the table structure – InnoDB…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch… #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and –no-data options, all secondary key definitions would be lost…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch… #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and –no-data options, all secondary key definitions would be lost…
Comment: How to recover table structure from InnoDB dictionary
May 8, 2013 By 4 Comments
… was saved then ibdata1 should be valid, maybe with some corruption. The tables structure you can get from the dictionary as… to do it http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:start . The biggest challenge here is to…_id for each table – http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:advanced_techniques#recovering_the_data_dictionary
Post: Is your MySQL buffer pool warm? Make it sweat!
April 16, 2013 By 6 Comments
…-pool –thread-pool-threads-count 100 –session-init-query \”set innodb_fake_changes=1\” > /var/log/playback.log 2>&1 & Our… option, we set the option innodb_fake_changes to prevent INSERTs, UPDATEs, and DELETEs from corrupting the data on the standby server. You will need Percona Server in order to use innodb_fake_changes. Thread…
Post: Recovering Innodb table Corruption
July 4, 2008 By 22 Comments
…in Innodb tablespace got corrupted. In such cases Innodb will typically print something like this: InnoDB: Database page corruption on disk or a failed InnoDB: …- when page in clustered key index is corrupted. It is worse compared to having data corrupted in secondary indexes, in which case simple…
Post: Data Corruption, DRBD and story of bug
November 29, 2010 By 6 Comments
… the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! Trash state means that InnoDB won’t… basically can’t help if there is possibility that application corrupts data by itself. For this case regular Master-Slave setup (in…
Post: How Percona Server handles data corruption more gracefully
January 6, 2012 By 2 Comments
… a question a while ago about how Percona Server handles corrupted data more gracefully than the standard MySQL server from Oracle. The… standard MySQL from Oracle, if any page of data in InnoDB is found to be corrupt, the entire instance will crash forcefully. This is a good policy if you want to treat your entire data set…
