千家信息网

怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found

发表于:2025-11-15 作者:千家信息网编辑
千家信息网最后更新 2025年11月15日,这篇文章主要介绍"怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found",在日常操作中,相信很多人在怎么解决My
千家信息网最后更新 2025年11月15日怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found

这篇文章主要介绍"怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found",在日常操作中,相信很多人在怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found问题上存在疑惑,小编查阅了各式资料,整理出简单好用的操作方法,希望对大家解答"怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found"的疑惑有所帮助!接下来,请跟着小编一起来学习吧!

【问题描述】:
检查error log的时候发现大量warnings:
[Warning] InnoDB Error Table mysql.innodb_index_stats not found
[Warning] InnoDB Error Table mysql.innodb_table_stats not found
[Warning] InnoDB Error Table mysql.slave_master_info not found
[Warning] InnoDB Error Table mysql.slave_relay_log_info not found
[Warning] InnoDB Error Table mysql.slave_worker_info not found

或在打开innodb表时,在err-log里会打印出:
InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
Error: Fetch of persistent statistics requested for table "{databse_name}"."{table_name}" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.

【解决方案】:
先看看能否drop table,如果说表不存在,则继续下一步。

  1. DROP TABLE mysql.innodb_index_stats;

  2. DROP TABLE mysql.innodb_table_stats;

  3. DROP TABLE mysql.slave_master_info;

  4. DROP TABLE mysql.slave_relay_log_info;

  5. DROP TABLE mysql.slave_worker_info;


删除datadir下mysql数据库中的这五张表的frm文件(如有ibd也一并删除)

  1. rm -rf $datadir/mysql/innodb_index_stats.*

  2. rm -rf $datadir/mysql/innodb_table_stats.*

  3. rm -rf $datadir/mysql/slave_master_info.*

  4. rm -rf $datadir/mysql/slave_relay_log_info.*

  5. rm -rf $datadir/mysql/slave_worker_info.*


再执行如下语句,重新创建这五张表:

  1. USE mysql;


  2. CREATE TABLE `innodb_index_stats` (

  3. `database_name` varchar(64) COLLATE utf8_bin NOT NULL,

  4. `table_name` varchar(64) COLLATE utf8_bin NOT NULL,

  5. `index_name` varchar(64) COLLATE utf8_bin NOT NULL,

  6. `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

  7. `stat_name` varchar(64) COLLATE utf8_bin NOT NULL,

  8. `stat_value` bigint(20) unsigned NOT NULL,

  9. `sample_size` bigint(20) unsigned DEFAULT NULL,

  10. `stat_description` varchar(1024) COLLATE utf8_bin NOT NULL,

  11. PRIMARY KEY (`database_name`,`table_name`,`index_name`,`stat_name`)

  12. ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;


  13. CREATE TABLE `innodb_table_stats` (

  14. `database_name` varchar(64) COLLATE utf8_bin NOT NULL,

  15. `table_name` varchar(64) COLLATE utf8_bin NOT NULL,

  16. `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

  17. `n_rows` bigint(20) unsigned NOT NULL,

  18. `clustered_index_size` bigint(20) unsigned NOT NULL,

  19. `sum_of_other_index_sizes` bigint(20) unsigned NOT NULL,

  20. PRIMARY KEY (`database_name`,`table_name`)

  21. ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin STATS_PERSISTENT=0;


  22. CREATE TABLE `slave_master_info` (

  23. `Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file.',

  24. `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log currently being read from the master.',

  25. `Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last read event.',

  26. `Host` char(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'The host name of the master.',

  27. `User_name` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The user name used to connect to the master.',

  28. `User_password` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The password used to connect to the master.',

  29. `Port` int(10) unsigned NOT NULL COMMENT 'The network port used to connect to the master.',

  30. `Connect_retry` int(10) unsigned NOT NULL COMMENT 'The period (in seconds) that the slave will wait before trying to reconnect to the master.',

  31. `Enabled_ssl` tinyint(1) NOT NULL COMMENT 'Indicates whether the server supports SSL connections.',

  32. `Ssl_ca` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Authority (CA) certificate.',

  33. `Ssl_capath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path to the Certificate Authority (CA) certificates.',

  34. `Ssl_cert` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL certificate file.',

  35. `Ssl_cipher` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the cipher in use for the SSL connection.',

  36. `Ssl_key` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The name of the SSL key file.',

  37. `Ssl_verify_server_cert` tinyint(1) NOT NULL COMMENT 'Whether to verify the server certificate.',

  38. `Heartbeat` float NOT NULL,

  39. `Bind` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'Displays which interface is employed when connecting to the MySQL server',

  40. `Ignored_server_ids` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The number of server IDs to be ignored, followed by the actual server IDs',

  41. `Uuid` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The master server uuid.',

  42. `Retry_count` bigint(20) unsigned NOT NULL COMMENT 'Number of reconnect attempts, to the master, before giving up.',

  43. `Ssl_crl` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The file used for the Certificate Revocation List (CRL)',

  44. `Ssl_crlpath` text CHARACTER SET utf8 COLLATE utf8_bin COMMENT 'The path used for Certificate Revocation List (CRL) files',

  45. `Enabled_auto_position` tinyint(1) NOT NULL COMMENT 'Indicates whether GTIDs will be used to retrieve events from the master.',

  46. PRIMARY KEY (`Host`,`Port`)

  47. ) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Master Information';


  48. CREATE TABLE `slave_relay_log_info` (

  49. `Number_of_lines` int(10) unsigned NOT NULL COMMENT 'Number of lines in the file or rows in the table. Used to version table definitions.',

  50. `Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the current relay log file.',

  51. `Relay_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The relay log position of the last executed event.',

  52. `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'The name of the master binary log file from which the events in the relay log file were read.',

  53. `Master_log_pos` bigint(20) unsigned NOT NULL COMMENT 'The master log position of the last executed event.',

  54. `Sql_delay` int(11) NOT NULL COMMENT 'The number of seconds that the slave must lag behind the master.',

  55. `Number_of_workers` int(10) unsigned NOT NULL,

  56. `Id` int(10) unsigned NOT NULL COMMENT 'Internal Id that uniquely identifies this record.',

  57. PRIMARY KEY (`Id`)

  58. ) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Relay Log Information';


  59. CREATE TABLE `slave_worker_info` (

  60. `Id` int(10) unsigned NOT NULL,

  61. `Relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,

  62. `Relay_log_pos` bigint(20) unsigned NOT NULL,

  63. `Master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,

  64. `Master_log_pos` bigint(20) unsigned NOT NULL,

  65. `Checkpoint_relay_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,

  66. `Checkpoint_relay_log_pos` bigint(20) unsigned NOT NULL,

  67. `Checkpoint_master_log_name` text CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,

  68. `Checkpoint_master_log_pos` bigint(20) unsigned NOT NULL,

  69. `Checkpoint_seqno` int(10) unsigned NOT NULL,

  70. `Checkpoint_group_size` int(10) unsigned NOT NULL,

  71. `Checkpoint_group_bitmap` blob NOT NULL,

  72. PRIMARY KEY (`Id`)

  73. ) ENGINE=InnoDB DEFAULT CHARSET=utf8 STATS_PERSISTENT=0 COMMENT='Worker Information';

最后重启mysqld即可。

到此,关于"怎么解决MySQL中的5.6.x InnoDB Error Table mysql.innodb_table_stats not found"的学习就结束了,希望能够解决大家的疑惑。理论与实践的搭配能更好的帮助大家学习,快去试试吧!若想继续学习更多相关知识,请继续关注网站,小编会继续努力为大家带来更多实用的文章!

学习 更多 问题 帮助 实用 接下来 数据 数据库 文件 文章 方案 方法 时候 理论 知识 篇文章 网站 解决方案 语句 资料 数据库的安全要保护哪些东西 数据库安全各自的含义是什么 生产安全数据库录入 数据库的安全性及管理 数据库安全策略包含哪些 海淀数据库安全审计系统 建立农村房屋安全信息数据库 易用的数据库客户端支持安全管理 连接数据库失败ssl安全错误 数据库的锁怎样保障安全 华为网络技术群 数据库有数据定义等功能 哈普网络技术 java与数据库连接的心得 如何自建简易数据库 激战2捏脸男数据库 常州市万网网络技术有限公司 常用的服务器管理命令行 太仓运营网络技术咨询热线 数据库如何设置百分比 广东佛山络威网络技术有限公司 电脑进界面提示连接服务器失败 戴尔服务器维修点 天津什么是网络技术服务产品介绍 app登陆请求服务器失败 怎么将数据库导入本地 青岛乐透互联网络科技有限公司 网络安全模块的拼音 网络安全的五禁止是什么 石家庄服务器数据恢复 控制系统专业软件开发 Dell服务器管理口配置 怎么看服务器是真的还是假的 江苏陶欣伯助学基金会数据库 区块链技术还需要数据库吗 蓝色隐士怎么看服务器排队 网络安全视频资源共享 船舶网络安全管理计划 苹果登录服务器一直转圈圈 登封租房网络安全
0