Re-installing common_schema after upgrading to MySQL 5.6_MySQL
Jun 01, 2016 pm 01:13 PMAfter upgrading from MySQL 5.5 to 5.6, I started getting some warnings when running queries incommon_schema. For example:
<code>+---------+------+--------------------------------------------------------------------------------------------------------------------------------------------------+| Level | Code | Message|+---------+------+--------------------------------------------------------------------------------------------------------------------------------------------------+| Warning | 1109 | Unknown table 'innodb_index_stats' in information_schema || Warning | 1109 | Unknown table 'innodb_index_stats' in information_schema || Warning | 1356 | View 'common_schema.processlist_repl' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them || Warning | 1356 | View 'common_schema.processlist_top' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them|| Warning | 1356 | View 'common_schema.slave_hosts' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them|| Warning | 1356 | View 'common_schema.slave_status' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them |+---------+------+--------------------------------------------------------------------------------------------------------------------------------------------------+</code> Copy after login |
The common_schema installer is good at accomodating whichever version of MySQL it is being installed on, but if you change that version it makes sense that common_schema needs to be re-installed. As stated in thedocumentation:
If you should upgrade your MySQL server, or enable features which were turned off during install of common_schema, the new feature set are not automatically available by common_schema, and a re-install of common_schema is required.
A re-install is easy. Here’s what I did:
<code>wget https://common-schema.googlecode.com/files/common_schema-2.2.sqlmysql --init-command="set sql_log_bin = 0;" </code> Copy after login |
Most of the warnings went away, but I’m still getting this:
<code>+---------+------+----------------------------------------------------------+| Level | Code | Message|+---------+------+----------------------------------------------------------+| Warning | 1109 | Unknown table 'innodb_index_stats' in information_schema || Warning | 1109 | Unknown table 'innodb_index_stats' in information_schema |+---------+------+----------------------------------------------------------+</code> Copy after login |
Apparently in MySQL 5.6 theinnodb_index_stats
table has moved frominformation_schema
to themysql
schema, so I submitted abug report. So far this isn’t affecting the way I use common_schema, but if it did the common_schema source code is very readable so it would probably be a simple patch.

Hot Article

Hot tools Tags

Hot Article

Hot Article Tags

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Reduce the use of MySQL memory in Docker

How do you alter a table in MySQL using the ALTER TABLE statement?

How to solve the problem of mysql cannot open shared library

Run MySQl in Linux (with/without podman container with phpmyadmin)

What is SQLite? Comprehensive overview

Running multiple MySQL versions on MacOS: A step-by-step guide

What are some popular MySQL GUI tools (e.g., MySQL Workbench, phpMyAdmin)?

How do I configure SSL/TLS encryption for MySQL connections?
