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

Mysql-5.6.30卸载的更多相关文章

  1. MySQL 5.7.30 的安装/升级（所有可能的坑都在这里）

    楔子 由于之前电脑上安装的MySQL版本是比较老的了,大概是5.1的版本,不支持JSON字段功能.而最新开发部门开发的的编辑器产品,使用到了JSON字段的功能. 因此需要升级MySQL版本,升级的目标 ...

  2. CentOS 配置Apache+Mysql+PHP (yum)与卸载

    一.安装Apache2 #yum -y install httpd 安装配置完成,启动httpd服务#service httpd start 二.安装Mysql1.安装mysql#yum -y ins ...

  3. MySql的安装与卸载

    首先到官网下载MySQL,点击安装 出现的页面如下,依次安装就好了,安装过程中需要修改的只有编码格式,需要填写的是数据库的密码,MySQL的默认用户名为root,默认端口为3306,端口号最好不要修改 ...

  4. MySQL系列--1.安装卸载与用户权限管理

    MySQL安装 1.Ubuntu18下安装MySQL sudo apt-get install mysql-server MySQL的版本为5.7.25 2.登录MySQL 采用mysql-serve ...

  5. MySQL 5.6.30 升级到5.7.10

    MySQL 5.6.30 升级到5.7.10 注意,这种方式的前提是数据文件没有和软件目录在一起,如果在一起,需要停止数据库后先移动数据文件 1.解压5.7.10包到/usr/local2.停止当前的 ...

  6. 数据库MySQL的安装与卸载

    安装 MySQL  卸载 MySQL: 停止 MySQL 服务 开始-->所有应用-->Windows 管理工具-->服务,将 MySQL 服务停止. 卸载 mysql server ...

  7. mysql数据库安装与卸载以及Navicat安装

    关系型数据库Mysql 1.mysql官网网址:www.mysql.org 2.mysql数据库安装 傻瓜式安装下载地址 https://dev.mysql.com/downloads/install ...

  8. linux(Debian)下安装与MySql的安装、卸载、配置及使用

    参考资料:http://www.cnblogs.com/xusir/p/3334217.html 以下是简要记录. 一.安装 安装:apt-get install mysql-server mysql ...

  9. MySQL 性能优化 30个数据库设计的最佳实践

    数据库设计是整个程序的重点之一,为了支持相关程序运行,最佳的数据库设计往往不可能一蹴而就,只能反复探寻并逐步求精,这是一个复杂的过程,也是规划和结构化数据库中的数据对象以及这些数据对象之间关系的过程. ...

随机推荐

  1. Toll-Free Bridge

    引 在深入了解桥接机制的时候看到一篇好文,虽然已经很久远,但是忍不住看了好几遍,心中诸多不解一扫而光.在此放上链接: 原文:http://ridiculousfish.com/blog/posts/b ...

  2. [ZT] 几大酒店集团美国Co-Brand信用卡比较（三）如何选择最适合你的酒店联名信用卡

    原文地址: http://www.3798.com/archives/596.html 接着对我们这种不是某个酒店忠诚客户的用户选择卡片进行分析.首先要强调的是,我们比较的是信用卡项目本身,而不是酒店 ...

  3. maven 将依赖的jar包打入jar包中

    pom中加入以下代码,利用mvn assembly:assembly就可以了. <build> <plugins> <plugin> <artifactId& ...

  4. excel表中内容如何反排列

    如题,我的意思是,比如excel表中有如下内容: 1.红色 2.黄色 3.蓝色 现在我需要一次性全部反向排列,变成 3.蓝色 2.黄色 1.红色 这不是纯数字排序,因为我序号不是自然数的等差数列,其中 ...

  5. top指令

    top - :: up :, user, load average: 0.00, 0.01, 0.05 Tasks: total, running, sleeping, stopped, zombie ...

  6. Scrum会议5

    组名称:天天向上 项目名称:连连看 参会成员:王森(Master)张金生 张政 栾骄阳 时间:2016.10.20 已完成内容: 1.游戏中实现了两个按钮消除的算法. 2.在游戏中加入了音乐. 计划完 ...

  7. POJ 2777 Count Color（线段树染色，二进制优化）

    Count Color Time Limit: 1000MS   Memory Limit: 65536K Total Submissions: 42940   Accepted: 13011 Des ...

  8. java.lang.NoClassDefFoundError: org/apache/commons/lang/exception/NestableRuntim [问题点数：40分，结帖人wangxiaohua_001]

    14:56:10.093 WARN!! Error for /butterfly/plugins/zhonghang/UsefulData/save_usefuldata.bshjava.lang.N ...

  9. virtual box ubuntu卡在开机光标

    创建虚拟机的时候选择之前保存的虚拟机盘vdi文件,打开的时候卡在光标.原来是因为虚拟机是64位的,但是新建的时候只有32位的ubuntu可以选择就选择的32位. 解决办法: 在bios设置里,打开cp ...

  10. GWP PHP auth page works

    经过修改,看起来GWP能工作了.不过还是需要深入了解ca的page flow,PHP and Perl大不同 1015  ls /var/www/html/gwp/lib/database.php 1 ...