Uninstall Commercial MySQL Server on Ubuntu

-
Uninstall Commercial MySQL Server on Ubuntu

As part DB server decommission , We need to uninstall DB binary/packages from the DB server post DB backup with long term retention. 

Below are the steps for uninstalling MySQL Server package from ubuntu server:

1) On Ubuntu server , MySQL Server is installed as DEB package.

2) Before Uninstalling MySQL Server package , We need to stop MySQL server.

shell> sudo service mysql stop

3) Remove all the depending package .

4) Remove package from the server.

If you want to preserve configuration files and data, remove the package using dpkg command with -r option.

shell> sudo dpkg -r mysql

If you want to remove everything including configuration files and data, remove the package using -P option.

shell> sudo dpkg -P mysql-server mysql-client mysql-commercial-client mysql-commercial-client-core mysql-commercial-server mysql-commercial-server-core mysql-common




Logs:

root@mysqlhost01:/etc/mysql/mysql.conf.d# dpkg -l |grep -i mysql
ii  mysql-client                          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client meta package depending on latest version
ii  mysql-commercial-client               8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client
ii  mysql-commercial-client-core          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client Core Binaries
ii  mysql-commercial-server               8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Server
ii  mysql-commercial-server-core          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Server Core Binaires
ii  mysql-common                          8.0.17+commercial-1ubuntu18.04                  amd64        Common files shared between packages
ii  mysql-server                          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Server meta package depending on latest version
root@mysqlhost01:/etc/mysql/mysql.conf.d# dpkg -P mysql
dpkg: warning: ignoring request to remove mysql which isn't installed
root@mysqlhost01:/etc/mysql/mysql.conf.d# dpkg -P mysql-server
(Reading database ... 162070 files and directories currently installed.)
Removing mysql-server (8.0.17+commercial-1ubuntu18.04) ...
root@mysqlhost01:/etc/mysql/mysql.conf.d# dpkg -l |grep -i mysql
ii  mysql-client                          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client meta package depending on latest version
ii  mysql-commercial-client               8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client
ii  mysql-commercial-client-core          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Client Core Binaries
ii  mysql-commercial-server               8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Server
ii  mysql-commercial-server-core          8.0.17+commercial-1ubuntu18.04                  amd64        MySQL Server Core Binaires
ii  mysql-common                          8.0.17+commercial-1ubuntu18.04                  amd64        Common files shared between packages
root@mysqlhost01:/etc/mysql/mysql.conf.d# dpkg -P mysql-client mysql-commercial-client mysql-commercial-client-core mysql-commercial-server mysql-commercial-server-core mysql-common
(Reading database ... 162064 files and directories currently installed.)
Removing mysql-commercial-server (8.0.17+commercial-1ubuntu18.04) ...
update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode
Purging configuration files for mysql-commercial-server (8.0.17+commercial-1ubuntu18.04) ...
.
dpkg: warning: while removing mysql-commercial-server, directory '/etc/mysql/mysql.conf.d' not empty so not removed
Removing mysql-commercial-server-core (8.0.17+commercial-1ubuntu18.04) ...
Removing mysql-client (8.0.17+commercial-1ubuntu18.04) ...
Removing mysql-commercial-client (8.0.17+commercial-1ubuntu18.04) ...
Purging configuration files for mysql-commercial-client (8.0.17+commercial-1ubuntu18.04) ...
Removing mysql-commercial-client-core (8.0.17+commercial-1ubuntu18.04) ...
Removing mysql-common (8.0.17+commercial-1ubuntu18.04) ...
Purging configuration files for mysql-common (8.0.17+commercial-1ubuntu18.04) ...
update-alternatives: warning: alternative /etc/mysql/my.cnf.fallback (part of link group my.cnf) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/my.cnf is dangling; it will be updated with best choice
dpkg: warning: while removing mysql-common, directory '/etc/mysql' not empty so not removed
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
root@mysqlhost01:/etc/mysql/mysql.conf.d#

you can learn more about MySql and InnoDB from below books:

========================================================================
You can also , Visit our Blogs for related topic on installation and Uninstallation:

Location: Singapore

Comments

Post a Comment

Please do not enter any spam link in comment Section suggestions are Always Appreciated. Thanks.. !

Popular posts from this blog

Restore MySQL Database from mysqlbackup

-
Image
 Restore MySQL Database from mysqlbackup  In todays world, One of the most common activity is to perform database restore using old backup or performing PIT recovery for database.  In this blog , We will show you how to perform restore and recovery of the MySQL database using backup taken via mysqlbackup. In order to restore Mysql database from MySQL backup , We will follow below steps: 1) Shut down MySQL Database Server/Service Check the status of the mysql service using command : systemctl status mysql Shut down mysql service using command : systemctl stop mysql 2) Delete all existing file of MySQL Server Delete all files inside the server's data directory. Also delete all files inside the directories specified by the --innodb_data_home_dir, --innodb_log_group_home_dir, and --innodb_undo_directory options for restore, if the directories are different from the data directory. 3) Restore full Backup mysqlbackup  --defaults-file=/etc/mysql/mysql.conf.d/mysqld.cnf --d...
Read more

Oracle Database 19C Installation on Windows Server 2016

-
Image
Oracle Database 19C Installation on Windows Server 2016 In Database world, Its important to be on the latest version of the database flavor. Though Oracle have release 21c Database as well but by far Oracle 19C is most stable version.( You also check our similar blog for  Installation of Microsoft SQL Server 2016 ) Please do also check out blog for  Oracle 19c New Features to know about Oracle 19c features.  In this blog, We will be installing Oracle 19C DB on Windows Server. 1) Create required directory for Oracle Home and Oracle Base. Oracle Base: E:\app\oracle Oracle Home: E:\app\oracle\db\19.0.0\dbhome_1 2) Move the binary to E:\app\oracle\product\19.0.0 directory and unzip 3) Check unzipped directory. 4)Right Click on setup and  Run Setup as Administrator: 5)   On Configuration Screen, Select Set up software only 6)   On Database Installation Option page, Select Single instance Database installation for stand alone database server. 7)  O...
Read more

MySQL InnoDB Cluster Restore/Create Issue : - Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000)

-
Image
MySQL InnoDB Cluster Restore Issue : - Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000) Recently ,We have been restoring and recreating MySQL InnoDB Cluster and faced below issue after firing : MySQL mysqlhost01:3306 ssl JS > var cluster = dba.createCluster('testdbCluster') .. ..... ... Creating InnoDB cluster 'testdbCluster' on 'mysqlhost01:3306'... Adding Seed Instance... ERROR: Unable to start Group Replication for instance 'mysqlhost01:3306'. Please check the MySQL server error log for more information. Dba.createCluster: Group Replication failed to start: MySQL Error 3094 (HY000): mysqlhost01:3306: The START GROUP_REPLICATION command failed as the applier module failed to start. (RuntimeError) MySQL mysqlhost01:3306 ssl JS > Below is full command output with error message: Below are the message in MySQL error log: This issue is Caused by the old(original server) relay log information exiting in metadata tables ....
Read more