June 20, 2013

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… align=”alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3[/caption]… Bug fixed #1184427. Query to the INNODB_CHANGED_PAGES table would cause server to stop with… #1186831. Reduced the overhead from the Handle Corrupted Tables check as it was missing branch predictor annotations. …

Post: Percona Server for MySQL 5.5.30-30.2 now available

…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch prediction. Bug…(Alexey Bychko). Percona Server for MySQL was missing help texts in the MySQL client because the help tables were missing. Bug fixed #1041981…

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch prediction. Bug…(Alexey Bychko). Percona Server for MySQL was missing help texts in the MySQL client because the help tables were missing. Bug fixed #1041981…

Comment: How to recover table structure from InnoDB dictionary

… saved then ibdata1 should be valid, maybe with some corruption. The tables structure you can get from the dictionary as it is…. You can check the docs how to do it http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:start… to find index_id for each table – http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:advanced_techniques#recovering…

Post: Recovering Innodb table Corruption

CHECK TABLE in INNODB is pretty useless. For my manually corrupted table I am getting: mysql> check table test; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> check table test; +———–+——-+———-+———-+ | Table

Post: Verifying backup integrity with CHECK TABLES

… post on InnoDB‘s handling of corrupted pages, because the best way to check for corruption is with CHECK TABLES, but if a page is corrupt, InnoDB will crash the server to prevent access to the corrupt data…

Post: MySQL Crash Recovery

… use tiny script which moves out all MyISAM tables out of MySQL database directory, checks them with MyISAMchk and moves them back to… table open which is important. There are other problems which you may experience related to MySQL Crash Recovery – Restoring data from backup, corrupted Innodb

Post: Magic Innodb Recovery self healing

… 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… wanted to check if this is really required by trying lower recovery settings. Happily I was able to restart MySQL with innodb_force… 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…

Post: Connecting orphaned .ibd files

corrupted and innodb_force_recovery doesn’t help Chris Calender suggests two methods. The first is create/drop the tableMySQL server. 0. Create empty InnoDB tablespace. 1. Create the table: mysql>CREATE TABLE

Post: Recovery deleted ibdata1

…to corruption and data loss. For the same reason we can’t make MySQL backup …mysql# And restart MySQL: root@localhost:/var/lib/mysql# /etc/init.d/mysql restart After the restart all InnoDB tables are reachable: mysql… system checks that InnoDB files ibdata and ib_logfile* do exist Do not restart MySQL