Database error in vBulletin 3.7.2 - Error Number 1030 When Trying To Access Forum

[VIPTV]

HELP! Database error in vBulletin 3.7.2 - Error Number 1030 When Trying To Access Forum

For the past few days, the following database error (listed below) has been given every single time anyone tries to access two forums on my vbulletin website. The two specific forums which give the error happen to be the largest forums on my site. One of the forums has almost 5 Million posts, the other one has about 100,000 posts.

You can still access threads within the forum without a problem, and you can even reply to the threads without a problem, but you can not access the threads listing in the forum.

If anyone is willing to help please let me know, or if you can just point me in the right direction in fixing it, would be greatly appreciated.

Here is the database error given each time:

Database error in vBulletin 3.7.2:

Invalid SQL:

SELECT COUNT(*) AS threads, SUM(IF(thread.lastpost > 1316379418 AND open <> 10, 1, 0)) AS newthread

FROM vb_thread AS thread


WHERE forumid = 54
AND sticky = 0

AND visible IN (0,1,2)


AND lastpost >= 1284847243;

MySQL Error : Got error 127 from storage engine
Error Number : 1030
Request Date : Monday, September 19th 2011 @ 12:00:43 AM
Error Date : Monday, September 19th 2011 @ 12:00:50 AM
Script : http://**********.com/forums/forumdisplay.php?f=54
Referrer : http://**********.com/forums/forumdisplay.php?f=36
IP Address : ***.**.**.***
Username : ********
Classname : vB_Database
MySQL Version : 4.1.22-standard-log

I've removed the unnecessary information because I'm not sure of the rules on here about posting the specific sites / advertising etc.

Thanks in advance to anyone who can help AT ALL!

[HMBeaty]

This error means:

MySQL error: 127 = Record-file is crashed

To fix this run Repair/Optimize in the Admin CP. You may need to run it more than once to fix all errors:

Admin CP -> Maintenance -> Repair/Optimize Tables -> Check All -> Continue

[VIPTV]

Alright thanks, I was thinking about doing this, but I've done it before and it didn't repair everything correctly and actually caused more issues on the site.

I had to get someone to repair them manually because after trying to repair them through the admin CP it caused the tables to crash.

I'll give it a shot though.

Thanks again.

--------------- Added [DATE]1316400343[/DATE] at [TIME]1316400343[/TIME] ---------------

I'm still hesitant to do this, can anyone second this suggestion before I risk this...

[HMBeaty]

If you're hesitant on doing the above suggestion, make a backup of your database before any changes are made.

NOTE: You SHOULD be making a db backup anyway at LEAST once a day

[Lynne]

See this thread for other methods to repair your database - 3 ways to repair a database

[VIPTV]

thanks a lot, definitely appreciate the help...