46611377152 2023-10-24T07:01:53.823797Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46616620032 2023-10-24T07:01:53.851715Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/ls_product_cate.ibd＇ with space ID 9681, since the redo log references ./test_hhrj/ls_product_cate.ibd with space ID 9680. 2023-10-24T07:01:53.868019Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46621862912 2023-10-24T07:01:53.917725Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46627105792 2023-10-24T07:01:53.968540Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46632348672 2023-10-24T07:01:54.023230Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46637591552 2023-10-24T07:01:54.073597Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46642834432 2023-10-24T07:01:54.089850Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID. 2023-10-24T07:01:54.089887Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID. 2023-10-24T07:01:54.090307Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46645103735 2023-10-24T07:01:54.090452Z 0 [Note] InnoDB: Database was not shutdown normally! 2023-10-24T07:01:54.090457Z 0 [Note] InnoDB: Starting crash recovery. 2023-10-24T07:01:54.091405Z 0 [ERROR] InnoDB: Tablespace 5935 was not found at ./test_php_chat_u/hx_index_visit.ibd. 2023-10-24T07:01:54.091411Z 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace. 2023-10-24T07:01:54.093818Z 0 [ERROR] InnoDB: Tablespace 9463 was not found at ./test_php_chat_i/ai_dev_crontab.ibd. 2023-10-24T07:01:54.094149Z 0 [ERROR] InnoDB: Tablespace 9484 was not found at ./test_php_chat_i/ai_index_visit.ibd. 2023-10-24T07:01:54.097484Z 0 [ERROR] InnoDB: Cannot continue operation.
46611377152 2023-10-24T07:01:53.823797Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46616620032 2023-10-24T07:01:53.851715Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/ls_product_cate.ibd＇ with space ID 9681, since the redo log references ./test_hhrj/ls_product_cate.ibd with space ID 9680. 2023-10-24T07:01:53.868019Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46621862912 2023-10-24T07:01:53.917725Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46627105792 2023-10-24T07:01:53.968540Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46632348672 2023-10-24T07:01:54.023230Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46637591552 2023-10-24T07:01:54.073597Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46642834432 2023-10-24T07:01:54.089850Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID. 2023-10-24T07:01:54.089887Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID. 2023-10-24T07:01:54.090307Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46645103735 2023-10-24T07:01:54.090452Z 0 [Note] InnoDB: Database was not shutdown normally! 2023-10-24T07:01:54.090457Z 0 [Note] InnoDB: Starting crash recovery. 2023-10-24T07:01:54.091405Z 0 [ERROR] InnoDB: Tablespace 5935 was not found at ./test_php_chat_u/hx_index_visit.ibd. 2023-10-24T07:01:54.091411Z 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace. 2023-10-24T07:01:54.093818Z 0 [ERROR] InnoDB: Tablespace 9463 was not found at ./test_php_chat_i/ai_dev_crontab.ibd. 2023-10-24T07:01:54.094149Z 0 [ERROR] InnoDB: Tablespace 9484 was not found at ./test_php_chat_i/ai_index_visit.ibd. 2023-10-24T07:01:54.097484Z 0 [ERROR] InnoDB: Cannot continue operation.
46611377152
2023-10-24T07:01:53.823797Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46616620032
2023-10-24T07:01:53.851715Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/ls_product_cate.ibd＇ with space ID 9681, since the redo log references ./test_hhrj/ls_product_cate.ibd with space ID 9680.
2023-10-24T07:01:53.868019Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46621862912
2023-10-24T07:01:53.917725Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46627105792
2023-10-24T07:01:53.968540Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46632348672
2023-10-24T07:01:54.023230Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46637591552
2023-10-24T07:01:54.073597Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46642834432
2023-10-24T07:01:54.089850Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID.
2023-10-24T07:01:54.089887Z 0 [Note] InnoDB: Ignoring data file ＇./test_hhrj/#sql-ib9712-1332999540.ibd＇ with space ID 9681. Another data file called ./test_hhrj/ls_product_cate.ibd exists with the same space ID.
2023-10-24T07:01:54.090307Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46645103735
2023-10-24T07:01:54.090452Z 0 [Note] InnoDB: Database was not shutdown normally!
2023-10-24T07:01:54.090457Z 0 [Note] InnoDB: Starting crash recovery.
2023-10-24T07:01:54.091405Z 0 [ERROR] InnoDB: Tablespace 5935 was not found at ./test_php_chat_u/hx_index_visit.ibd.
2023-10-24T07:01:54.091411Z 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2023-10-24T07:01:54.093818Z 0 [ERROR] InnoDB: Tablespace 9463 was not found at ./test_php_chat_i/ai_dev_crontab.ibd.
2023-10-24T07:01:54.094149Z 0 [ERROR] InnoDB: Tablespace 9484 was not found at ./test_php_chat_i/ai_index_visit.ibd.
2023-10-24T07:01:54.097484Z 0 [ERROR] InnoDB: Cannot continue operation.
用户500598139
2023年10月24日
|
浏览 183
根据提供的日志信息，出现了一些与InnoDB存储引擎相关的错误。以下是对每个错误的简要解释：
-
Ignoring data file ‘./test_hhrj/ls_product_cate.ibd’ with space ID 9681, since the redo log references ‘./test_hhrj/ls_product_cate.ibd’ with space ID 9680.
这个错误表示由于重做日志引用了与空间ID 9681关联的数据文件’./test_hhrj/ls_product_cate.ibd’，因此忽略了与空间ID 9680关联的数据文件。 -
Tablespace 5935 was not found at ‘./test_php_chat_u/hx_index_visit.ibd’.
这个错误表示在’./test_php_chat_u/hx_index_visit.ibd’中找不到表空间5935。 -
Tablespace 9463 was not found at ‘./test_php_chat_i/ai_dev_crontab.ibd’.
这个错误表示在’./test_php_chat_i/ai_dev_crontab.ibd’中找不到表空间9463。 -
Tablespace 9484 was not found at ‘./test_php_chat_i/ai_index_visit.ibd’.
这个错误表示在’./test_php_chat_i/ai_index_visit.ibd’中找不到表空间9484。
针对这些错误，您可以尝试以下解决方案：
- 检查日志中提到的数据文件是否存在，并确保它们位于正确的位置。
- 如果您有备份，请尝试恢复备份并重新启动数据库。
- 如果不需要丢失对表空间所做的更改，请根据错误消息中的建议，将innodb_force_recovery设置为1，然后重新启动数据库。请注意，这可能会导致数据丢失。
- 如果以上方法都无效，您可能需要联系数据库管理员或专业的MySQL支持团队以获取进一步的帮助。
请记住，这些只是一些可能的解决方案，具体的解决方法可能需要根据您的特定情况进行调整。
我要提问
复制内容
分享给好友
AI编程问答网 免责声明：
以上内容除特别注明外均来源于网友提问，AI编程问答网回答，权益归原著者所有；
下一篇：简历教育经历怎么写