Mysql-5.6.30卸载
一、删除相关文件
rm -rf /var/lib/mysql/mysql (删除数据文件)
rm -f /root/.mysql_secure (删除缺省root密码文件，以便rpm包安装时重新生成
二、卸载MySQL-server-5.6.30-1.el6.x86_64包
rpm -e MySQL-server-5.6.30-1.el6.x86_64
三、重新安装MySQL-server-5.6.30-1.el6.x86_64包
rpm -ivh MySQL-server-5.6.30-1.el6.x86_64.rpm
warning: MySQL-server-5.6.30-1.el6.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
2016-09-04 11:53:12 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-09-04 11:53:12 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 30354 ...
2016-09-04 11:53:12 30354 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-09-04 11:53:12 30354 [Note] InnoDB: The InnoDB memory heap is disabled
2016-09-04 11:53:12 30354 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-09-04 11:53:12 30354 [Note] InnoDB: Memory barrier is not used
2016-09-04 11:53:12 30354 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-09-04 11:53:12 30354 [Note] InnoDB: Using Linux native AIO
2016-09-04 11:53:12 30354 [Note] InnoDB: Using CPU crc32 instructions
2016-09-04 11:53:12 30354 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-09-04 11:53:12 30354 [Note] InnoDB: Completed initialization of buffer pool
2016-09-04 11:53:12 30354 [Note] InnoDB: Highest supported file format is Barracuda.
2016-09-04 11:53:12 30354 [Note] InnoDB: Log scan progressed past the checkpoint lsn 18718277304
2016-09-04 11:53:12 30354 [Note] InnoDB: Database was not shutdown normally!
2016-09-04 11:53:12 30354 [Note] InnoDB: Starting crash recovery.
2016-09-04 11:53:12 30354 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-09-04 11:53:12 30354 [Note] InnoDB: Restoring possible half-written data pages
2016-09-04 11:53:12 30354 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 18718279764
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_admins in the InnoDB data dictionary has tablespace id 6, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_channel_count in the InnoDB data dictionary has tablespace id 15, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_channel_info in the InnoDB data dictionary has tablespace id 14, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_invoke_config in the InnoDB data dictionary has tablespace id 11, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_node_info in the InnoDB data dictionary has tablespace id 13, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/m_node_link in the InnoDB data dictionary has tablespace id 8, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table monitor/sequence in the InnoDB data dictionary has tablespace id 9, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table mysql/innodb_index_stats in the InnoDB data dictionary has tablespace id 2, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table mysql/innodb_table_stats in the InnoDB data dictionary has tablespace id 1, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table mysql/slave_master_info in the InnoDB data dictionary has tablespace id 4, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table mysql/slave_relay_log_info in the InnoDB data dictionary has tablespace id 3, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Table mysql/slave_worker_info in the InnoDB data dictionary has tablespace id 5, but tablespace with that id or name does not exist. Have you deleted or moved .ibd files? This may also be a table created with CREATE TEMPORARY TABLE whose .ibd and .frm files MySQL automatically removed, but the table still exists in the InnoDB internal data dictionary.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2016-09-04 11:53:12 30354 [Note] InnoDB: 128 rollback segment(s) are active.
2016-09-04 11:53:12 30354 [Note] InnoDB: Waiting for purge to start
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."innodb_index_stats"' in the cache. Attempting to load the tablespace with space id 2.
2016-09-04 11:53:12 7fba7ebfd700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/innodb_index_stats'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Failed to find tablespace for table '"mysql"."innodb_table_stats"' in the cache. Attempting to load the tablespace with space id 1.
2016-09-04 11:53:12 7fba7ebfd700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2016-09-04 11:53:12 30354 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql/innodb_table_stats'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2016-09-04 11:53:12 30354 [Note] InnoDB: 5.6.30 started; log sequence number 18718279764
ERROR: 1050 Table '`mysql`.`innodb_table_stats`' already exists
2016-09-04 11:53:12 30354 [ERROR] Aborting
2016-09-04 11:53:12 30354 [Note] Binlog end
2016-09-04 11:53:12 30354 [Note] InnoDB: FTS optimize thread exiting.
2016-09-04 11:53:12 30354 [Note] InnoDB: Starting shutdown...
2016-09-04 11:53:14 30354 [Note] InnoDB: Shutdown completed; log sequence number 18718317797
2016-09-04 11:53:14 30354 [Note] /usr/sbin/mysqld: Shutdown complete
warning: MySQL-server-5.6.30-1.el6.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
2016-09-04 12:03:29 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-09-04 12:03:29 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 30790 ...
2016-09-04 12:03:29 30790 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-09-04 12:03:29 30790 [Note] InnoDB: The InnoDB memory heap is disabled
2016-09-04 12:03:29 30790 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-09-04 12:03:29 30790 [Note] InnoDB: Memory barrier is not used
2016-09-04 12:03:29 30790 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-09-04 12:03:29 30790 [Note] InnoDB: Using Linux native AIO
2016-09-04 12:03:29 30790 [Note] InnoDB: Using CPU crc32 instructions
2016-09-04 12:03:29 30790 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-09-04 12:03:29 30790 [Note] InnoDB: Completed initialization of buffer pool
2016-09-04 12:03:29 30790 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-09-04 12:03:29 30790 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-09-04 12:03:29 30790 [Note] InnoDB: Database physically writes the file full: wait...
2016-09-04 12:03:29 30790 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-09-04 12:03:29 30790 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2016-09-04 12:03:30 30790 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-09-04 12:03:30 30790 [Warning] InnoDB: New log files created, LSN=45781
2016-09-04 12:03:30 30790 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-09-04 12:03:30 30790 [Note] InnoDB: Doublewrite buffer created
2016-09-04 12:03:30 30790 [Note] InnoDB: 128 rollback segment(s) are active.
2016-09-04 12:03:30 30790 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-09-04 12:03:30 30790 [Note] InnoDB: Foreign key constraint system tables created
2016-09-04 12:03:30 30790 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-09-04 12:03:30 30790 [Note] InnoDB: Tablespace and datafile system tables created.
2016-09-04 12:03:30 30790 [Note] InnoDB: Waiting for purge to start
2016-09-04 12:03:30 30790 [Note] InnoDB: 5.6.30 started; log sequence number 0
A random root password has been set. You will find it in '/root/.mysql_secret'.
2016-09-04 12:03:30 30790 [Note] Binlog end
2016-09-04 12:03:30 30790 [Note] InnoDB: FTS optimize thread exiting.
2016-09-04 12:03:30 30790 [Note] InnoDB: Starting shutdown...
2016-09-04 12:03:31 30790 [Note] InnoDB: Shutdown completed; log sequence number 1625977
2016-09-04 12:03:31 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-09-04 12:03:31 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30) starting as process 30812 ...
2016-09-04 12:03:31 30812 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-09-04 12:03:31 30812 [Note] InnoDB: The InnoDB memory heap is disabled
2016-09-04 12:03:31 30812 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-09-04 12:03:31 30812 [Note] InnoDB: Memory barrier is not used
2016-09-04 12:03:31 30812 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-09-04 12:03:31 30812 [Note] InnoDB: Using Linux native AIO
2016-09-04 12:03:31 30812 [Note] InnoDB: Using CPU crc32 instructions
2016-09-04 12:03:31 30812 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-09-04 12:03:32 30812 [Note] InnoDB: Completed initialization of buffer pool
2016-09-04 12:03:32 30812 [Note] InnoDB: Highest supported file format is Barracuda.
2016-09-04 12:03:32 30812 [Note] InnoDB: 128 rollback segment(s) are active.
2016-09-04 12:03:32 30812 [Note] InnoDB: Waiting for purge to start
2016-09-04 12:03:32 30812 [Note] InnoDB: 5.6.30 started; log sequence number 1625977
2016-09-04 12:03:32 30812 [Note] Binlog end
2016-09-04 12:03:32 30812 [Note] InnoDB: FTS optimize thread exiting.
2016-09-04 12:03:32 30812 [Note] InnoDB: Starting shutdown...
2016-09-04 12:03:33 30812 [Note] InnoDB: Shutdown completed; log sequence number 1625987
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER !
You will find that password in '/root/.mysql_secret'.
You must change that password on your first connect,
no other statement but 'SET PASSWORD' will be accepted.
See the manual for the semantics of the 'password expired' flag.
Also, the account for the anonymous user has been removed.
In addition, you can run:
/usr/bin/mysql_secure_installation
which will also give you the option of removing the test database.
This is strongly recommended for production servers.
See the manual for more instructions.
Please report any problems at http://bugs.mysql.com/
The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com
WARNING: Found existing config file /usr/my.cnf on the system.
Because this file might be in use, it was not replaced,
but was used in bootstrap (unless you used --defaults-file)
and when you later start the server.
The new default config file was created as /usr/my-new.cnf,
please compare it with your file and take the changes you need.
四、配置datadir路径
vi /usr/my.cnf
datadir=/data
启动
mysqld_safe &
service mysql start
五、修复数据
[Err] 1034 - Incorrect key file for table 'm_request_record'; try to repair it
mysql> repair table m_request_record;
退出mysql,执行如下修复动作：
myisamchk –of /data/monitor/m_request_record.MYI
myisamchk –r /data/monitor/m_request_record.MYI
myisamchk safe-reocver /data/monitor/m_request_record.MYI