Title: Wordfence Bad Database Table
Last modified: November 3, 2018

---

# Wordfence Bad Database Table

 *  Resolved [wellsite](https://wordpress.org/support/users/wellsite/)
 * (@wellsite)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/wordfence-bad-database-table/)
 * For security reason, we have replaced the db name with xxx.
    Our hosting support
   has reported the following issue to us. Please advise if it is ok to drop the
   bad tables. See the error message at the bottom of my message for reference.
 * We received a notification from the Wellsites VPS that the latest backup failed(
   see report at foot of email). I asked an engineer to look into this and they 
   advised:
 * It appears that your backup failed because some cPanel users have a WordFence
   plugin with one or more bad tables. I put a list of users at the bottom of this
   email. Since every bad table is a WordFence table I believe this is a problem
   with WordFence and not the database and for a detailed explanation, I recommend
   contacting their developers.
 * In the meantime in order to get the backups to run there are a few things you
   could do so backups will run again.
 * Or you we could drop the bad tables.
 * Let me know if you would like us to drop the tables for you or I can provide 
   you with a list of tables that have been affected.
 * [2018-11-03 17:02:14 +0000] mydental_livedb: mysqldump: Got error: 1146: Table‘
   xxx.md_wfVulnScanners’ doesn’t exist when using LOCK TABLES [2018-11-03 17:02:
   16 +0000] xxx: mysqldump failed — database may be corrupt
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwordfence-bad-database-table%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [wfasa](https://wordpress.org/support/users/wfasa/)
 * (@wfasa)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/wordfence-bad-database-table/#post-10853341)
 * Hi [@wellsite](https://wordpress.org/support/users/wellsite/),
    If you have broken
   tables it might be best to do a fresh install of Wordfence, meaning delete all
   Wordfence tables and do a new installation.
 * Was the old db prefix md and you changed it to xxx? If so, how did you make that
   change?
 *  [wfdave](https://wordpress.org/support/users/wfdave/)
 * (@wfdave)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/wordfence-bad-database-table/#post-10902970)
 * Hi [@wellsite](https://wordpress.org/support/users/wellsite/),
 * We haven’t heard back from you in a while, so I’ve gone ahead and marked this
   thread as resolved.
 * Please feel free to open another thread if you’re still having issues with Wordfence.
 * Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Wordfence Bad Database Table’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [wfdave](https://wordpress.org/support/users/wfdave/)
 * Last activity: [7 years, 5 months ago](https://wordpress.org/support/topic/wordfence-bad-database-table/#post-10902970)
 * Status: resolved