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的更多相关文章

  1. 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 ...

  2. 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.输 ...

  3. "Native table 'performance_schema'.'session_variables' has the wrong structure") [SQL: "SHOW VARIABLES LIKE 'sql_mode'"]

    mysql_upgrade -u root -p--force 升级完重启

  4. 修复mysql:[ERROR] Native table ‘performance_schema’

    转: http://www.amznz.com/error-native-table-performance_schema/ mysql数据库出现如下错误,主要是因为升级了mysql软件包,而一些数据 ...

  5. Mysql 升级重装后连接出错 Table \'performance_schema.session_variables\' doesn\'t exist

    升级重装后  连接出错 报这个错误 Table 'performance_schema.session_variables' doesn't exist   使用这个命令即可 [root@localh ...

  6. Table ‘performance_schema.session_variables’ doesn’t exist

    运行mysql时,提示Table ‘performance_schema.session_variables’ doesn’t exist 解决的方法是: 第一步:在管理员命令中输入: mysql_u ...

  7. linux下apt安装mysql导致mysql.user table is damaged

    笔者在ubuntu下用 apt install mysql-server类似的命令安装mysql, 安装了最新版的mysql5.7,覆盖了操作系统内置的数据库mysql系统库. 最初启动mysql出错 ...

  8. Table 'performance_schema.session_status' doesn't exist错误,解决办法

    Mysql升级到5.7+之后一直出现Table 'performance_schema.session_status' doesn't exist错误,解决办法 1. 进入Mysql的安装目录的bin ...

  9. mysqldump导出备份数据库报Table ‘performance_schema.session_variables‘ doesn‘t exist

    今天在bash进行本地数据库往云端数据库导数据的时候,在本地导出.sql文件这第一步就出现了错误问题,导出sql文件的命令: mysqldump -u 用户名 -p 数据库名 > xxx.sql ...

随机推荐

  1. es68对象的解构赋值

    <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8&quo ...

  2. Flat UI简介

    Flat UI简介 一.简介 Flat UI是基于Bootstrap之上进行二次开发的扁平化前端框架,他提供了动感.时尚的风格色调搭配,简洁.炫丽的功能组件,同时还提供了更为平滑的js交互动画,可以称 ...

  3. 学大伟业Day解题报告

    预计分数:30+30+0=60 实际分数:30+20+0=50 题解部分全部来自http://www.cnblogs.com/TheRoadToTheGold/p/7723564.html T1htt ...

  4. 分享一个vue常用的ui控件

      vue学习文档 http://www.jianshu.com/p/8a272fc4e8e8 vux github ui demo:https://github.com/airyland/vux M ...

  5. C/C++(基础-常量,类型转换)

    字符 char ascII码表 #include<stdio.h> int main() { unsigned char ch; for(ch = 0;ch < 128;ch++) ...

  6. SQL、Linq相关字段搜索

    结合一些分词组件,如盘古,对于用户查询关键字红按钮很容易分出 ‘红’ ‘按钮’二个单词 我们假设产品名称列里面是红色,规格里面是按钮 /* 普通sql实现全文搜索declare @key1 nvarc ...

  7. Python day4知识回顾

    # -*- coding: utf_8 _*_# Author:Vi#字典是无序的 info = { 'student001':"DIO", 'student002':" ...

  8. IOS - 获取UITextField的输入文本

    当UITextField文本改变时, 依据内容更新数据, 通过写监听事件就可以. 加入监听: [timesField addTarget:self action:@selector(textField ...

  9. Python 标准库 csv —— csv 文件的读写

    csv 文件,逗号分割文件. 0. 读取 csv 到 list from csv import reader def load_csv(csvfile): dataset = [] with open ...

  10. python3操作Excel

    1.安装openpyxl模块: 在cmd命令窗执行命令 pip install openpyxl    安装openpyxl模块 from openpyxl import load_workbook ...