… objects are now allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve write performance for high levels… to indicate an incomplete result set. Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log… 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
… target database: mysql orig_old < /tmp/orig.schema.sql Ensure innodb_import_table_from_xtrabackup = 1 (dynamic variable) Prepare the backup…. This will allow you to compare and restore values (potentially corrupted via user error or other issues) with SQL rather than… FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=’orig’ AND ENGINE=’InnoDB‘; EOF mysql -N -B <<'EOF' > import-ddl.sql SELECT CONCAT…
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… 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
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the…. Bug fixed #1099387 (Alexey Bychko). Reduced the overhead from innodb_pass_corrupt_table value checks by optimizing them for better CPU branch…
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… how to do it http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:start . The biggest challenge…_id for each table – http://www.percona.com/docs/wiki/innodb-data-recovery-tool:mysql-data-recovery:advanced_techniques#recovering_the…
Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available
April 17, 2013 By 2 Comments
…started before running wsrep recovery, this would lead to memory corruption and server crash. Bug fixed #1132974 (Seppo Jaakola). Conflicting prepared…fixed #1154095 (Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work load contained DDL …
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…
Post: Finally. How to verify if all MySQL records were recovered
April 25, 2013 By Leave a Comment
…. There are two ways to know how many records an InnoDB page stores. The index page has a header PAGE_N… – and count them. As you might know, records inside an InnoDB page are organized in an unidirectional list. The list is… two conclusions can be make: The page structure is not corrupt You know how many records to expect This is what…
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: file… Percona we offer assistance in MySQL Recovery, including recovery from Innodb corruptions and deleted data.
