Tablespace for table ‘`wp`.`wp_actionscheduler_claims`’ exists

  • Resolved tonyzyc

    (@tonyzyc)


    2 months, 1 week ago

    I am getting the following error when importing the database. What should I do to import the database?

    Error

    SQL query: Copy

    — — Table structure for table wp_actionscheduler_claims

    CREATE TABLE wp_actionscheduler_claims (
    claim_id bigint(20) UNSIGNED NOT NULL,
    date_created_gmt datetime NOT NULL DEFAULT ‘0000-00-00 00:00:00’
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

    MySQL said: Documentation 1813 – Tablespace for table ‘wp.wp_actionscheduler_claims‘ exists. Please DISCARD the tablespace before IMPORT

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Barry

    (@barryhughes-1)

    Possibly you need to use CREATE TABLE IF NOT EXISTS (relevant docs here). Or, if the tables already exist, then you could perhaps remove the CREATE TABLE statements. What are you using to do the import?

    Thread Starter tonyzyc

    (@tonyzyc)

    I am running XAMPP on my local computer and importing the wordpress database.

    I don’t have the Action Scheduler plugin installed. Why are there such tables for Action Scheduler in my database?

    How do I uninstall and delete these tables from the database? Now, it is causing me to not be able to import the database

    Plugin Author Barry

    (@barryhughes-1)

    I don’t have the Action Scheduler plugin installed. Why are there such tables for Action Scheduler in my database?

    Action Scheduler is available as a plugin, but mostly it is included as a library for other plugins.

    A great example is WooCommerce—Action Scheduler is packaged up inside it—and lots of other plugins do the same thing. So, to answer your question, I would imagine that you installed some other plugin that happens to use Action Scheduler ‘behind the scenes’.

    How do I uninstall and delete these tables from the database?

    Well, I’m still not sure how you are building the data to be exported, so it’s a little hard to answer … but if it is via a tool like phpMyAdmin then there are probably options to enforce the use of CREATE TABLE IF NOT EXISTS like I noted in my last reply.

    Or, you could delete the tables from the destination database first of all, so long as you aren’t worried about losing data. Or, you could modify the SQL dump (again, per my earlier answer).

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.