May 23, 2012

Post: How to recover deleted rows from an InnoDB Tablespace

indexes (with their IDs) to the error log. mysql (employees) > CREATE TABLE innodb_table_monitor (id int) ENGINE=InnoDB; TABLE: namenot only rows deleted accidentally. You should manually find the data you need to recover and save it in another file

Post: Missleading Innodb message on recovery

… 20000000, file name ./mysql-bin.003000 He has tried to restart replication from mysql-bin.005000 position 10000000 which failed with “Could not find first log file name in binary log index file” error message Looking at the Master for this slave I could see its binary log files going only to about 2000, so the binary log file mentioned…

Post: How Percona does a MySQL Performance Audit

name-resolve is easy to miss, as is the absence of innodb_log_filein the mysql.* tables, running mk-duplicate-key-checker to find redundant indexesin a high-performance system is virtually every query.) If it’s not possible to use a patched binary

Comment: How SHOW SLAVE STATUS relates to CHANGE MASTER TO

Getting this error: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file‘ tried changing binlon file to position to full path, but no luck, any suggestions?

Comment: How SHOW SLAVE STATUS relates to CHANGE MASTER TO

Getting this error: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file’ tried changing binlon file to position to full path, but no luck, any suggestions?