mysql :Native table 'performance_schema'.'cond_instances' has the wrong structure
err:
150418 13:25:06 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
150418 13:25:06 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
有人建议使用%MYSQL%/bin/mysql_upgrade -u root –p 来修复。
但启动后仍然有如下日志:
150421 14:06:31 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
150421 14:06:59 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
150421 14:07:26 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
select table_name from information_schema.tables where table_schema='mysql' and engine='InnoDB';
+----------------------+
| table_name |
+----------------------+
| gtid_slave_pos |
| innodb_index_stats |
| innodb_table_stats |
| slave_master_info |
| slave_relay_log_info |
| slave_worker_info |
+----------------------+
> use mysql
> select * from gtid_slave_pos;
ERROR 1932 (42S02): Table 'mysql.gtid_slave_pos' doesn't exist in engine
> drop table gtid_slave_pos;
Query OK, 0 rows affected, 1 warning (0.00 sec)
拷贝%MYSQL%\share\mysql_system_tables.sql 中创建 gtid_slave_pos语句执行。
CREATE TABLE IF NOT EXISTS gtid_slave_pos (
domain_id INT UNSIGNED NOT NULL,
sub_id BIGINT UNSIGNED NOT NULL,
server_id INT UNSIGNED NOT NULL,
seq_no BIGINT UNSIGNED NOT NULL,
PRIMARY KEY (domain_id, sub_id))
COMMENT='Replication slave GTID position';
ERROR 1813 (HY000): Tablespace for table '`mysql`.`gtid_slave_pos`' exists. Please DISCARD the table
space before IMPORT.
> show variables like '%data%';
+-------------------------------+--------------------------+
| Variable_name | Value |
+-------------------------------+--------------------------+
| character_set_database | utf8 |
| collation_database | utf8_general_ci |
| datadir | E:\database\MYSQL\ |
| innodb_data_file_path | ibdata1:10M:autoextend |
| innodb_data_home_dir | E:\database\innodb_home\ |
| innodb_stats_on_metadata | OFF |
| max_length_for_sort_data | 1024 |
| max_long_data_size | 1048576 |
| metadata_locks_cache_size | 1024 |
| metadata_locks_hash_instances | 8 |
| myisam_data_pointer_size | 6 |
| skip_show_database | OFF |
| updatable_views_with_limit | YES |
+-------------------------------+--------------------------+
删除E:\database\MYSQL\mysql\gtid_slave_pos.*
重复gtid_slave_pos 执行创建表语句,该问题解决。
mysql :Native table 'performance_schema'.'cond_instances' has the wrong structure的更多相关文章
- mysqldump: Couldn't execute 'SHOW VARIABLES LIKE 'ndbinfo_version'': Native table 'performance_schema'.'session_variables' has the wrong structure (1682)
centos7.5 导出整个数据库报错 问题: [root@db01 ~]# mysqldump -uroot -pBgx123.com --all-databases --single-transa ...
- ubuntu14.04 mysql-workbench Connecting to MySQL server ... Native table 'performance_schema'.'session_variables' has the wrong structure错误解决
使用的mysql版本: mysql Ver 14.14 Distrib 5.7.9, for Linux (x86_64) using EditLine wrapper 打开shell命令 1.输 ...
- "Native table 'performance_schema'.'session_variables' has the wrong structure") [SQL: "SHOW VARIABLES LIKE 'sql_mode'"]
mysql_upgrade -u root -p--force 升级完重启
- 修复mysql:[ERROR] Native table ‘performance_schema’
转: http://www.amznz.com/error-native-table-performance_schema/ mysql数据库出现如下错误,主要是因为升级了mysql软件包,而一些数据 ...
- Mysql 升级重装后连接出错 Table \'performance_schema.session_variables\' doesn\'t exist
升级重装后 连接出错 报这个错误 Table 'performance_schema.session_variables' doesn't exist 使用这个命令即可 [root@localh ...
- Table ‘performance_schema.session_variables’ doesn’t exist
运行mysql时,提示Table ‘performance_schema.session_variables’ doesn’t exist 解决的方法是: 第一步:在管理员命令中输入: mysql_u ...
- linux下apt安装mysql导致mysql.user table is damaged
笔者在ubuntu下用 apt install mysql-server类似的命令安装mysql, 安装了最新版的mysql5.7,覆盖了操作系统内置的数据库mysql系统库. 最初启动mysql出错 ...
- Table 'performance_schema.session_status' doesn't exist错误,解决办法
Mysql升级到5.7+之后一直出现Table 'performance_schema.session_status' doesn't exist错误,解决办法 1. 进入Mysql的安装目录的bin ...
- mysqldump导出备份数据库报Table ‘performance_schema.session_variables‘ doesn‘t exist
今天在bash进行本地数据库往云端数据库导数据的时候,在本地导出.sql文件这第一步就出现了错误问题,导出sql文件的命令: mysqldump -u 用户名 -p 数据库名 > xxx.sql ...
随机推荐
- 60.浅谈nodejs中的Crypto模块
转自:https://www.cnblogs.com/c-and-unity/articles/4552059.html node.js的crypto在0.8版本并没有改版多少,这个模块的主要功能是加 ...
- ajax ---- json 和 xml 区别
2.XML和JSON优缺点 (1).XML的优缺点<1>.XML的优点 A.格式统一,符合标准: B.容易与其他系统进行远程交互,数据共享比较方便.<2>.XML的缺点 A.X ...
- 洛谷 P1757 通天之分组背包
P1757 通天之分组背包 题目背景 直达通天路·小A历险记第二篇 题目描述 自01背包问世之后,小A对此深感兴趣.一天,小A去远游,却发现他的背包不同于01背包,他的物品大致可分为k组,每组中的物品 ...
- 洛谷 P2108 学英语
P2108 学英语 题目描述 为了适应紧张的大学学习生活,小Z发愤图强开始复习巩固英语. 由于小Z对数学比较有好感,他首先复习了数词.小Z花了一整天的时间,终于把关于基数词的知识都搞懂了.于是小Z非常 ...
- 关于oracle sql语句查询时 表名和字段名要加双引號的问题具体解释
作为oracle的刚開始学习的人相信大家一定会遇到这个问题.如图: 明明就是navicat可视化创建了表,但是就是不能查到!这个为什么呢? select * ...
- 徒弟们对话,遇到sb领导,离职吧
由于涉及私密,所以qq号做了干扰.见谅. 非常多人以为在公司,你优化了几十个sql老板就给你涨工资了.或者你bbed搞点特殊恢复就涨工资了. 或者解决某些棘手问题就涨工资了. 那是不正确的. 遇 ...
- struts2中action手动获取參数
struts2中action手动获取Session,jsp页面參数 1. ActionContext 在Struts2开发中,除了将请求參数自己主动设置到Action的字段中,我们往往也须要在Acti ...
- php学习笔记6
PHP 字符串变量 PHP 中的字符串变量 字符串变量用于包含有字符的值. 在创建字符串之后,我们就可以对它进行操作了.您可以直接在函数中使用字符串,或者把它存储在变量中. 在下面的实例中,我们创建一 ...
- Spring CORS
转载:Spring MVC 4.2 增加 CORS 支持 http://spring.io/blog/2015/06/08/cors-support-in-spring-framework http: ...
- ORACLE10g R2【单实例 FS→单实例FS】
ORACLE10g R2[单实例FS→单实例FS] 本演示案例所用环境: primary standby OS Hostname pry std OS Version RHEL5.8 RHEL5. ...