按照教程部署铛铛

Shyloc

复制了mysql目录下的data文件夹后，数据库没法启动了了，一点开就闪退

jishuang

mysql数据库就是标准的，可以通过cmd的方式到bin目录下调用命令处理，看具体的错误

Shyloc

E:\BeX5_V3.8>启动MySQL数据库.bat
正在启动MySQL...
.
...小提示..................................................................
.                                                                         .
. MySQL默认参数                                                           .
. 主机名/IP：127.0.0.1                                                    .
. 用户名：root                                                            .
. 密码：x5                                                                .
. 端口：3306                                                              .
.                                                                         .
...........................................................................
2020-05-29 13:28:09 0 [Warning] TIMESTAMP with implicit DEFAULT value is depreca
ted. Please use --explicit_defaults_for_timestamp server option (see documentati
on for more details).
2020-05-29 13:28:09 0 [Note] mysqld (mysqld 5.6.26) starting as process 9660 ...

2020-05-29 13:28:09 9660 [Note] Plugin 'FEDERATED' is disabled.
2020-05-29 13:28:09 9660 [Note] InnoDB: Using atomics to ref count buffer pool p
ages
2020-05-29 13:28:09 9660 [Note] InnoDB: The InnoDB memory heap is disabled
2020-05-29 13:28:09 9660 [Note] InnoDB: Mutexes and rw_locks use Windows interlo
cked functions
2020-05-29 13:28:09 9660 [Note] InnoDB: Memory barrier is not used
2020-05-29 13:28:09 9660 [Note] InnoDB: Compressed tables use zlib 1.2.3
2020-05-29 13:28:09 9660 [Note] InnoDB: Not using CPU crc32 instructions
2020-05-29 13:28:09 9660 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-05-29 13:28:09 9660 [Note] InnoDB: Completed initialization of buffer pool
2020-05-29 13:28:09 9660 [Note] InnoDB: Highest supported file format is Barracu
da.
2020-05-29 13:28:09 9660 [Note] InnoDB: The log sequence numbers 8654514 and 865
4514 in ibdata files do not match the log sequence number 54876218 in the ib_log
files!
2020-05-29 13:28:09 9660 [Note] InnoDB: Database was not shutdown normally!
2020-05-29 13:28:09 9660 [Note] InnoDB: Starting crash recovery.
2020-05-29 13:28:09 9660 [Note] InnoDB: Reading tablespace information from the
.ibd files...
2020-05-29 13:28:09 9660 [ERROR] InnoDB: Attempted to open a previously opened t
ablespace. Previous tablespace takeout/takeout_food uses space ID: 6 at filepath
: .\takeout\takeout_food.ibd. Cannot open tablespace x5/takeout_food which uses
space ID: 6 at filepath: .\x5\takeout_food.ibd
InnoDB: Error: could not open single-table tablespace file .\x5\takeout_food.ibd

InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

E:\BeX5_V3.8\mysql\bin>

jishuang

Cannot open tablespace  mysql数据库标准的报错到网上查找

Shyloc

不行，能打开但是读不到粘进去的铛铛的数据

Shyloc

啊。不成，网上办法摆不平，成功启动数据库了也读取不到数据库表

jishuang

把数据库重新弄，在拷贝的是否要确保数据库服务没有启动

Shyloc

jishuang 发表于 2020-5-29 18:10
把数据库重新弄，在拷贝的是否要确保数据库服务没有启动

重新弄了也不行，数据加载不进去

Shyloc

jishuang 发表于 2020-5-29 18:10
把数据库重新弄，在拷贝的是否要确保数据库服务没有启动

转储也不行，这个库到这里就卡住了

jishuang

这个就是据库的标准操作，到网上查找处理方案