Error 1033 Mysql Incorrect Information In File
Contents |
& Site Management Integration Options Developers eMail Components CloudLinux Extensions Extension Catalog Submit your Extension Plans & Pricing Support Resources FAQs Forums Knowledge Base Documentation Downloads Plesk University Release notes Blog Become
Error 1033 Hy000 Incorrect Information In File Mysql Tables_priv Frm
a Partner Russian German French Spanish Chinese Japanese Italian Language English Russian mysqldump got error 1033 incorrect information in file when using lock tables German French Spanish Chinese Japanese Italian any Search [How to] How to fix InnoDB corruption cases for the
Mysql Incorrect Information In File Frm Innodb
MySQL database Article ID: 6586, created on Aug 6, 2009, last review on Jun 13, 2016 Applies to: Plesk Symptoms The following error is shown in Plesk: ERROR: PleskMainDBException MySQL incorrect information in file mysql query failed: Incorrect information in file: './psa/misc.frm' Plesk upgrade fails with the following error: DATABASE ERROR!!! Database psa found, but version undefined The MySQL service does not start: /etc/init.d/mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] mysqldump and mysqlcheck fail with an error message claiming a table does not exist (use the MySQL administrator account to error 1033 hy000 incorrect information in file frm check): mysqlcheck -uadmin -p****** db_example db_example.BackupTasks error : Can't find file: 'BackupTasks.MYD' (errno: 2) A table cannot be properly queried with the SELECT statement: mysql> select * from db_example.misc; ERROR 1033 (HY000): Incorrect information in file: './db_example/misc.frm' The table cannot be repaired because the InnoDB engine does not support reparation. mysql> repair table misc; +-------------------------+--------+----------+---------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +-------------------------+--------+----------+---------------------------------------------------------+ | psa.APSApplicationItems | repair | note | The storage engine for the table doesn't support repair | +-------------------------+--------+----------+---------------------------------------------------------+ The following information can be found in the MySQL log file: 150704 19:09:27 InnoDB: Waiting for the background threads to start 150704 19:09:28 InnoDB: Error: tablespace size stored in header is 3712 pages, but 150704 19:09:28 InnoDB: the sum of data file sizes is only 3072 pages 150704 19:09:28 InnoDB: Cannot start InnoDB. The tail of the system tablespace is 150704 19:09:28 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an 150704 19:09:28 InnoDB: inappropriate way, removing ibdata files from there? 150704 19:09:28 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force 150704 19:09:28 I
10.10) had two corrupted tables, with the following errors when we tried to access their content: ERROR 1033 (HY000): /usr/sbin/mysqld: Incorrect information
Incorrect Information In File Frm Innodb
in file: './database/sp_account.frm' ERROR 1033 (HY000): /usr/sbin/mysqld: Incorrect information in file: './database/sp_screen.frm' error 1033 hy000 incorrect information in file mysql proc frm Since there were a lot of updates on the database, restoring a backup was not an option, so
Innodb_force_recovery
we tried the standard recovery tools provided by MySQL: REPAIR TABLE : http://dev.mysql.com/doc/refman/5.1/en/repair-table.html InnoDB recovery : http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html Unfortunately, these two procedures ended up with no successful results 🙁 So we dug https://kb.plesk.com/en/6586 more on the Internet, and we found this very interesting article : http://blogs.skysql.com/2011/05/innodb-data-recovery-success-story.html In this article, the authors refers to the Percona InnoDB Data Recovery Tool which allows recovering lost data by extracting rows from MySQL raw files. We strictly followed the documentation, and finally managed to recover our data in order to restore them in our corrupted tables. Here are the https://www.ekito.fr/people/repairing-a-badly-hurt-mysql-database-2/ steps that we followed. First, we downloaded the source code of the tool onto our MySQL server; then, we built it (the doc is self explanatory). The next step consists of extracting the pages using this command: page_parser -5 -f /var/lib/mysql/ibdata1 It creates a directory which contains several subdirectories with a lot of files (in our case "pages-1328713071/FIL_PAGE_INDEX/"). Then, the tricky part is to enable the InnoDB Tablespace Monitor by using this MySQL command: CREATE TABLE innodb_table_monitor (id int) ENGINE=InnoDB; With this monitor enabled, we had to look at the MySQL error log (/var/log/mysql/error.log) in order to locate the page index of our corrupted table: TABLE: name database/sp_account, id 0 85, columns 23, indexes 2, appr.rows 220 ... INDEX: name PRIMARY, id 0 215, fields 1/22, uniq 1, type 3 root page 401, appr.key vals 220, leaf pages 3, size pages 4 ... In this output, it shows that we have to look at the page located in the 0-215 subdirectory of our extracted pages (ie pages-1328713071/FIL_PAGE_INDEX/0-215/). Then, we had to merge the pages
theatlassian-fisheye-