List:General Discussion« Previous MessageNext Message »
From:Bob Eby Date:August 18 2014 1:44pm
Subject:Re: mysql Digest 15 Aug 2014 12:32:06 -0000 Issue 5209
View as plain text  
Wouldn't you run mysql_upgrade *before* upgrading?  (ie: copy new stuff
onto old DB, *then* mysql_upgrade *then* start running new software?)

So I went to google, and realised that I’d probably upgraded without
> running mysql_upgrade.  So I try..
>
> [~] john@server% (872) mysql_upgrade -u root -p mysql
>
>
>
More details I'm sure, but just my initial thought.

Thanks,
Bob


On Fri, Aug 15, 2014 at 8:32 AM, <mysql-digest-help@stripped> wrote:

>
> mysql Digest 15 Aug 2014 12:32:06 -0000 Issue 5209
>
> Topics (messages 230517 through 230517)
>
> Incorrect Infomation in tables_priv.frm
>         230517 by: John McIntyre
>
> Administrivia:
>
> To unsubscribe from the digest, e-mail:
>         <mysql-digest-unsubscribe@stripped>
> or click:
>         http://lists.mysql.com/mysql-digest?unsub=1
>
> To post to the list, e-mail:
>         <mysql@stripped>
>
>
> ----------------------------------------------------------------------
>
>
>
> ---------- Forwarded message ----------
> From: John McIntyre <joh98.mac@stripped>
> To: mysql@stripped
> Cc:
> Date: Fri, 15 Aug 2014 13:31:29 +0100
> Subject: Incorrect Infomation in tables_priv.frm
> Hi,
> I have MySQL 5.1.73 running on a CentOS 6.5 Linux system.     Recently, I
> was adding a couple of users, and when I tried to FLUSH PRIVILEGES, I got
> this …
>
> (root@stripped [(none)] 13:24:19 (1) $ FLUSH PRIVILEGES ;
> ERROR 1033 (HY000): Incorrect information in file:
> './mysql/tables_priv.frm’
>
> So I went to google, and realised that I’d probably upgraded without
> running mysql_upgrade.  So I try..
>
> [~] john@server% (872) mysql_upgrade -u root -p mysql
> Enter password:
> Looking for 'mysql' as: mysql
> Looking for 'mysqlcheck' as: mysqlcheck
> Running 'mysqlcheck with default connection arguments
> Running 'mysqlcheck with default connection arguments
> 0wn3lou4.oc_appconfig                              OK
> 0wn3lou4.oc_clndr_calendars                        OK
>
> That for a lot of lines, and then …
>
> mysql.help_relation                                OK
> mysql.help_topic                                   OK
> mysql.host                                         OK
> mysql.innodb_index_stats
> Error    : Incorrect information in file: './mysql/innodb_index_stats.frm'
> error    : Corrupt
> mysql.innodb_table_stats
> Error    : Incorrect information in file: './mysql/innodb_table_stats.frm'
> error    : Corrupt
> mysql.ndb_binlog_index                             OK
> mysql.plugin                                       OK
> mysql.proc
> Error    : Incorrect information in file: './mysql/proc.frm'
> error    : Corrupt
> mysql.procs_priv
> Error    : Incorrect information in file: './mysql/procs_priv.frm'
> error    : Corrupt
> mysql.proxies_priv
> Error    : Incorrect information in file: './mysql/proxies_priv.frm'
> error    : Corrupt
>
> .. for loads of lines, and then …
>
> ERROR 1033 (HY000) at line 659: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 661: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 663: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 666: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 669: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 672: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 675: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 678: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 681: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 684: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 686: Incorrect information in file:
> './mysql/event.frm'
> ERROR 1033 (HY000) at line 714: Incorrect information in file:
> './mysql/tables_priv.frm'
> FATAL ERROR: Upgrade failed
>
> There are four databases on that server, two of them critical, production
> databases.  I can get around the privileges problem by stopping and
> starting the database out of office hours, but even then, when I do …
>
> 140815 13:28:29 mysqld_safe Starting mysqld daemon with databases from
> /var/lib/mysql
> 140815 13:28:29  InnoDB: Initializing buffer pool, size = 8.0M
> 140815 13:28:29  InnoDB: Completed initialization of buffer pool
> 140815 13:28:29  InnoDB: Started; log sequence number 4 2002382636
> 140815 13:28:29 [ERROR] /usr/libexec/mysqld: Incorrect information in
> file: './mysql/tables_priv.frm'
> 140815 13:28:29 [ERROR] /usr/libexec/mysqld: Incorrect information in
> file: './mysql/event.frm'
> 140815 13:28:29 [ERROR] Cannot open mysql.event
> 140815 13:28:29 [ERROR] Event Scheduler: An error occurred when
> initializing system tables. Disabling the Event Scheduler.
> 140815 13:28:29 [Note] /usr/libexec/mysqld: ready for connections.
>
> The user changes are taken into account, however.
>
> Needless to say, mysql_dump doesn’t work either.
>
> Any advice gratefully received.
>
> John.
>
>
>
>

Thread
Re: mysql Digest 15 Aug 2014 12:32:06 -0000 Issue 5209Bob Eby18 Aug 2014