Olá, estou com esse problema ao importar os meus banco de dados
LOG Error:
2022-01-17T17:19:14.610909Z 350 [Warning] InnoDB: Tablespace 'pequiemporio/wp_actionscheduler_actions' exists in the cache with id 1476 != 2366
2022-01-17T17:19:14.621994Z 350 [Warning] InnoDB: Tablespace 'pequiemporio/wp_actionscheduler_claims' exists in the cache with id 1477 != 2367
2022-01-17T17:19:14.630689Z 350 [Warning] InnoDB: Tablespace 'pequiemporio/wp_actionscheduler_groups' exists in the cache with id 1478 != 2368
2022-01-17T17:19:14.639703Z 350 [Warning] InnoDB: Tablespace 'pequiemporio/wp_actionscheduler_logs' exists in the cache with id 1479 != 2369
2022-01-17T17:19:14.644638Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.644653Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.644658Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.644661Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_cli_cookie_scan.ibd'
2022-01-17T17:19:14.644691Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_cli_cookie_scan.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_cli_cookie_scan.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.647568Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.647585Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.647589Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.647593Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_cli_cookie_scan_categories.ibd'
2022-01-17T17:19:14.647597Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_cli_cookie_scan_categories.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_cli_cookie_scan_categories.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.650663Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.650676Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.650680Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.650683Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_cli_cookie_scan_cookies.ibd'
2022-01-17T17:19:14.650687Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_cli_cookie_scan_cookies.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_cli_cookie_scan_cookies.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.653815Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.653828Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.653831Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.653835Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_cli_cookie_scan_url.ibd'
2022-01-17T17:19:14.653839Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_cli_cookie_scan_url.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_cli_cookie_scan_url.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.656915Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.656944Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.656948Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.656952Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_cli_scripts.ibd'
2022-01-17T17:19:14.656956Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_cli_scripts.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_cli_scripts.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.660116Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.660133Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.660137Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.660141Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_commentmeta.ibd'
2022-01-17T17:19:14.660144Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_commentmeta.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_commentmeta.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.663169Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.663187Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.663191Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.663194Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_comments.ibd'
2022-01-17T17:19:14.663198Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_comments.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_comments.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.667083Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.667096Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.667100Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.667104Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_e_submissions.ibd'
2022-01-17T17:19:14.667107Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_e_submissions.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_e_submissions.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.670253Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.670271Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.670282Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.670286Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_e_submissions_actions_log.ibd'
2022-01-17T17:19:14.670290Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_e_submissions_actions_log.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_e_submissions_actions_log.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.673414Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.673428Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.673431Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.673435Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_e_submissions_values.ibd'
2022-01-17T17:19:14.673438Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_e_submissions_values.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_e_submissions_values.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.676725Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.676738Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.676742Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.676745Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_links.ibd'
2022-01-17T17:19:14.676749Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_links.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_links.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.679797Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.679814Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.679819Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.679822Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_options.ibd'
2022-01-17T17:19:14.679826Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_options.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_options.ibd' under the 'datadir' of MySQL.
2022-01-17T17:19:14.746247Z 350 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2022-01-17T17:19:14.746267Z 350 [ERROR] InnoDB: Error number 17 means 'File exists'
2022-01-17T17:19:14.746271Z 350 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2022-01-17T17:19:14.746274Z 350 [ERROR] InnoDB: Cannot create file './pequiemporio/wp_postmeta.ibd'
2022-01-17T17:19:14.746279Z 350 [ERROR] InnoDB: The file './pequiemporio/wp_postmeta.ibd' already exists though the corresponding table did not exist in the InnoDB data dictionary. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file './pequiemporio/wp_postmeta.ibd' under the 'datadir' of MySQL.
