when trying to optimizr / repair tables

[IncubuRs]

Status: OK pollvote Optimize Status: Table is already up to date post Check Warning: Table is marked as crashed and last repair failed post Check Warning: Size of indexfile is: 6652928 Should be: 5137408 post Check Warning: Size of datafile is: 69596524 Should be: 69596416 post Check Error: Found 147863 keys of 0 post Check Error: Corrupt post




I see those errors

[Steve Machol]

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

If you cannot access the Admin CP you can also use phpMyAdmin to repair tables.

If that doesn't work then this may be too damaged to fix with the normal methods. Please check out this thread for other ways to repair a db, particularly items #2 and 3:

http://www.vbulletin.com/forum/showthread.php?s=&threadid=44909

You may have to ask your host to try and repair this for you.

[Charlie_Brown]

Yea as it worked for me.

[IncubuRs]

worked here too .. ty



Can i set a cron job to optimize the tables like every 6 hours ?

[Floris]

6 hours is not needed. Unless it is needed, and then I recommend to change host or rebuild the database on a new hard drive or something else that prevents such huge corruption.

[IncubuRs]

how to rebuild the database ?
:$

[Floris]

Dump the .sql

Create a new mysql database

Restore the .sql

Update vB's config.php

And run that, and compare the corruption before/after