Database Error

  • Resolved Abigailm

    (@abigailm)


    3 years, 9 months ago

    I’m running into a database error and don’t know how to fix it.

    Basically, I have backup routine running daily on my server, but is throwing an error tied to the “wp_supsystic_tbl_diagrams” table.

    I get this error:

    mysqldump: Couldn’t execute ‘show fields from wp_supsystic_tbl_diagrams‘: Table ‘.wp_supsystic_tbl_diagrams’ doesn’t exist in engine

    I tried to check & repair the table in phpMyAdmin – but that also showed an error. If I try to browse the table, I get the same error as above (“#1932 – Table – “doesn’t exist in engine.”)

    Within the database structure, this table shows as existing, but no entry for rows, type, or size — and the table shows “in use”

    Is it safe to drop this table?

    I found this article – https://supsystic.com/documentation/table-doesnt-exist-error/ – but it doesn’t seem to apply to the problem I am seeing. I have been using this plugin for several years now and have not made any changes to the database.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Abigailm

    (@abigailm)

    Just a follow-up —
    I wasn’t able to drop the problem table — the “doesn’t exist” error prevented that as well.

    I thought I could export my table, uninstall the plugin and then reinstall it — but it turns out that the export/import features are available only in the pro version.

    I only had one active table, so I ended up directly copying that table into an Excel spreadsheet, then copying it back into a WP table block. Then I uninstalled the Supsystic plugin.

    I’d note that with the uninstall (deactivating and deleting), the Supsystic tables were emptied but remained in the database – so I did have to manually drop them.

    So basically this problem was resolved for me by abandoning use of this particular plugin in favor of an alternate solution.

    Plugin Support Support Ole

    (@trsupsys)

    We are glad that you figured out how to solve that issue by your own.
    Unfortunately, we did not quite understand what exactly the problem with our plugin is. From your words, it is obvious that some manipulations were done that led to such a result.
    Don’t hesitate to contact us if you’ll need our help again.

    Thread Starter Abigailm

    (@abigailm)

    Well, the problem was that nothing had been done that could be tied to plugin usage — there had been no manual updates or changes to the single table that had been created with the plugin. The problem seems to have started with the update to version 1.9.99 — but rolling back to the previous version did not resolve the problem. And since the corrupted table did not respond to any of the usual commands, it could not be repaired.

    In any case, in the end I have decided I don’t need to use this plugin – so it doesn’t matter for me. But perhaps my report will help if anyone else reports a similar problem.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Database Error’ is closed to new replies.