error-mysql InnoDB: Error: “mysql”.”innodb_table_stats

PRIMARY KEY (`db`,`name`,`type`)  

2015-06-23 22:39:39 1190 [Warning] Buffered warning: Changed limits:
table_cache: 431 (requested 2000)

此外的也足以由此那条语句修改:

  

mysql InnoDB: Error: “mysql”.”innodb_table_stats
屈居错误日志:

可是只要您曾经济建设了库和表能够透过以下措施进行询问。

`sql_data_access`
enum(‘CONTAINS_SQL’,’NO_SQL’,’READS_SQL_DATA’,
‘MODIFIES_SQL_DATA’) NOT NULL   

150623 22:39:12 mysqld_safe mysqld from pid file
/var/run/mysqld/mysqld.pid ended
150623 22:39:39 mysqld_safe Starting mysqld daemon with databases from
/var/lib/mysql
2015-06-23 22:39:39 0 [Warning] TIMESTAMP with implicit DEFAULT value
is deprecated. Please use –explicit_defaults_for_timestamp server
option (see documentation for more details).
2015-06-23 22:39:39 1190 [Warning] Buffered warning: Changed limits:
max_open_files: 1024 (requested 5000)

set character_set_client=’utf8′;

下一场实施以下代码重建该表,经测试成功. 

2015-06-23 22:39:06 1252 [Note] Giving 0 client threads a chance to
die gracefully
2015-06-23 22:39:06 1252 [Note] Shutting down slave threads
2015-06-23 22:39:06 1252 [Note] Forcefully disconnecting 0 remaining
clients
2015-06-23 22:39:06 1252 [Note] Binlog end
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘partition’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘BLACKHOLE’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘PERFORMANCE_SCHEMA’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_DATAFILES’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_TABLESPACES’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_FOREIGN_COLS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_FOREIGN’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_FIELDS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_COLUMNS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_INDEXES’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_TABLESTATS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_SYS_TABLES’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_INDEX_TABLE’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_INDEX_CACHE’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_CONFIG’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_BEING_DELETED’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_DELETED’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_FT_DEFAULT_STOPWORD’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_METRICS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_BUFFER_POOL_STATS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_BUFFER_PAGE_LRU’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_BUFFER_PAGE’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_CMP_PER_INDEX_RESET’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_CMP_PER_INDEX’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_CMPMEM_RESET’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_CMPMEM’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_CMP_RESET’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘INNODB_CMP’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin
‘INNODB_LOCK_WAITS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘INNODB_LOCKS’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘INNODB_TRX’
2015-06-23 22:39:09 1252 [Note] Shutting down plugin ‘InnoDB’
2015-06-23 22:39:09 1252 [Note] InnoDB: FTS optimize thread exiting.
2015-06-23 22:39:09 1252 [Note] InnoDB: Starting shutdown…
2015-06-23 22:39:12 1252 [Note] InnoDB: Shutdown completed; log
sequence number 44832642
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘ARCHIVE’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘MyISAM’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘CSV’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘MRG_MYISAM’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘MEMORY’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin
‘sha256_password’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin
‘mysql_old_password’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin
‘mysql_native_password’
2015-06-23 22:39:12 1252 [Note] Shutting down plugin ‘binlog’
2015-06-23 22:39:12 1252 [Note] /usr/sbin/mysqld: Shutdown complete

CREATE DATABASE `test`

`created` timestamp NOT NULL default CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP,  

2015-06-23 22:39:39 1190 [Note] Plugin ‘FEDERATED’ is disabled.
2015-06-23 22:39:39 1190 [Note] InnoDB: Using atomics to ref count
buffer pool pages
2015-06-23 22:39:39 1190 [Note] InnoDB: The InnoDB memory heap is
disabled
2015-06-23 22:39:39 1190 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2015-06-23 22:39:39 1190 [Note] InnoDB: Memory barrier is not used
2015-06-23 22:39:39 1190 [Note] InnoDB: Compressed tables use zlib
1.2.3
2015-06-23 22:39:39 1190 [Note] InnoDB: Using Linux native AIO
2015-06-23 22:39:39 1190 [Note] InnoDB: Not using CPU crc32
instructions
2015-06-23 22:39:39 1190 [Note] InnoDB: Initializing buffer pool, size
= 1.0G
2015-06-23 22:39:40 1190 [Note] InnoDB: Completed initialization of
buffer pool
2015-06-23 22:39:40 1190 [Note] InnoDB: Highest supported file format
is Barracuda.
2015-06-23 22:39:40 1190 [Note] InnoDB: 128 rollback segment are
active.
2015-06-23 22:39:40 1190 [Note] InnoDB: Waiting for purge to start
2015-06-23 22:39:40 1190 [Note] InnoDB: 5.6.22 started; log sequence
number 44832642
2015-06-23 22:39:41 1190 [Note] Server hostname (bind-address): ‘*’;
port: 3306
2015-06-23 22:39:41 1190 [Note] IPv6 is available.
2015-06-23 22:39:41 1190 [Note] – ‘::’ resolves to ‘::’;
2015-06-23 22:39:41 1190 [Note] Server socket created on IP: ‘::’.
2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table
mysql.db: expected column ‘User’ at position 2 to have type char, found
type char.
2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table
mysql.event: expected column ‘definer’ at position 3 to have type char,
found type char.
2015-06-23 22:39:41 1190 [ERROR] Incorrect definition of table
mysql.event: expected column ‘sql_mode’ at position 14 to have type
set(‘REAL_AS_FLOAT’,’PIPES_AS_CONCAT’,’ANSI_QUOTES’,’IGNORE_SPACE’,’NOT_USED’,’ONLY_FULL_GROUP_BY’,’NO_UNSIGNED_SUBTRACTION’,’NO_DIR_IN_CREATE’,’POSTGRESQL’,’ORACLE’,’MSSQL’,’DB2′,’MAXDB’,’NO_KEY_OPTIONS’,’NO_TABLE_OPTIONS’,’NO_FIELD_OPTIONS’,’MYSQL323′,’MYSQL40′,’ANSI’,’NO_AUTO_VALUE_ON_ZERO’,’NO_BACKSLASH_ESCAPES’,’STRICT_TRANS_TABLES’,’STRICT_ALL_TABLES’,’NO_ZERO_IN_DATE’,’NO_ZERO_DATE’,’INVALID_DATES’,’ERROR_FOR_DIVISION_BY_ZERO’,’TRADITIONAL’,’NO_AUTO_CREATE_USER’,’HIGH_NOT_PRECEDENCE’,’NO_ENGINE_SUBSTITUTION’,’PAD_CHAR_TO_FULL_LENGTH’),
found type
set(‘REAL_AS_FLOAT’,’PIPES_AS_CONCAT’,’ANSI_QUOTES’,’IGNORE_SPACE’,’IGNORE_BAD_TABLE_OPTIONS’,’ONLY_FULL_GROUP_BY’,’NO_UNSIGNED_SUBTRACTION’,’NO_DIR_IN_CREATE’,’POSTGRESQL’,’ORACLE’,’MSSQL’,’DB2′,’MAXDB’,’NO_KEY_OPTIONS’,’NO_TABLE_OPTIONS’,’NO_FIELD_OPTIONS’,’MYSQL323′,’MYSQL40′,’ANSI’,’NO_AUTO_VALUE_ON_ZERO’,’NO_BACKSLASH_ESCAPES’,’STRICT_TRANS_TABLES’,’STRICT_A
2015-06-23 22:39:41 1190 [ERROR] Event Scheduler: An error occurred
when initializing system tables. Disabling the Event Scheduler.
2015-06-23 22:39:41 1190 [Note] /usr/sbin/mysqld: ready for
connections.
Version: ‘5.6.22’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MySQL
Community Server
2015-06-23 23:00:47 7f7038bc0700 InnoDB: Error: Column last_update in
table “mysql”.”innodb_table_stats” is INT UNSIGNED NOT NULL but should
be BINARY NOT NULL (type mismatch).
2015-06-23 23:00:47 7f7038bc0700 InnoDB: Error: Fetch of persistent
statistics requested for table “moodle”.”mdl_config” 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.

MySQL会并发汉语乱码的缘故不外乎下列几点:
1.server自己设定难点,譬如还停留在latin1
2.table的语系设定难点(包括character与collation)
3.客户端程式(举例php)的连线语系设定难点
一、制止制造数据库及表现身中文乱码和查阅编码方法
1、创设数据库的时候:

  

CHARACTER SET ‘utf8’
    COLLATE ‘utf8_general_ci’;
2、建表的时候 CREATE TABLE `database_user` (
`ID` varchar(40) NOT NULL default ”,
`UserID` varchar(40) NOT NULL default ”,
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

`language` enum(‘SQL’) NOT NULL default ‘SQL’,  

ALTER DATABASE `db_name` CHARACTER SET utf8;

  

正解是:在MySQL的安装文件中进入bin目录下,双击MySQLInstanceConfig.exe,重新走三回server的安插,但要求专注的是,在Character
Set环节,要挑选第三项,character选取utf8,(第一项是暗中认可server字符集为latin1)。

default ‘CONTAINS_SQL’,  

那3个设置好了,基本就不会出标题了,即建库和建表时都使用同样的编码格式。

`param_list` blob NOT NULL,  

对此数据库字符集,能够透过那一个命令改变:

_NOT_PRECEDENCE’) NOT NULL default ”,  

MySQL写入汉语乱码之管理character_set_server编码(mysql暗中同意编码latin1)。Java连接MySQL时,写入到数据库的粤语,常常会编程乱码。
  

`sql_mode` set  

但是,character_set_server要是默感觉latin1,要长久改换,用set命令是无用的,而退换my.ini文件,也远非意义。 

自个儿在开立存储进度的时候出现”错误码: 1307 Failed to CREATE PROCEDURE

完结布署后,重启MySQL,写入的数目到MySQL中就是中文啦。为了消除中文乱码,你是还是不是还在不停的卸载重装MySQL呢?试试这些主意吧!

`modified` timestamp NOT NULL default ‘0000-00-00 00:00:00’,  

1.翻看私下认可的编码格式:
mysql> show variables like
“%char%”;
+————————–+—————+
| Variable_name | Value |
+————————–+—————+
| character_set_client | gbk |
| character_set_connection | gbk |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | gbk |
| character_set_server | utf8 |
| character_set_system | utf8 |
+————————–+————-+

 

 

mysql创立存款和储蓄进度退步1307荒唐化解