SQL Error

[Nemesis]

http://www.vbulletin.com/forum/showt...5-tried-repair...

Don't know if this will help, but here you go.

[Raven Faust]

nope no help thanks tho

[To0]

It won't allow the repair because there is a active connection (most likely).

You could try restarting the sql or http server to disconnect any connections and then try to repair but in most cases that won't do the trick either.

The only real option you have is to delete the table "thread" and import a backup of table "thread" which would instantly resolve your issue.

This is not a provider issue.

Good luck.

[SplitIce]

repair has locking To0 so thats not an issue, REPAIR TABLE WILL fix the problem, marking as crashed just means the mysql server crashed or unclean shutdowned while a write operation was taking place and the db needs to be fixed.

[To0]

Repair will not work on table "thread" if marked as crashed and a connection is persistent even after reboot of SQL. I've had the same table crash on me several times in my career with this same exact issue.

It will continue to 1.) Timeout, or 2.) Remain crashed.

Granted, I was able to repair the table in the past. However, once it is un-repairable (according to Raven's statements) your only option is to overwrite it with an existing backup.

[SplitIce]

the table that is crashed is: ./GTS1/post

that means :-
DB: GTS1
Table: post

[To0]

According to initial thread:

MySQL Error : Table 'thread' is marked as crashed and should be repaired
Error Number : 1194
Request Date : Thursday, March 11th 2010 @ 02:50:46 AM
Error Date : Thursday, March 11th 2010 @ 02:50:46 AM

[Raven Faust]

see to0 knows his shit, Split that table was for UGTeam.. , but there both having same issues with diff tables..

After trying to repair using phpmyadmin i got:

Session: The storage engine for the table doesn't support repair ( so now its on the session table)

[Raven Faust]

fixed it, had to use an old backup :\ thanks everyone close this thread.

[SplitIce]

MEMORY doesnt support repair, but sessions can just be truncated as it is not important. but be aware if a memory table is corrupt you probably have some serious issues on the server since when restarted they are no more, aka they cant be crashed.