Uninstalling Advanced Server on Linux v11
Note that after uninstalling Advanced Server, the cluster data files remain intact and the service user persists. You may manually remove the cluster data and service user from the system.
Uninstalling on RHEL/AlmaLinux/Rocky Linux
You can use variations of the rpm or dnf command to remove installed packages. Note that removing a package does not damage the Advanced Server data directory.
Include the -e option when invoking the rpm command to remove an installed package; the command syntax is:
rpm -e <package_name>
Where package_name is the name of the package that you would like to remove.
You can use the dnf remove command to remove a package installed by dnf. To remove a package, open a terminal window, assume superuser privileges, and enter the command:
dnf remove <package_name>
Where package_name is the name of the package that you would like to remove.
rpm doesn't remove a package that another package requires. If you attempt to remove a package that satisfies a package dependency, rpm provides a warning.
Note
In RHEL or Rocky Linux or AlmaLinux 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8, you must disable the clean_requirements_on_remove parameter in the /etc/yum.conf file.
To uninstall Advanced Server and its dependent packages; use the following command:
dnf remove edb-as11-server*
Uninstalling on Debian or Ubuntu
To uninstall Advanced Server, invoke the following command. The configuration files and data directory remains intact.
apt-get remove edb-as11-server*
To uninstall Advanced Server, configuration files, and data directory, invoke the following command:
apt-get purge edb-as11-server*
Uninstalling on SLES
To uninstall Advanced Server, assume the identity of a root user and invoke the following command:
zypper remove edb-as11-server
Updating an RPM Installation
If you have an existing Advanced Server RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the edb.repo file, assume superuser privileges and enter:
On RHEL or CentOS 7:
yum upgrade edb-repo
On RHEL or Rocky Linux/AlmaLinux 8:
dnf upgrade edb-repo
yum or dnf will update the edb.repo file to enable access to the current EDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum or dnf to upgrade all packages whose names include the expression edb:
On RHEL or CentOS 7:
yum upgrade edb*
On RHEL or Rocky Linux/AlmaLinux 8:
dnf upgrade edb*
Note
The yum upgrade or dnf upgrade command will only perform an update between minor releases; to update between major releases, you must use pg_upgrade.
For more information about using yum commands and options, enter yum --help on your command line.
For more information about using dnf commands and options, visit:
https://docs.fedoraproject.org/en-US/quick-docs/dnf/
Updating Components on a SLES Host:
To update components installed with zypper, use the zypper update command.