php mysql phpmyadmin innodb myisam share|improve this question asked Mar 18 '12 at 18:44 warr0032 55116 add a comment| 3 Answers 3 active oldest votes up vote 3 down vote accepted Is it plausible for my creature to have similar IQ as humans? All Drupal 6 websites on the same server have no problem, but the two Drupal 7 databases corrupted. Thanks for any help. navigate here
When I use phpmyadmin to check the database I got the following message: 1033: Incorrect information in file: './xxx/accesslog.frm' when using LOCK TABLE I am running Drupal 7.9. im so depressed Log in or register to post comments Your host should have copied faqing commented July 17, 2013 at 10:20am Your host should have copied your database. My ISP experienced slowdown problems on that server earlier this morning, and when the sites came up (possibly after an ISP reboot?) both D7 sites displayed the same 1033 error as Create a wire coil When casting a cube spell on a hex grid do you pick a honeycomb for origin or an intersection for origin?
I suspect this had something to do with my cPanel/WHM setup overwriting the file, but I'll never know for sure. Doesn't look good, could Mysql just trash every table? Restarting did nothing gjaswal commented March 26, 2012 at 6:13pm Yup. mysql> SHOW ENGINES; +------------+----------+----------------------------------------------------------------+ | Engine | Support | Comment
TurtlePower commented February 1, 2012 at 3:46am Similar problem for me... I did not imagine this. If you have phpmyadmin installed, you can run check all tables and run CHECK TABLE and REPAIR TABLE and needed. Continued Read the MySQL Manual page on removing InnoDB log files for a safer backup and restoration procedures.
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 Log in or register to post comments Drupal 7 database corrupted faqing commented December 6, 2011 at 11:06pm I also got the same message for my two Drupal 7 sites: "PDOException: Good Luck! Your tables are probably corrupt.
If I try to repair the database I just get a list of the files that have been corrupted, but no progress on actually fixing anything. http://forums.mysql.com/read.php?22,106192,106192 After 2 days of bothering my host admins I found this post. Hoping someone can help me with this issue. Then, when the .h was generated, we had to rebuild the tool-set by firing a "make" command.
It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? check over here Cause .frm file for the problematic table is corrupted in the MySQL server. Why does this execution plan have Compute Scalars? It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.
Then, we had to merge the pages files into one: find pages-1328713071/FIL_PAGE_INDEX/0-215/ -type f -name '*.page' | sort -n | xargs cat > merged_file Then, the tool-set needs the definition of the corrupted If not, you may want to review the following Mysql docs: http://dev.mysql.com/doc/refman/5.1/en/check-table.html http://dev.mysql.com/doc/refman/5.1/en/repair-table.html If things are really bad, you may require root access to mysql and/or the server to use some repair Error Incorrect information in file: './zenpengu_main/ac... his comment is here Restarting did nothing for me.
Register FAQ/Rules My SitePoint Forum Actions Mark Forums Read Quick Links View Forum Leaders Remember Me? Reply Leave a Reply Cancel reply Required fields are marked *.Message *Name * Email * Website Notify me of followup comments via e-mail. When I checked it at cpanel, I found the two databases (D7) are empty.
Hope that helps... I don't do such experiments on live servers :-) I restarted MySQL and there was no problem with the table. Make all the statements true Radius of Convergence of Infinite Series Where are sudo's insults stored? all Drupal 7 sites went down together and Drupal 6 were fine.
I classify this as another one of MySQLs cryptic error messages. So now I do the ugly thing and kill the mysqld process that holding the file lock and then restart MySQL: [[email protected] mysql]# kill -9 24574 [[email protected] mysql]# ps ax | You may have to register before you can post: click the register link above to proceed. weblink Log in or register to post comments ⋅ Categories: Drupal 7.x Comments Your tables are probably Codeblind commented October 16, 2011 at 11:35pm Addendum at the frontofem: How are you trying
What I can do now is to ask my host company to restore the database for me. Quick Navigation Databases & MySQL Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Community Center News & Announcements General Discussions Introductions Talk With The Experts Log in or register to post comments Yup. When I click on the database tables in question they come up with: "Error No. 1033 Incorrect information in file: 'filename'" Is there anyway to recover this data or is it
Replication has been stopped on a slave server due to the following error. Contact Sales USA: +1-866-221-0634 Canada: +1-866-221-0634 Germany: +49 89 143 01280 France: +33 1 57 60 83 57 Italy: +39 02 249 59 120 UK: +44 207 553 8447 Japan: 0120-065556 This says to me that it is likely that the MySQL restart didn't go as well as the initscript would have liked me to believe. While I was typing up a support ticket to my host, the MySQL server got restarted (maybe from another ticket?), InnoDB was enabled again and the D7 sites and databases were
Query: 'INSERT INTO `table` (`id`,`col1`) VALUES (1,'foobar')' # or mysql> REPAIR TABLE table; +-------------+--------+----------+----------------------------------------------------+ | Table | Op | Msg_type | Msg_text The one thing I did notice was that the Storage Engine has been switched to MyISAM with InnoDB saying it has been disabled. Is this possible? SitePoint Sponsor User Tag List Results 1 to 3 of 3 Thread: Error 'Incorrect information in file: ' Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch
Code: Last_Errno: 1033 Last_Error: Error 'Incorrect information in file: './expansion/locations.frm'' on query. locations is InnoDB table.