Error Code 1033 Mysql
Contents |
information in file March 2, 2011 I recently encountered this error on Disposeamail - a free disposable email site of mine that uses MySQL heavily for storing all incoming mail mysql error 1033 (hy000) incorrect information in file through an email pipe script. I did a lot of researching, and basically,
Mysql Error 1033 Incorrect Information File Frm
there are a few primary culprits I was able to identify that will hopefully save you some time. Check mysql error code 1005 your /tmp directory MySQL will produce this error sometimes when the temp directory is not writeable. Ensure that /tmp (and/or /var/tmp) has the correct permissions (777) Check the my.cnf file and
Mysql Error Code 1064
search for a tmpdir =/tmp flag. Ensure the value is pointing to the correct temp directory. Ensure your /tmp directory is not full Check your my.cnf If you made changes recently, revert them and restart MySQL (especially InnoDB Buffer Pool settings) Restore my.cnf.back is there is one If you are using InnoDB tables , ensure the skip-innodb line in my.cnf is commented out mysql error code 13 or removed. Clear InnoDB Log Files This step ONLY APPLIES IF THE ABOVE STEPS DID NOT WORK. Read the MySQL Manual page on removing InnoDB log files for a safer backup and restoration procedures. Basically, the steps are: Shut down MySQL Remove ib_logfile* files from the MySQL data directory (move them or rename them if you want to be safe) Re-start MySQL My specific problem was that somehow the "skip-innodb" line got added back into my "my.cnf" file, so MySQL was expecting a different table format when loading data. I suspect this had something to do with my cPanel/WHM setup overwriting the file, but I'll never know for sure. Good Luck! Categories: Programming Technical Tags: database mysql mysql-errors My Projects & WebsitesCountism - Tally Counter App DevData - Developer Data Source MerryList - Christmas Wishlist Creator InvoiceMore - Online Invoicing & Billing Online JavaScript Compressor Online String Functions Frisby.js - REST API testing Recent Posts One Project Selling My Passive Income Stream: JSCompress.com Return Field Errors in Your JSON Error Response Don't Transpile JavaScript for Node.js Disabled Comments Switching from Middleman Back to WordPress Countism © 2016 Vance Lucas
Day Texas 2014 MongoDB Boston Oct 2012 MongoNYC 2013 NYC Cassandra Meetup - 100 Million Events - Sep 2012 NYC* Tech Day March 2013 Projects Colortail Gem DSpam-SpamAssassin Results Module Get Concurrent Relay Recipients TTD Facebook Categories Apache (1) Architecture (1) Asterisk (5) AWS (1)
Mysql Error Code 1175
backup (1) Blogroll (1) Book Reviews (5) Cassandra (2) Chef (1) Databases (5) EnGarde (1) Hadoop
Mysql Error Code 28
(2) Hardware (1) jRuby (2) Linux Security (6) Lua (1) Mac (13) Mail (9) Misc (19) MongoDB (2) Musings (5) MySQL (6) News mysql error code 1045 (2) NSQ (2) Perl (18) Perl Modules (13) Poetry (2) python (4) Rails (13) Redis (1) Ruby (8) Security (8) SEO (5) Social Networking (3) SPAM (3) Startup (3) System Administration (20) Testing (1) Tips (5) Virtualization (1) MySQL http://vancelucas.com/blog/mysql-error-1033-incorrect-information-in-file/ Error 1033: Incorrect Information in File 5 Jan 2010 -- eric If you've ever been plagued by an error 1033 issue in MySQL (replication will show it as well), then I might be able to help you out. The error reads something like, "Incorrect information in file: ‘./mydb/table.frm'. I classify this as another one of MySQLs cryptic error messages. Here is how I determined that this was my problem. Googling around got me an answer, but I http://eric.lubow.org/2010/databases/mysql/mysql-error-1033-incorrect-information-in-file/ had to read a bunch of different responses to piece together the answer. Essentially this issue (in my case) was a result of the InnoDB engine not loading up when MySQL was restarted. Therefore when MySQL tried to read the frm file (table description) which was written for an InnoDB table with the MyISAM reader, it didn't like it. Since MyISAM is the fallback engine, it went to that and the table became unusable. Last_Errno: 1033 Last_Error: Error 'Incorrect information in file: './st/table.frm'' on query. Default database: 'mydb'. Query: 'INSERT INTO `table` (`id`,`col1`) VALUES (1,'foobar')' # or mysql> REPAIR TABLE table; +-------------+--------+----------+----------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +-------------+--------+----------+----------------------------------------------------+ | mydb.table | repair | Error | Incorrect information in file: './mydb/table.frm' | | mydb.table | repair | error | Corrupt | +-------------+--------+----------+----------------------------------------------------+ 2 rows in set (0.02 sec) I already knew my table table is an InnoDB table. To be sure that this was the issue, I simply checked to see which engines were loaded (removed some for brevity). mysql> SHOW ENGINES; +------------+----------+----------------------------------------------------------------+ | Engine | Suppor
& 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 a Partner https://kb.plesk.com/en/6586 Russian German French Spanish Chinese Japanese Italian Language English Russian German French Spanish Chinese Japanese Italian any Search [How to] How to fix InnoDB corruption cases for the 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 query failed: Incorrect information mysql error 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 check): mysqlcheck -uadmin -p****** db_example db_example.BackupTasks mysql error code 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 InnoDB: a startup if you are trying to recover a badly corrupt databa