InnoDB: Progress in percent: 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
2023-07-22T04:36:18.710403Z 3 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`admin` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T04:36:18.714269Z 3 [ERROR] InnoDB: Operating system error number 80 in a file operation.
2023-07-22T04:36:18.714814Z 3 [ERROR] InnoDB: Cannot create file '.\bnsmg_accountdb_trunk\admin.ibd'
2023-07-22T04:36:18.715046Z 3 [ERROR] InnoDB: The file '.\bnsmg_accountdb_trunk\admin.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 '.\bnsmg_accountdb_trunk\admin.ibd' under the 'datadir' of MySQL.
2023-07-22T04:56:08.540774Z 14 [ERROR] InnoDB: Operating system error number 80 in a file operation.
2023-07-22T04:56:08.541282Z 14 [ERROR] InnoDB: Cannot create file '.\bnsmg_accountdb_trunk\admin.ibd'
2023-07-22T04:56:08.541543Z 14 [ERROR] InnoDB: The file '.\bnsmg_accountdb_trunk\admin.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 '.\bnsmg_accountdb_trunk\admin.ibd' under the 'datadir' of MySQL.
2023-07-22T05:00:38.924367Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`codepay_order` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.925710Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`codepay_user` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.926927Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`giftcode` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.928937Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`player` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.930867Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`rechargeaccount` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.932739Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`serverlist` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:00:38.933889Z 18 [ERROR] InnoDB: Table `bnsmg_accountdb_trunk`.`tblbanlist` does not exist in the InnoDB internal data dictionary though MySQL is trying to drop it. Have you copied the .frm file of the table to the MySQL database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2023-07-22T05:01:18.509128Z 18 [ERROR] InnoDB: Operating system error number 80 in a file operation.
2023-07-22T05:01:18.509526Z 18 [ERROR] InnoDB: Cannot create file '.\bnsmg_accountdb_trunk\admin.ibd'
2023-07-22T05:01:18.509779Z 18 [ERROR] InnoDB: The file '.\bnsmg_accountdb_trunk\admin.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 '.\bnsmg_accountdb_trunk\admin.ibd' under the 'datadir' of MySQL.
2023-07-22T05:01:56.115931Z 20 [ERROR] InnoDB: Operating system error number 80 in a file operation.
2023-07-22T05:01:56.116288Z 20 [ERROR] InnoDB: Cannot create file '.\bnsmg_accountdb_trunk\admin.ibd'
2023-07-22T05:01:56.116529Z 20 [ERROR] InnoDB: The file '.\bnsmg_accountdb_trunk\admin.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 '.\bnsmg_accountdb_trunk\admin.ibd' under the 'datadir' of MySQL.