Mysql Error 1033
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 incorrect information file frm through an email pipe script. I did a lot of researching, and basically,
Mysql Error 1033 (hy000) Incorrect Information In File
there are a few primary culprits I was able to identify that will hopefully save you some time. Check
Incorrect Information In File Mysql
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
Incorrect Information In File Frm Innodb
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 error 1033 hy000 incorrect information in file mysql tables_priv frm 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 enable innodb Get Concurrent Relay Recipients TTD Facebook Categories Apache (1) Architecture (1) Asterisk (5) mysql repair table AWS (1) backup (1) Blogroll (1) Book Reviews (5) Cassandra (2) Chef (1) Databases (5) EnGarde (1) Hadoop (2) Hardware (1) jRuby (2) Linux Security (6) Lua (1) Mac (13) Mail (9) Misc (19) MongoDB (2) Musings (5) MySQL (6) News (2) NSQ (2) Perl (18) Perl Modules (13) http://vancelucas.com/blog/mysql-error-1033-incorrect-information-in-file/ 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 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 http://eric.lubow.org/2010/databases/mysql/mysql-error-1033-incorrect-information-in-file/ 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 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.ta
Hayden 1 Comment One of these errors might appear on your website without warning: Warning: DB function failed with https://major.io/2007/08/25/182/ error number 1033
Incorrect information in file: './database_name/table_name.frm' SQL=SELECT col1, col2 FROM table_name WHERE col3 = 'some_value' ORDER BY col1 ASC MySQL is telling you that the table structure it has within data files doesn't match the structure in the .frm file that's on the disk. There's only a few scenarios where this can happen: Different incorrect information version of the .frm files If the .frm files from an older or later version of the table are placed in MySQL's data directory, MySQL will become confused and it won't be able to determine the proper database structure. Pending table alteration A pending database operation that ran an ALTER TABLE may not have written changes to incorrect information in the disk. MySQL may have stopped running abruptly or the entire server may have crashed. The normal operation for MySQL is to make changes in memory first and then perform disk operations. Complete wierdness I cannot explain it, and I can't figure out the logic that would allow it to happen, but some web application vulnerabilities can cause this problem. I've seen it happen with Joomla! sites running on fairly secure servers, and there was no Apache privilege escalation used to modify the .frm files directly. How is it fixed? The only way to repair it is to import the table again from a mysqldump backup, find the correct .frm file and restore it on the server, or run an ALTER TABLE to bring the table back to its original state. Share this post:TwitterGoogleLinkedInRedditEmailPrintTagged With: database, emergency Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Email check failed, please try again Sorry, your blog cannot share posts by email.