Results 1 to 3 of 3
Thread: Table error/repair question
Oct 27, 2009, 16:18 #1
Table error/repair question
So I have a particular table that keeps crashing. It gives the good ol' error message: "Table is Marked as Crashed and Should be Repaired". Besides using a query 'REPAIR TABLE xxxx' what are my options? This is happening almost daily.
Would any of the following help? (I ask before doing because of the amount of people using it at any given moment)
- Recreate the particular table from scratch?
- Change it from MyISAM to Innod?
Is there a way to detect this and repair before users see that error message (or error 134)?
Oct 27, 2009, 16:24 #2
- Join Date
- Aug 2000
- Philadephia, PA
- 1 Post(s)
- 0 Thread(s)
What you should do is identify the cause of the crashes, not just come up with better ways to deal with it after it happens. Very few things can cause crashed tables -- a bad hard drive, bad memory, or the MySQL server itself crashing while running. All these circumstances can be checked -- run a disk check, run a memory test, and check MySQL's log to see if it's been restarting after crashing.Try Improvely, your online marketing dashboard.
→ Conversion tracking, click fraud detection, A/B testing and more
Oct 27, 2009, 20:07 #3
No problems servers side. I'm working sessions table that stores the session id as a hash and has a timestamp with user data in it. Just not sure how this can occur.