Bug #47710 | mysql-5.1.39-linux-i686-glibc23 upgrade failed | ||
---|---|---|---|
Submitted: | 29 Sep 2009 11:46 | Modified: | 30 Sep 2009 9:45 |
Reporter: | Ugur Dincer | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 5.1.39 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[29 Sep 2009 11:46]
Ugur Dincer
[29 Sep 2009 13:27]
MySQL Verification Team
Thank you for the bug report. Looks like it is duplicate of bug: http://bugs.mysql.com/bug.php?id=42028.
[29 Sep 2009 14:21]
Ugur Dincer
I run my current mysql instance on the default port (3306). Looking for 'mysql' as: /tmp/mysql-5.1.39-linux-i686-glibc23/bin/mysql Looking for 'mysqlcheck' as: /tmp/mysql-5.1.39-linux-i686-glibc23/bin/mysqlcheck Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock'
[29 Sep 2009 15:04]
Susanne Ebrecht
This is a duplicate of bug #42028
[29 Sep 2009 15:13]
Ugur Dincer
Any plans to resolve this and the duplicate(s) in the next release?
[30 Sep 2009 9:45]
Ugur Dincer
I'm not an experienced MySQL user so I would like to add some stupid questions Since mysql_upgrade fails, how should I progress the upgrade process According to the upgrade instructions: mysql_upgrade executes the following commands to check and repair tables and to upgrade the system tables: mysqlcheck --all-databases --check-upgrade --auto-repair mysql < fix_priv_tables mysqlcheck --all-databases --check-upgrade --fix-db-names --fix-table-names What is the name of the fix_priv_tables script generated interally? Or is it enough to just run >> mysqlcheck --all-databases --check-upgrade --auto-repair