dougnyc Posted October 30, 2002 Posted October 30, 2002 Everything was fine until my database began having errors last week. I resolved the problem by optimizing the bad tables in PHPmyAdmin only to have other tables get damaged. Now I've removed advertisments because my site is so unreliable. I am using version 2.2 and now even after optimizing the customers table I still get a error (1030 - Got error 127 from table handler) No I can't export that information. Is there a mysql command I can run to fix it? Also, what can be done to stop this from reoccuring? - Doug
SpoonFed Posted October 31, 2002 Posted October 31, 2002 Yes, it's a pretty easy fix: start mysql issue the command use catalog (or whatever your database name is) issue the command repair table tablename. Open your catalog and keep watching for 127 errors noting the name of the table that gave you the error and redo above fore each corrupted table. As for preventing that from happening again? Not sure how it's happening in the first place. It's happened to me from my mysql server locking up (not related to osscommerce or mysql but for other reasons). Pretty easy to fix and stay on top of. I found a contribution that will let you do all this from the admin page but I haven't tried it yet so I don't know if it will work. hth Scott There are 10 kinds of people in the world, those who understand binary - and those who do not.
dougnyc Posted October 31, 2002 Author Posted October 31, 2002 I'm having trouble using those MYSQL Commands: Error SQL-query?:? [Edit] repair customers MySQL said: You have an error in your SQL syntax near 'customers' at line 1 Back What can I type into PHPMyAdmin to repair a table?
dougnyc Posted October 31, 2002 Author Posted October 31, 2002 When there is a problem with a table in the database I don't always notice it until a customer notifys me. Is there a way or a place to look for these errors without having to search every facet of the site on a daily basis?
SpoonFed Posted November 1, 2002 Posted November 1, 2002 Well, you mistyped the repair command. After starty mysql and issuing "use catalog" (or whatever your database name is) the next command is "repair table tablename" (of course replace tablename with the correct table name :) As for checking the entire database, yes there is a way that is quite simple. The contribution that I mentioned works great and is easy to use. The only trouble I found with it is if your database name isn't catalog you have to change some code (but it's easy with find/replace) The name of the contribution is Database Maintenance version 1.0.1 and it's in the features section. HTH Scott There are 10 kinds of people in the world, those who understand binary - and those who do not.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.