Bug #84889 MYSQL 8.0.1 - MYSQLD ERRORLOG UPGRADE ERRORS AT SERVER START LIVE UPGRADE
Submitted: 8 Feb 2017 14:55 Modified: 27 Mar 2017 15:07
Reporter: Susan Koerner Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:8.0.1 OS:Any
Assigned to: CPU Architecture:Any

[8 Feb 2017 14:55] Susan Koerner
Description:
During a live upgrade, error messages are written to the mysqld errorlog that are related to generating the new data dictionary when starting an 5.7.18 datadir on 8.0.1 binaries.

2017-02-08T14:15:12.749585Z 1 [Note] Created Data Dictionary for upgrade
2017-02-08T14:15:13.624743Z 3 [ERROR] ./bin/mysqld: Unknown system variable 'show_compatibility_56'
2017-02-08T14:15:13.624889Z 3 [Warning] Parsing 'sys.diagnostics' routine body failed. Creating routine without parsing routine body
2017-02-08T14:15:13.817630Z 3 [ERROR] ./bin/mysqld: Unknown table 'INNODB_LOCK_WAITS' in information_schema
2017-02-08T14:15:13.817662Z 3 [Warning] Resolving dependency for the view 'sys.innodb_lock_waits' failed. View is no more valid to use
2017-02-08T14:15:13.917594Z 3 [ERROR] ./bin/mysqld: Table 'information_schema.COLUMNS' doesn't exist
2017-02-08T14:15:13.917638Z 3 [Warning] Resolving dependency for the view 'sys.schema_auto_increment_columns' failed. View is no more valid to use
2017-02-08T14:15:13.923335Z 3 [ERROR] ./bin/mysqld: Table 'information_schema.ROUTINES' doesn't exist
2017-02-08T14:15:13.923371Z 3 [Warning] Resolving dependency for the view 'sys.schema_object_overview' failed. View is no more valid to use
2017-02-08T14:15:13.925447Z 3 [ERROR] ./bin/mysqld: Table 'information_schema.STATISTICS' doesn't exist
2017-02-08T14:15:13.925475Z 3 [ERROR] ./bin/mysqld: View 'sys.x$schema_flattened_keys' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
2017-02-08T14:15:13.925501Z 3 [Warning] Resolving dependency for the view 'sys.schema_redundant_indexes' failed. View is no more valid to use
2017-02-08T14:15:14.130853Z 3 [ERROR] ./bin/mysqld: Unknown table 'INNODB_LOCK_WAITS' in information_schema
2017-02-08T14:15:14.130881Z 3 [Warning] Resolving dependency for the view 'sys.x$innodb_lock_waits' failed. View is no more valid to use
2017-02-08T14:15:14.267946Z 3 [ERROR] ./bin/mysqld: Table 'information_schema.STATISTICS' doesn't exist
2017-02-08T14:15:14.267984Z 3 [Warning] Resolving dependency for the view 'sys.x$schema_flattened_keys' failed. View is no more valid to use
2017-02-08T14:15:15.385681Z 3 [Warning] InnoDB: Unable to delete statistics for table mysql.#sql2-4b46-3: Lock wait timeout. They can be deleted later using DELETE FROM mysql.innodb_index_stats WHERE database_name = 'mysql' AND table_name = '#sql2-4b46-3'; DELETE FROM mysql.innodb_table_stats WHERE database_name = 'mysql' AND table_name = '#sql2-4b46-3';
2017-02-08T14:15:16.408896Z 3 [Warning] InnoDB: Unable to delete statistics for table mysql.#sql2-4b46-3: Lock wait timeout. They can be deleted later using DELETE FROM mysql.innodb_index_stats WHERE database_name = 'mysql' AND table_name = '#sql2-4b46-3'; DELETE FROM mysql.innodb_table_stats WHERE database_name = 'mysql' AND table_name = '#sql2-4b46-3';
2017-02-08T14:15:16.423219Z 3 [Note] Finished populating Data Dictionary tables with data.

Builds used:

$ cat mysql-advanced-5.7.18-linux-x86_64/docs/INFO_SRC
commit: 368e4c17af201237e32f18f707c9a6eec04df0ab
date: 2017-02-03 16:50:30 +0100
build-date: 2017-02-03 18:00:34 +0100
short: 368e4c1
branch: mysql-5.7

MySQL source 5.7.18

$ cat mysql-commercial-8.0.1-dmr-linux-x86_64/docs/INFO_SRC
commit: ec765638969ccecf292c2d3354614423cec53edf
date: 2017-02-04 11:02:00 +0800
build-date: 2017-02-04 17:01:41 +0100
short: ec76563
branch: mysql-trunk

MySQL source 8.0.1

How to repeat:
- initialize/start mysql server at 5.7.18
- shutdown
- start mysql server at 8.0.1
[27 Mar 2017 15:07] Paul DuBois
Posted by developer:
 
Noted in 8.0.2 changelog.

For upgrades from MySQL 5.7 to MySQL 8.0,
the server wrote unnecessary parsing warnings to the error log. These
messages are now suppressed.