Support » Plugin: WP STAGING - Backup Duplicator & Migration » Database error occur.

  • Resolved cheonmu

    (@cheonmu)


    Hi,

    When i using staging website, lots of database error.

    And i check error log, I get below error It is recorded.

    Could you tell me how do i solved this problem or what do i need check on my server again?

    Thank you

    
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9352. Another data file called ./seoart/wp_4_wfconfig.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9353. Another data file called ./seoart/wp_4_wfcrawlers.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9353. Another data file called ./seoart/wp_4_wfcrawlers.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9353. Another data file called ./seoart/wp_4_wfcrawlers.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9354. Another data file called ./seoart/wp_4_wffilechanges.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9354. Another data file called ./seoart/wp_4_wffilechanges.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9354. Another data file called ./seoart/wp_4_wffilechanges.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9355. Another data file called ./seoart/wp_4_wffilemods.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9355. Another data file called ./seoart/wp_4_wffilemods.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9355. Another data file called ./seoart/wp_4_wffilemods.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9356. Another data file called ./seoart/wp_4_wfhits.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9356. Another data file called ./seoart/wp_4_wfhits.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9356. Another data file called ./seoart/wp_4_wfhits.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9357. Another data file called ./seoart/wp_4_wfhoover.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9357. Another data file called ./seoart/wp_4_wfhoover.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9357. Another data file called ./seoart/wp_4_wfhoover.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9358. Another data file called ./seoart/wp_4_wfissues.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9358. Another data file called ./seoart/wp_4_wfissues.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9358. Another data file called ./seoart/wp_4_wfissues.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9359. Another data file called ./seoart/wp_4_wfknownfilelist.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9359. Another data file called ./seoart/wp_4_wfknownfilelist.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9359. Another data file called ./seoart/wp_4_wfknownfilelist.ibd exists with the same space ID.
    2021-07-20  5:53:54 0 [Note] InnoDB: Ignoring data file './seoart/#sql-alter-5cf25-72.ibd' with space ID 9359. Another data file called ./seoart/wp_4_wfknownfilelist.ibd exists with the same space ID.
    
    • This topic was modified 4 months, 1 week ago by cheonmu.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Rene Hermenau

    (@renehermi)

    Hello,

    these look like fundamental errors in your database tables.
    Please try to optimize and repair these tables with PhpMyAdmin.

    Does it help?

    However, these tables are no staging tables and belong to your production site, so this error does not seem to be related to WP STAGING at all.

    Cheers
    René

    Thread Starter cheonmu

    (@cheonmu)

    Hi, @renehermi

    Thanks for answering.

    I have optimized and repaired my database already.

    But nothing changed.

    Anyway, it’s okay to know that the cause of the database error is in my Database, not the plugin.

    I’ll check my database later as other problems may arise.

    Thank you.

    • This reply was modified 4 months, 1 week ago by cheonmu.
    Plugin Author Rene Hermenau

    (@renehermi)

    I hope you are able to fix it. Please feel free to post your solution here. It could be useful for other WordPress users, too.

    Btw. My developers’ heart was curious, so I’ve found something related:

    https://jira.mariadb.org/browse/MDEV-20755
    https://bugs.mysql.com/bug.php?id=75614

    If you are not able to repair of the tables, you can still do a full SQL dump and then import that dump into a new database.

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