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. iOS下json的解析 NSJSONSerialization

      - (IBAction)JOSNButtonPressed:(id)sender { NSString *str=[@"http://douban.fm/j/mine/playlist? ...

  2. hdu-acm steps Monkey and Banana

    这道题是典型的dp题.首先是数据的处理上,因为每个长方体的3条不同长度的棱都可以作为高,因此一个长方体可以看成3个不同的长方体.从而将数据扩展为3*n,然后将所有的长方体以长度为第一排序条件,宽度为第 ...

  3. JavaScript - 时间函数

    时间美化函数 /* 1.< 60s, 显示为“刚刚” 2.>= 1min && < 60 min, 显示与当前时间差“XX分钟前” 3.>= 60min &am ...

  4. 开源top100

    1.SwitchyOmega 项目简介:SwitchyOmega 是 SwitchySharp 的新版本.这是一个 Chrome 浏览器用来切换不同代理的插件.SwitchyOmega 初次安装时会检 ...

  5. The P4 Language Specification v1.0.2 Parser

    <p4规范>解析器部分详解 p4解析器是根据有限状态机的思想来设计的. 解析器中解析的过程可以被一个解析图(parser graph)所表示,解析图中所表示的某一个状态(或者说,在P4语言 ...

  6. SSH服务器拒绝了密码 请再试一次

    应该是sshd的设置不允许root用户用密码远程登录. 修改: vim /etc/ssh/sshd_config 找到: # Authentication:LoginGraceTime 120Perm ...

  7. 《Java程序设计》第2周学习总结

    20145317彭垚<Java程序设计>第2周学习总结 教材学习内容总结 类型 基本类型 整数(short.int.long) 字节(byte) 浮点数(float/double) 字符( ...

  8. Scrapy安装介绍

    一. Scrapy简介 Scrapy is a fast high-level screen scraping and web crawling framework, used to crawl we ...

  9. breadth-first depth-first best-first

    Computer Science An Overview _J. Glenn Brookshear _11th Edition For our example in Figure 11.7, we c ...

  10. file_get_contents无法获取数据的一种情况

    下面这段php代码突然不好使了,返回的 $html 为空,百思不得解.网上说法好多,但都是一家之言,解决不了我的问题.(我的解决方法也是一家之言,只能解决file_get_contents获取不到数据 ...