A. 如何徹底卸載centos mysql
yum list |grep -i mysql 然後把mysql的包刪除，比如： yum remove mysql yum remove mysql-server
B. centos7怎樣卸載mysql
這個你可以到手機設置，程序管理中卸載。
或者使用騰訊手機管家的軟體管理功能進行卸載。
打開騰訊手機管家，點軟體管理再點軟體卸載，這時候就會出來你手機里所有軟體的列表，找到這個卸載。
C. centOS 卸載之前的php-mysql-apache centOS怎麼卸載mysql
centOS完全刪除mysql方法:
1 rpm -qa|grep mysql
查看安裝了哪些mysql和lib……
1 yum remove mysql mysql-server mysql-libs compat-mysql51
刪除上面查到的mysql和lib信息
2 rm -rf /var/lib/mysql
刪除mysql默認的安裝目錄
3 rm /etc/my.cnf
刪除mysql的配置文件
4 rpm -qa|grep mysql
再查看還有什麼依賴包沒刪除，如果還有沒刪除的話，回到第二步繼續刪……
到此為止已經將mysql完全刪除，可以繼續安裝新的mysql
D. 如何卸載centos的mysq
查看已經安裝的服務
rpm –qa|grep -i mysql
可以看到有兩個安裝包
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm
刪除這兩個服務(去掉後綴)
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64
查看殘留的目錄：
whereis mysql
然後刪除mysql目錄：
rm –rf /usr/lib64/mysql
刪除相關文件：
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret
最關鍵的：
rm -rf /var/lib/mysql
如果這個目錄如果不刪除，再重新安裝之後，密碼還是之前的密碼，不會重新初始化！
E. centos 怎麼卸載mysql
源碼編譯的，直接把安裝目錄刪掉就行，一般都安裝在/usr/local/mysql/里。rpm -qa只能看見rpm的安裝包，兩碼事。
查看已經安裝的服務
rpm –qa|grep -i mysql
-i 作用是不區分大小寫
yum remove mysql mysql-server mysql-libs compat-mysql51
rm -rf /var/lib/mysql
rm /etc/my.cnf
查看是否還有mysql軟體：
rpm -qa|grep mysql
有的話繼續刪除
可以看到有兩個安裝包
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm
刪除這兩個服務(去掉後綴)
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64
查看殘留的目錄：
whereis mysql
然後刪除mysql目錄：
rm –rf /usr/lib64/mysql
刪除相關文件：
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret
最關鍵的：
rm -rf /var/lib/mysql
如果這個目錄如果不刪除，再重新安裝之後，密碼還是之前的密碼，不會重新初始化！
網上查了很久都沒有文章提到這個，最後還是自己摸索找出來的。
卸載完成！怎麼確定是不是真的卸載干凈了呢？
一是看安裝輸出：
如果沒有卸載干凈，安裝server時輸入只有兩行：
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
卸載干凈了安裝輸入如下：
[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Preparing... ########################################### [100%]
1:MySQL-server ########################################### [100%]
2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait...
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created
2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created
2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables.
2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created.
2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0
A random root password has been set. You will find it in '/root/.mysql_secret'.
2014-09-23 07:22:46 26041 [Note] Binlog end
2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown...
2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977
2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled
2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO
2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions
2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool
2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda.
2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active.
2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start
2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977
2014-09-23 07:22:48 26065 [Note] Binlog end
2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting.
2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown...
2014-09-23 07:22:50 26065 [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 proction 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
New default config file was created as /usr/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
最後一段中提示了重要信息，很多人因為不喜歡讀英文，導致接下來不知道怎麼操作！
二就是安裝完成，啟動服務之後
使用命令：「mysql -uroot -p」輸入你之前安裝後設置的密碼，看能不能登錄，如果還可以登錄，說明沒有卸載干凈！
G. centos怎麼卸載mysql
試試騰訊電腦管家干凈快速
電腦管家將檢測當前電腦上已安裝的全部軟體，您可以選擇卸載不想要繼續使用的軟體，卸載不常用的軟體有助於提升系統性能，增加磁碟可用空間。
在軟體卸載面板中，選擇不想要繼續使用的軟體，然後點擊[卸載]按鈕，可以完成卸載操作。
打開騰訊電腦管家——軟體管理——卸載
H. CentOS下如何完全卸載MySQL
這里主要解決使用rpm安裝的卸載問題，安裝方法見：CentOS安裝mysql*.rpm提示conflicts with file from package的解決辦法
雖然說這里的是使用rpm安裝的卸載問題，我覺得使用yum方式安裝的如果遇到相同?問題也一樣適用。
查看已經安裝的服務
rpm –qa|grep -i mysql
-i 作用是不區分大小寫
可以看到有兩個安裝包
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm
刪除這兩個服務(去掉後綴)
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64
查看殘留的目錄：
Whereis mysql
然後刪除mysql目錄：
rm –rf /usr/lib64/mysql
刪除相關文件：
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret
最關鍵的：
rm -rf /var/lib/mysql
如果這個目錄如果不刪除，再重新安裝之後，密碼還是之前的密碼，不會重新初始化！
網上查了很久都沒有文章提到這個，最後還是自己摸索找出來的。
卸載完成！
如果有幫助求採納
I. 如何卸載centos的mysql
手機有一部份軟體是支持卸載的，如果卸載不了的一定要卸載的話你可以使用騰訊手機管家，打開騰訊手機管家，點更多，裡面有一個預裝卸載，選擇開啟，再按步驟操作
自帶的可以獲取ROOT許可權以後卸載
J. centos怎麼刪除mysql
查看是否還有mysql軟體：
rpm -qa|grep mysql
如果存在的話，繼續刪除即可。