…. This will allow you to compare and restore values (potentially corrupted via user error or other issues) with SQL rather than….sql SELECT CONCAT(‘ALTER TABLE `’, table_name, ‘` DISCARD TABLESPACE;’) AS _ddl FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=’orig’ AND ENGINE=’InnoDB‘; EOF mysql -N…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
… any bitmap files. Bug fixed #1184427. Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O… an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn… issues. Bug fixed #1186831. Reduced the overhead from the Handle Corrupted Tables check as it was missing branch predictor annotations. Bug fixed…
Post: How to recover table structure from InnoDB dictionary
April 22, 2013 By 4 Comments
… 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 dictionary… exist for any InnoDB table. If explicitely defined its `NAME` is PRIMARY. If the primary key is not defined InnoDB will use a…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
April 24, 2013 By Leave a Comment
… bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb_lazy_drop_table has been deprecated. Feature has…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch prediction…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb_lazy_drop_table has been deprecated. Feature has…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch prediction…
Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available
April 17, 2013 By 2 Comments
…replicate in case DROP TABLE statement is used on a temporary table. Bug fixed #1084702 (Seppo…wsrep recovery, this would lead to memory corruption and server crash. Bug fixed #1132974 (Seppo …Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work …
Comment: How to recover table structure from InnoDB dictionary
May 8, 2013 By 4 Comments
1) innodb_file_per_table is OFF by default, which means all tables are in ibdata1. 2) if it was HW problem and… saved then ibdata1 should be valid, maybe with some corruption. The tables structure you can get from the dictionary as it is… is to find index_id for each table – http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:advanced…
Post: Recovering Innodb table Corruption
July 4, 2008 By 22 Comments
… delete any data (though you can create or drop Innodb tables): mysql> optimize table test; +———–+———-+———-+———————————-+ | Table | Op | Msg_type | Msg_text | +———–+———-+———-+———————————-+ | test.test | optimize… sure indexes are not corrupted. So we looked at how to get your data back from simple Innodb Table Corruption. In more complex cases you may need to use higher innodb_force_recovery modes to block…
Post: Innodb Recovery Update - The tricks what failed.
May 24, 2007 By 3 Comments
… dump tables with innodb_force_recovery=4 was confirmed to be added in 5.0.33, meaning you could not really recover corrupted Innodb tables… have some impact. Innodb tables rarely become corrupt Indeed even if you leave out crashes in my experience Innodb tables become corrupted more seldom than MyISAM…
Post: Magic Innodb Recovery self healing
May 22, 2007 By 2 Comments
… the table corrupting with Innodb, as it is limited to only one particular index on one particular table type it is likely to be Innodb… to now dump potentially corrupted tables (in this particular corruption instance Innodb did not print table name in question), drop tables, restart Innodb without innodb_force_recovery and…
