Can’t Delete it and crashed my Database

  • Resolved Soprano

    (@soprano)


    5 years, 2 months ago

    Hello,

    A developer recently asked me to install this plugin so they could inspect an issue with one of the table rows in my database.

    Everything went smoothly but a few hours after, my database started hitting maximum 6 CPU cores and showing a 503 error on my front end.

    I rarely exceed 1.5 cpu core usage, and when I asked my host they said some queries in my database were slow and timing out. I can’t say this plugin was directly responsible for that, but I haven’t had an issue with my database in years, and this developer only claims to have been reading some of the data in the rows.

    But my main concern is that I can’t seem to delete this plugin. Whenever I deactivate it, the successful deactivation message popups up in wordpress, but the plugin remains enabled.

    I deleted the folder from the plugins ftp, but I noticed it has creates 2 wp options and new tables in the database (like 9).

    How can I remove this plugin completely from my installation?

    Apart from:

    Database Tables
    wp_wpda_logging
    wp_wpda_media
    wp_wpda_menus
    wp_wpda_publisher
    wp_wpda_table_design
    wp_wpda_table_settings
    wp_wpdp_page
    wp_wpdp_project
    wp_wpdp_table

    Options
    wpda_show_whats_new
    wpda_version

    Is there anything else I need to delete? After removing all this I still get a notice from wordpress saying: The plugin wp-data-access/wp-data-access.php has been deactivated due to an error: Plugin file does not exist.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi Soprano,

    Sorry to hear you are having trouble with the plugin.

    Whether tables and options are deleted during uninstall depends on your Uninstall Settings which can be changed on the Manage Plugin page (tab Uninstall Settings). By default the tables and options are deleted. If the Uninstall Settings are disabled they will not.

    I uninstalled and reinstalled the plugin on my test computer and noticed that only table wp_wpda_table_settings was not deleted. This is a new table introduced in version 2.6.0. I will add the removal of this table to the unstall section as well. Did you disabled the Uninstall Settings previously? That would explain the problem.

    You can safely drop the plugin tables and delete the plugin options from the wp options table. If you want the plugin to do this for you, you can reinstall the plugin, make sure you have enabled the checkboxen on the Uninstall Settings tab (please explicitly save your settings) and uninstall the plugin again.

    Can you provide more information about the activities that might have slow down your system? That’s important for me to know. I test the plugin all the time with small, medium and large tables (import, export, queries, and so on). The plugin itself does not access any tables without indexes. I wonder what was going wrong.

    Best regards,
    Peter

    Thread Starter Soprano

    (@soprano)

    Thanks Peter for your response.

    I checked to make sure the right settings were selected to delete both options and tables prior to trying to delete the plugin. The main issue didn’t seem to be there, but in the actual deleting of the plugin which would not delete, if it had successfully deleted I would assume it would have also followed the settings selected and removed the options and tables from the DB.

    I’m still not sure what slowed down the system, I used a system restore point from a day before at the cost of losing the last few hours of data, which fixed the issue of the ram/cpu overload. I did experience another outage for an 3 hours last night apparently according to a third party up time monitor.

    Perhaps it had to do with the size of my DB. It’s not big (400MBs) but it does have a lot of rows (2.4 Million). I’m working on decluttering it a bit to see if that helps.

    Plugin Author Passionate Programmer Peter

    (@peterschulznl)

    Hi Soprano,

    Good to hear you fixed it!

    If your developer used the plugin to query a table with such a large number of rows, then that query might have been the course of your problem. If you use the search box in the Data Explorer the query does a full table scan. I have successfully tested this with tables containing up to 100.000 rows, but never with such a large number of rows as you have. I’ll see if I can think of a way to improve this behaviour in the future. Thank you for response and patience!

    Best regards,
    Peter

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Can’t Delete it and crashed my Database’ is closed to new replies.