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 --datadir=/var/lib
Read more

Oracle 19c New Features

-
Oracle 19c New Features As Oracle Support have made 12.2 version of Oracle ,its has become important for us to upgrade our 12c database to 19c.And before upgrade any database to latest version , We need to know the latest new features of that particular version.  In the current blog , We are going to discuss about new features of the Oracle 19C database : 1)Automatic Indexing  This is one of the important Oracle database 19c New feature. Automatic Indexing is one of the great feature included in 19c . It automates index management tasks, such as creating, rebuilding, and dropping indexes in an Oracle Database based on changes in the application workload. This feature improves database performance by managing indexes automatically in an Oracle Database. Oracle has provided new package DBMS_AUTO_INDEX for this. This enables automatic indexing in a database, but creates any new auto indexes as invisible indexes, so that they cannot be used in SQL statements: EXEC DBMS_AUTO_INDEX.CONFIGURE
Read more

Install & Configure MySQL Router - MySQL InnoDB Cluster

-
Image
Install & Configure MySQL Router -  MySQL InnoDB Cluster MySQL Router is one of the important component of MySQL InnoDB Cluster as it's used by applications to connect to the MySQL DBs running on cluster.  In this blog, We will show How we can install and configure MySQL Router either on application server or on dedicated server for MySQL Router. Below are the step to install and configure MySQL Router: 1) Install MySQL Router on the Server(In our case , We are restoring MySQL Router on the ubuntu server). Run command as root user : apt-get install MySQL-router 2) Bootstrap or Configure MySQL Router mysqlrouter --bootstrap clusteradmin@mysqlhost01:3306 --user=mysqlrouter In Case of any issue in configuring MySQL Router ,We can use -force option of the bootstrap. mysqlrouter --bootstrap clusteradmin@n4ldbdev5030:3306 --directory=/home/myrouter --user=mysqlrouter --force 3) Test Connectivity via MySQL Router. mysqlsh --uri clusteradmin@localhost:6446 you can learn more about
Read more