• Hello,

    Do you know why this happens ? I got this error after adding the repair code define(‘WP_ALLOW_REPAIR’, true); to wp-config.php

    Thank you for your help.

    ERRORS:
    The wp_users table is okay.

    The wp_usermeta table is not okay. It is reporting the following error: InnoDB: Index ‘user_id’ contains 1431224 entries, should be 1431229.. WordPress will attempt to repair this table…
    Failed to repair the wp_usermeta table. Error: InnoDB: Index ‘user_id’ contains 1431224 entries, should be 1431229.

    The wp_posts table is okay.

    The wp_comments table is okay.

    The wp_links table is okay.

    The wp_options table is not okay. It is reporting the following error: InnoDB: Index ‘option_name’ contains 1226 entries, should be 1281.. WordPress will attempt to repair this table…
    Failed to repair the wp_options table. Error: InnoDB: Index ‘option_name’ contains 1226 entries, should be 1281.

    The wp_postmeta table is okay.

    The wp_terms table is okay.

    The wp_term_taxonomy table is okay.

    The wp_term_relationships table is okay.

    The wp_termmeta table is okay.

    The wp_commentmeta table is okay.

    Some database problems could not be repaired. Please copy-and-paste the following list of errors to the WordPress support forums to get additional assistance.

    wp_usermeta: InnoDB: Index ‘user_id’ contains 1431224 entries, should be 1431229.
    wp_options: InnoDB: Index ‘option_name’ contains 1226 entries, should be 1281.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    From your hosting control panel, find PHPMYADMIN. Access your database. Select all the tables, and at the bottom, where it says “with selected”, choose “check”. Then, repair any tables that are not OK.

    Thread Starter advexpwoo

    (@advexpwoo)

    Thank you, I did it but it didn’t fix. The only way is to restore a complete backup of the database after deleting it. Even restoring the corrupted tables only didn’t work. Do we know why it happens ?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Check with your host. Generally, tables get corrupt when the database server is shut down improperly or crashes.

    Thread Starter advexpwoo

    (@advexpwoo)

    Thank you, they said that they cannot find anything and server is ok.

    Can you tell me a last thing:

    If crash happens live when I am working on the website, where can I check to know what was being written in the database or what happened at the moment of the crash ?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    You can’t; that’s only available if they enable detailed logging at the database server and you had access to those logs.

    Thread Starter advexpwoo

    (@advexpwoo)

    Thanks again, so I will ask them, as I am on a dedicated server. Is this the only thing that I need to ask ?

    “detailed logging at the database server” ?

    Cheers.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Read on on mysql logging; this not a WordPress support issue.

    Thread Starter advexpwoo

    (@advexpwoo)

    Thanks for all.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Database errors after trying to repair, not the first time, what to do ?’ is closed to new replies.