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@root.server [(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_calendarsOK That for a lot of lines, and then … mysql.help_relationOK 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.
回复: Incorrect Infomation in tables_priv.frm
DEAR john You can try rename tables_priv.frm.then restart mysql instance. If the mysql instance can restart sucessfully,you can export the production database by using mysqldump. 2014-08-15 I AM AN ORACLE FANS! Skype:Frank.oracle Email:xiangdong...@gmail.com 发件人：John McIntyre joh98@gmail.com 发送时间：2014-08-15 20:31 主题：Incorrect Infomation in tables_priv.frm 收件人：mysqlmysql@lists.mysql.com 抄送： 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@root.server [(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_calendarsOK That for a lot of lines, and then … mysql.help_relationOK 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.
MySQL Cluster Manager 1.3.2 has been released
Dear MySQL users, MySQL Cluster Manager 1.3.2, has been released and can be downloaded from the My Oracle Support (MOS) website. It will also be available on Oracle Software Delivery Cloud at http://edelivery.oracle.com with the September update in a few weeks. MySQL Cluster Manager is an optional component of MySQL Cluster Carrier Grade Edition - providing a command-line-interface that automates common management tasks. These include these on-line operations: - Configuring and starting MySQL Cluster - Upgrades - Addition of new nodes - Configuration changes - Backup and restore MySQL Cluster Manager is a commercial extension. More details can be found at http://www.mysql.com/products/cluster/mcm/ A brief summary of changes in MySQL Cluster Manager version 1.3.2 is listed below: Functionality Added or Changed (2014-08-15) * Agent; Client: In order to improve execution robustness, MySQL Cluster Manager now fails any commands that reconfigure a cluster with a message (i.e. ERROR 5027 Unable to perform command due to utility proc_name with pid ospid on host) if any utility process (for example, mysql_upgrade, mysql_install_db, or ndb_restore) that was started by a previous command is still remaining (running or hung) on any host when the command is issued. (Bug #18966650) * Client: MySQL Cluster Manager now throws an error if the user tries to import a cluster or a cluster configuration using the import cluster (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-cluster.html) or import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command while the user who runs the mcmd process does not have permissions to the cluster processes' PID files. This happens typically when mcmd is started with the user mysql while the cluster is started with root. (Bug #18887139) Bugs Fixed * Agent; Client: On Windows platforms, when a data node could not be restarted during a rolling restart of the cluster, it was not reported to the user. With this fix, the user now gets a report when a maintenance restart of a data node failed. (Bug #19227535) * Agent; Client: The import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command did not import configuration settings from a cluster's my.cnf file properly; problems included: + Some settings in the [mysqld] section were left out (for example, key_buffer_size and query_cache_type). + Some options in the [client] section were included by mistake. + The !include and !includedir statements for including settings from other files were ignored + Quoted values were not handled properly---the quotes were taken literally. + Lines starting with ; were not treated as comments. + The option modifiers loose_ and maximum_ were not recognized. + Option group for specific release series (for example, [mysqld-5.6]) were not imported. (Bug #19078129) * Agent; Client: When the configuration of a running cluster was being imported using the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command, even if the parameter ThreadConfig was not defined in the config.ini file, its value could be imported from the running node's setting for it. The imported value overrode the configuration prescribed by the MaxNoOfExecutionThreads parameter in config.ini, which is supposed to set the thread configuration when ThreadConfig is not specified in config.ini. This fix prevents the import of the value for ThreadConfig from the running node, making MySQL Cluster Manager rely on the config.ini file for the thread configuration. (Bug #19032714) * Agent; Client: The import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command sometimes imported MySQL server default values that were not specified in the cluster's configuration files. With this fix, no such values are imported. (Bug #18651301) * Agent; Client: When using the import config (http://dev.mysql.com/doc/mysql-cluster-manager/1.3/en/mcm-import-config.html) command, the format of an imported configuration setting was sometimes changed from that which was used in the config.ini file---for example, a value in megabytes was imported as a value in bytes and then shown as such by the get command. That made it more difficult for the user to compare the original and the imported value. This fix makes MySQL Cluster Manager follow the original format in the config.ini file when importing a cluster's configuration. (Bug #18651726) * Agent: The MySQL Cluster Manager agent might crash when running an import config
