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 ...
随机推荐
- Hive里的分区、分桶、视图和索引再谈
福利 => 每天都推送 欢迎大家,关注微信扫码并加入我的4个微信公众号: 大数据躺过的坑 Java从入门到架构师 人工智能躺过的坑 Java全栈大联盟 ...
- vue中 v-cloak 的用法
原文来自:http://www.sunzhongwei.com/hide-vuejs-variable-with-v-cloak-when-page-loading
- spark源码编译,本地调试
1.下载源码 2.进入源码根据README.md编译源码,注意使用的是源码目录下的maven编译 3.用idea导入顶层pom文件 4.修改顶层pom文件和example下的pom文件,将scope的 ...
- 前端js中this指向及改变this指向的方法
js中this指向是一个难点,花了很长时间来整理和学习相关的知识点. 一. this this是JS中的关键字, 它始终指向了一个对象, this是一个指针; 参考博文: JavaScript函数中的 ...
- 搭建并配置本地GitLab服务器教程
由于工作单位不一定能够方便使用外部网络,现以下载rpm包来搭建一套本地GitLab服务器. 1. 系统准备 系统:redhat 7.3 2. 下载所需安装包 去官网下rpm包,下载地址,ce是免费的社 ...
- Mac使用Docker-machine訪问docker publish port
Step 1.Export the port in your container(docker-machine or boot2docker) 首先,要保证你公布port的image已经run起来了. ...
- hdoj-1289-A Bug's Life【种类并查集】
A Bug's Life Time Limit: 15000/5000 MS (Java/Others) Memory Limit: 32768/32768 K (Java/Others) Total ...
- linux host主机名配置
1.查看主机名 #hostname 2.查看ip #ifconfig 2.添加主机名配置 #vi /etc/hosts 新增一行 172.23.26.195 vhost145.idmp.safe
- vim-复制、粘贴
选中某些行,可以在命令行模式下执行如下操作 v(小写),按上下左右键,可以选中某些行 V(大写),按上下键,这时候可以直接选中光标所在的行 ctrl+v(小写),可以选中一个矩形区域 取消选中,这些指 ...
- Spring中JDBCTemplate的入门
Spring是IOC和AOP的容器框架,一站式的框架 连接数据库的步骤:[必须会写] Spring当中如何配置连接数据库? 第一步配置核心配置文件: <?xml version="1. ...