| Bug #43829 | mysql_upgrade and log tables | ||
|---|---|---|---|
| Submitted: | 24 Mar 2009 11:30 | Modified: | 5 Oct 2010 8:36 |
| Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
| Version: | 6.0.10, 5.1 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | qc | ||
[24 Mar 2009 12:01]
Peter Laursen
A clarification: Basically I think that if this is expected behaviour, then the word *ERROR* should not occur in the console output!
[24 Mar 2009 13:14]
MySQL Verification Team
Thank you for the bug report.
[10 Jul 2009 8:12]
Sveta Smirnova
See also bug #30487
[5 Oct 2010 8:36]
Susanne Ebrecht
This is a duplicate of bug #30487
Description: MySQL upgrade table ckecks returns with log tables ("Error: You can't use locks with log tables.") How to repeat: C:\Program Files\MySQL\MySQL Server 6.0\bin>mysql_upgrade --port=3308 -uroot -p Enter password: Looking for 'mysql.exe' as: C:\Program Files\MySQL\MySQL Server 6.0\bin\mysql.ex e Looking for 'mysqlcheck.exe' as: C:\Program Files\MySQL\MySQL Server 6.0\bin\mys qlcheck.exe Running 'mysqlcheck'... Running 'mysqlcheck'... mysql.backup_history Error : You can't use locks with log tables. status : OK mysql.backup_progress Error : You can't use locks with log tables. status : OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.general_log Error : You can't use locks with log tables. status : OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK mysql.host OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.servers OK mysql.slow_log Error : You can't use locks with log tables. status : OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK ... ... Running 'mysql_fix_privilege_tables'... OK Suggested fix: Not sure. Maybe it is a cosmetical detail only. Actually I do not know if the table checks were skipped or if only LOCKS were (checks performed on unlocked tables) btw: why two instances of 'mysqlcheck' ?