Comment: Connecting orphaned .ibd files
…16 14:19:30 debian /etc/mysql/debian-start[14967]: Triggering myisam-recover for all MyISAM tables > May ….” ? > Must I import .ibd into an empty database ? In this case ibdconnect does not need...
View ArticleComment: How to estimate time it takes Innodb to Recover ?
… 16 3276587130 080626 0:06:16 InnoDB: Database was not shut down normally! InnoDB: Starting crash… 0:06:20 [Note] Recovering after a crash using /var/log/mysql/bin 080626 0:06:20 …/lib/mysql/...
View ArticlePost: Recovery after DROP & CREATE
… deleted. That’s why it was possible to recover them with -D option. When a user immediately… to know which index_id belongs to which database/table. Sometime it’s not possible to find …# ./s_tables...
View ArticlePost: Aligning IO on a hard disk RAID – the Benchmarks
…/mysql socket=/var/run/mysqld/mysqld.sock innodb_file_per_table = true innodb_data_file_path = ibdata1:…file_size = 10G myisam_repair_threads = 1 myisam_recover skip-grant-tables Amount of rows used...
View ArticlePost: Recovery deleted ibdata1
… job for ibdconnect, but as long as MySQL isn’t restarted it is possible to recover database fast. Let me illustrate how. Let’s simulate the accident. For that I will delete /var/lib/mysql/ib…...
View ArticlePost: A recovery trivia or how to recover from a lost ibdata1 file
…mysql -u root “create database if not exists filler;” while [ 1 ] do CURRENT_SPACEID=`mysql…mysql/recover/ chown mysql.mysql /var/lib/mysql/recover/$CURRENT_TABLENAME.ibd sleep 1 echo “importing...
View ArticlePost: How to recover table structure from InnoDB dictionary
…=latin1 `NAME` is a human readable table name in form database_name/table_name e.g. sakila/actor. `ID` is a… parsers make dict_parsers 2. Split ibdata1 with page_parser ./page_parser -f...
View ArticleNew SpecJAppServer results at MySQL and Sun.
As you likely have seen Sun has posted the new SpecJAppServer Results More information from Tom Daly can be found here These results are quite interesting for me as I worked on some of the previous...
View ArticleCopying InnoDB tables between servers
The feature I announced some time ago http://www.mysqlperformanceblog.com/2009/06/08/impossible-possible-moving-innodb-tables-between-servers/ is now available in our latest releases of XtraBackup...
View ArticleShard-Query EC2 images available
Infobright and InnoDB AMI images are now availableThere are now demonstration AMI images for Shard-Query. Each image comes pre-loaded with the data used in the previous Shard-Query blog post. The data...
View ArticleClik here to view.
Why is the ibdata1 file continuously growing in MySQL?
We receive this question about the ibdata1 file in MySQL very often in Percona Support.The panic starts when the monitoring server sends an alert about the storage of the MySQL server – saying that the...
View ArticleClik here to view.
How to move the InnoDB log sequence number (LSN) forward
This post focuses on the problem of the InnoDB log sequence number being in the future.Preface: What is an InnoDB log sequence number?The Log sequence number (LSN) is an important database parameter...
View ArticleIncremental backups with log archiving for XtraDB
Percona Server 5.6.11-60.3 has introduced a new feature called Log Archiving for XtraDB. This feature makes copies of the old log files before they are overwritten, thus saving all the redo log for a...
View ArticleExamining the TokuDB MySQL storage engine file structure
As we know different storage engines in MySQL have different file structures. Every table in MySQL 5.6 must have a .frm file in the database directory matching the table name. But where the rest of the...
View ArticleA closer look at the MySQL ibdata1 disk space issue and big tables
A recurring and very common customer issue seen here at the Percona Support team involves how to make the ibdata1 file “shrink” within MySQL. I can only imagine there’s a degree of regret by some of...
View ArticleWhen (and how) to move an InnoDB table outside the shared tablespace
In my last post, “A closer look at the MySQL ibdata1 disk space issue and big tables,” I looked at the growing ibdata1 problem under the perspective of having big tables residing inside the so-called...
View ArticleRecovery deleted ibdata1
Recently I had a case when a customer deleted the InnoDB main table space – ibdata1 – and redo logs – ib_logfile*.MySQL keeps InnoDB files open all the time. The following recovery technique is based...
View ArticleRecovery after DROP & CREATE
In a very popular data loss scenario a table is dropped and empty one is created with the same name. This is because mysqldump in many cases generates the “DROP TABLE” instruction before the “CREATE...
View ArticleHow to recover table structure from InnoDB dictionary
To recover a dropped or corrupt table with Percona Data Recovery Tool for InnoDB you need two things: media with records(ibdata1, *.ibd, disk image, etc.) and a table structure. Indeed, there is no...
View ArticleClik here to view.
Why is the ibdata1 file continuously growing in MySQL?
We receive this question about the ibdata1 file in MySQL very often in Percona Support.The panic starts when the monitoring server sends an alert about the storage of the MySQL server – saying that the...
View Article