• Hey there,

    I’ve been having a few problems with my DB and I’ve had to do a repair on a few occasions to get things back up and running.

    My blog is https://www.unlimitedchoice.org/blog

    What happens is I visit my page, I can see the header and side bar, but not posts.

    If if then go to phpmyadmin I get the message that my ‘posts’ table has crashed. If I do a repair, it does work and then all my posts do come back. (However, after doing a repair recently I lost one of my text sidebar widgets).

    Anyway…

    If I run on check on the posts table I still get this message even after doing a repair

    xxx_posts check warning Size of indexfile is: 2822144 Should be: 2821120
    xxx_posts check error Key in wrong position at page 243712
    xxx_posts check error Corrupt

    Any advice or suggestions about what I can do to repair the table if the options to repair and optimise don’t fix it?

    With thanks,

    #Amit

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Marius L. J.

    (@clorith)

    Hi,

    If this is a repeat occurrence I would contact your web host and inform them that the tables are repeatedly corrupting them selves, it might be a sign of a failure on their end that they will need to fix.

    Thread Starter asodha

    (@asodha)

    Hey Marius,

    Thanks for the reply. I don’t think it’s so much an issue that keeps, happening, rather than an issue that has been there for a while already, and occasionally causes the table to crash; or at least that’s what I believe.

    I have a ticket open with them to see if there’s anything they can do. I’m also looking at options to find a database expert who might be able to fix it.

    A friend of mind suggested that I create a new table, import all the data, delete the original ‘posts’ table, and then rename the new table.

    Has anyone tried anything like that – do you know if it will work?

    As always, any assistance appreciated,

    Amit

    Moderator Marius L. J.

    (@clorith)

    You could try it, but I suspect it will keep happening if you import data that the server is struggling with, I’d hold off on doing anything with the database until your host replies to your ticket, and then re-evaluate what to do at that point.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Table Is Corrupt and Repair Doesn't Fix – What Can I do?’ is closed to new replies.