From 2c2a9cb1665be85e50dcddcf738694ba6f9e4e43 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 11:26:47 -0500 Subject: [PATCH 01/97] first draft of platform support and Power install section --- .../2.1.0/02_requirements_overview.mdx | 12 +- .../05_installing_the_hadoop_data_adapter.mdx | 240 +++++++++++------- 2 files changed, 158 insertions(+), 94 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx index 13360808b72..95cda34ddde 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx @@ -12,14 +12,14 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - - RHEL 8.x and 7.x - - CentOS 8.x and 7.x - - OL 8.x and 7.x + - RHEL 8/CentOS 8/OL 8 + - RHEL 7/CentOS 7/OL 7 - Ubuntu 20.04 and 18.04 LTS - Debian 10.x and 9.x -**Linux on IBM Power8/9 (LE)** - - - RHEL 7.x +**Linux on IBM Power (ppc64le)** + - RHEL 8 + - RHEL 7/CentOS 7 + The Hadoop Foreign Data Wrapper supports use of the Hadoop file system using a HiveServer2 interface or Apache Spark using the Spark Thrift Server. diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index 9ec328fdbf5..15b02f799bd 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -8,71 +8,59 @@ The Hadoop Foreign Data Wrapper can be installed with an RPM package. During the -## Installing the Hadoop Foreign Data Wrapper using an RPM Package +## Installing the on Linux x86-64 (amd64) -You can install the Hadoop Foreign Data Wrapper using an RPM package on the following platforms: +You can install the Hadoop Foreign Data Wrapper on the following operating systems on x86-64: -- [RHEL or CentOS 7 PPCLE](#rhel_centos7_PPCLE) -- [RHEL 7](#rhel7) - [RHEL 8](#rhel8) -- [CentOS 7](#centos7) +- [RHEL 7](#rhel7) - [CentOS 8](#centos8) +- [CentOS 7](#centos7) +- [buntu/Debian](#on-debian-or-ubuntu) - -### On RHEL or CentOS 7 PPCLE -1. Use the following command to create a configuration file and install Advance Toolchain: + - ```text - rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b +### On RHEL 8 - cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -3. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +3. Install the EPEL repository: ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -4. Install the EPEL repository: +4. Enable the additional repositories to resolve dependencies: ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: +5. Disable the built-in PostgreSQL module: ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + dnf -qy module disable postgresql ``` - 6. Install the selected package: - + ```text dnf install edb-as-hdfs_fdw ``` where `xx` is the server version number. - ### On RHEL 7 @@ -109,13 +97,11 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll where `xx` is the server version number. + +### On CentOS 8 - - -### On RHEL 8 - 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: ```text @@ -131,13 +117,13 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll 3. Install the EPEL repository: ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf -y install epel-release ``` 4. Enable the additional repositories to resolve dependencies: ```text - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + dnf config-manager --set-enabled PowerTools ``` 5. Disable the built-in PostgreSQL module: @@ -153,8 +139,6 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll where `xx` is the server version number. - - ### On CentOS 7 @@ -185,54 +169,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll where `xx` is the server version number. - - - - - -### On CentOS 8 - - -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: - - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -3. Install the EPEL repository: - - ```text - dnf -y install epel-release - ``` - -4. Enable the additional repositories to resolve dependencies: - - ```text - dnf config-manager --set-enabled PowerTools - ``` - -5. Disable the built-in PostgreSQL module: - - ```text - dnf -qy module disable postgresql - ``` -6. Install the selected package: - - ```text - dnf install edb-as-hdfs_fdw - ``` - - where `xx` is the server version number. - - - -## Installing the Hadoop Foreign Data Wrapper on a Debian or Ubuntu Host +### On Debian or Ubuntu To install the Hadoop Foreign Data Wrapper on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit the [EDB website](https://www.enterprisedb.com/repository-access-request/). @@ -292,3 +229,130 @@ The following steps will walk you through on using the EDB apt repository to ins ``` where `xx` is the server version number. + +## Installing on IBM Power (ppc64le) + +You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): + + - [RHEL 8](/#on-rhel-8-1) + - [RHEL 7/CentOS 7](#on-rhel-7-or-centos-7) + +### On RHEL 8 +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as-hdfs_fdw +``` + +Where `xx` is the server version number. + + + + +### On RHEL 7 or CentOS 7 + +1. Use the following command to create a configuration file and install Advance Toolchain: + + ```text + rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + + cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +4. Install the EPEL repository: + + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ``` + +5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: + + ```text + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` + +6. Install the selected package: + + ```text + dnf install edb-as-hdfs_fdw + ``` + + where `xx` is the server version number. + + + From 9328cd11ee60aab0f1ee94bd9e09b396e62bb016 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 12:49:21 -0500 Subject: [PATCH 02/97] Fixed typo --- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index 15b02f799bd..ed0eff4e4b9 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the Hadoop Foreign Data Wrapper on the following operating syste - [RHEL 7](#rhel7) - [CentOS 8](#centos8) - [CentOS 7](#centos7) -- [buntu/Debian](#on-debian-or-ubuntu) +- [Ubuntu/Debian](#on-debian-or-ubuntu) From 6c9387c0b1f8bfcfa1144838b8bdc8af0df975ab Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 13:23:01 -0500 Subject: [PATCH 03/97] removed CentOS 7 for Power per Kelly --- .../hadoop_data_adapter/2.1.0/02_requirements_overview.mdx | 2 +- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx index 95cda34ddde..a949e4ed2fa 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx @@ -19,7 +19,7 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux on IBM Power (ppc64le)** - RHEL 8 - - RHEL 7/CentOS 7 + - RHEL 7 The Hadoop Foreign Data Wrapper supports use of the Hadoop file system using a HiveServer2 interface or Apache Spark using the Spark Thrift Server. diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index ed0eff4e4b9..ef8f68b92c9 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -4,7 +4,6 @@ title: "Installing the Hadoop Foreign Data Wrapper" -The Hadoop Foreign Data Wrapper can be installed with an RPM package. During the installation process, the installer will satisfy software prerequisites. If yum encounters a dependency that it cannot resolve, it will provide a list of the required dependencies that you must manually resolve. @@ -302,7 +301,7 @@ Where `xx` is the server version number. -### On RHEL 7 or CentOS 7 +### On RHEL 7 1. Use the following command to create a configuration file and install Advance Toolchain: From 3d92f8aca69f7b6b14fef6a428cabc1995a079e7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 14:28:54 -0500 Subject: [PATCH 04/97] fixed another typo --- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index ef8f68b92c9..42e7f429744 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -7,7 +7,7 @@ title: "Installing the Hadoop Foreign Data Wrapper" -## Installing the on Linux x86-64 (amd64) +## Installing on Linux x86-64 (amd64) You can install the Hadoop Foreign Data Wrapper on the following operating systems on x86-64: From 3794fa849522c8088fafb067b699820b02f514d0 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Sat, 8 Jan 2022 01:01:53 +0530 Subject: [PATCH 05/97] Added EPAS Installation steps for IBM power (ppc64le) on RHEL 8 Added EPAS Installation steps for IBM power (ppc64le) on RHEL 8 --- ...age_manager_to_install_advanced_server.mdx | 105 ++++++++++++++---- 1 file changed, 83 insertions(+), 22 deletions(-) diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 4b3dc1b0868..416abea3f34 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -85,7 +85,7 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -### Installing Advanced Server on a CentOS Host +## Installing on CentOS You can use an RPM package to install Advanced Server on a CentOS host. @@ -174,7 +174,7 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a RHEL Host +## Installing on RHEL You can use an RPM package to install Advanced Server on a RHEL host. @@ -273,13 +273,82 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a CentOS/RHEL 7 ppc64le Host +## Installing on IBM Power (ppc64le) -You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc64le host. +You can install EDB Postgres Advanced Server on the following operating systems on IBM Power (ppc64le): -- To install the Advance Toolchain repository: +- RHEL 8 +- RHEL 7 + +### On RHEL 8 + +This topic describes how to install EDB Postgres Advanced Server and includes steps for getting started with your cluster and creating a database. + +There are three steps to completing an installation: + +- Setting up the repository +- Installing the package +- Performing the initial configuration + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: - On CentOS or RHEL 7 ppc64le: + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as13-server +``` + +Installing the server package creates an operating system user named `enterprisedb`. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. + +### On RHEL 7 + +You can use an RPM package to install Advanced Server on a RHEL 7 ppc64le host. + +- To install the Advance Toolchain repository: ```text rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b @@ -302,8 +371,6 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 - To install the repository configuration file, assume superuser privileges and invoke the following command: - On CentOS or RHEL 7 ppc64le: - ```text yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` @@ -316,17 +383,13 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 - Before installing Advanced Server, you must install the `epel-release` package: - On CentOS or RHEL 7 ppc64le: - ```text # yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm # yum makecache ``` -- Enable the repository: - - On RHEL 7, enable the `optional`, `extras`, and `HA` repositories to satisfy package dependencies: +- Enable the `optional`, `extras`, and `HA` repositories to satisfy package dependencies: ```text subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" @@ -348,11 +411,9 @@ rpm --import /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY Then, you can use `yum install` command to install Advanced Server. For example, to install the server and its core components, use the command: -- On CentOS or RHEL 7 ppc64le: - - ```text - yum -y install edb-as13-server - ``` +```text +yum -y install edb-as13-server +``` When you install an RPM package that is signed by a source that is not recognized by your system, `yum` may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter a `y`, and press `Return` to continue. @@ -651,7 +712,7 @@ Please note: The available package list is subject to change. The packages that install the database server component create a unit file (on version 7.x or 8.x hosts) and service startup scripts. -### Creating a Database Cluster and Starting the Service +## Creating a Database Cluster and Starting the Service The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: @@ -711,13 +772,13 @@ To list all the available clusters, use the following command: -#### Specifying Cluster Options with INITDBOPTS +### Specifying Cluster Options with INITDBOPTS You can use the `INITDBOPTS` variable to specify your cluster configuration preferences. By default, the `INITDBOPTS` variable is commented out in the service configuration file; unless modified, when you run the service startup script, the new cluster will be created in a mode compatible with Oracle databases. Clusters created in this mode will contain a database named `edb`, and have a database superuser named `enterprisedb`. -##### Initializing the Cluster in Oracle Mode +#### Initializing the Cluster in Oracle Mode If you initialize the database using Oracle compatibility mode, the installation includes: @@ -757,7 +818,7 @@ If you initialize the database using Oracle compatibility mode, the installation -##### Initializing the Cluster in Postgres Mode +#### Initializing the Cluster in Postgres Mode Clusters created in PostgreSQL mode do not include compatibility features. To create a new cluster in PostgreSQL mode, remove the pound sign (#) in front of the `INITDBOPTS` variable, enabling the `"--no-redwood-compat"` option. Clusters created in PostgreSQL mode will contain a database named `postgres` and have a database superuser named `postgres`. From 7c4ace7295d47ad6a6d9e1515343dc12e3bbd961 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 15:10:51 -0500 Subject: [PATCH 06/97] fixed jump link and stray reference to CentOS Power --- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index 42e7f429744..d6ac92250f4 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -233,8 +233,8 @@ The following steps will walk you through on using the EDB apt repository to ins You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): - - [RHEL 8](/#on-rhel-8-1) - - [RHEL 7/CentOS 7](#on-rhel-7-or-centos-7) + - [RHEL 8](#on-rhel-8-1) + - [RHEL 7](#on-rhel-7-or-centos-7) ### On RHEL 8 There are two steps to completing an installation: @@ -268,7 +268,7 @@ sudo su - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` - Where `USERNAME:PASSWORD` is the username and password available from your + where `USERNAME:PASSWORD` is the username and password available from your [EDB account](https://www.enterprisedb.com/user). 1. Install the EPEL repository and refresh the cache: @@ -296,7 +296,7 @@ sudo su - dnf -y install edb-as-hdfs_fdw ``` -Where `xx` is the server version number. +where `xx` is the server version number. From 2a526821704ddf81a54e474df608c93f9331f9e7 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 10 Jan 2022 15:18:51 +0530 Subject: [PATCH 07/97] Added PEM Installation steps for IBM power (ppc64le) on RHEL 8 Added PEM Installation steps for IBM power (ppc64le) on RHEL 8 --- .../03_installing_pem_server_on_linux.mdx | 65 +++++++++++++++++++ 1 file changed, 65 insertions(+) diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index 95480d09af2..1c10ee26349 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -181,3 +181,68 @@ zypper install edb-pem The operating system user `pem` gets created while installing the PEM Server. The PEM Server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session gets saved to this user's home directory. After installing PEM Server using `zypper`, you must configure the PEM Server. For detailed information see [Configuring the PEM Server on Linux Platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). + +## Installing the PEM Server on IBM Power (ppc64le) + +This topic describes how to install Postgres Enteprise Manager (PEM) Server. + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + + ```sh + dnf -qy module disable postgresql + ``` + +### Installing the Package + + ```sh + dnf -y install edb-pem + ``` + +!!! Note + The operating system user `pem` gets created while installing the PEM Server. The PEM Server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session gets saved to this user's home directory. \ No newline at end of file From 6dc227a050e9770ca6d531d89491caf887174fb9 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 13 Jan 2022 14:18:10 +0530 Subject: [PATCH 08/97] Added the IBM Power install steps for version 11 and 12 Added the IBM Power install steps for version 11 and 12 --- ...age_manager_to_install_advanced_server.mdx | 91 ++++++++++++++++-- ...age_manager_to_install_advanced_server.mdx | 95 ++++++++++++++++--- ...age_manager_to_install_advanced_server.mdx | 2 +- 3 files changed, 165 insertions(+), 23 deletions(-) diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 0eb0b86d18e..5dc0781681a 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -94,7 +94,7 @@ After receiving your repository credentials you can: - Modify the file, providing your user name and password. - Install Advanced Server. -### Installing Advanced Server on a CentOS Host +## Installing on CentOS You can use an RPM package to install Advanced Server on a CentOS host. @@ -167,7 +167,7 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a RHEL Host +## Installing on RHEL You can use an RPM package to install Advanced Server on a RHEL host (RHEL 8, 8.3 and onwards). @@ -250,9 +250,80 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a CentOS/RHEL 7 ppc64le Host +## Installing on IBM Power (ppc64le) -You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc64le host. +You can install EDB Postgres Advanced Server on the following operating systems on IBM Power (ppc64le): + +- RHEL 8 +- RHEL 7 + +### On RHEL 8 + +This topic describes how to install EDB Postgres Advanced Server and includes steps for getting started with your cluster and creating a database. + +There are three steps to completing an installation: + +- Setting up the repository +- Installing the package +- Performing the initial configuration + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as12-server +``` + +Installing the server package creates an operating system user named `enterprisedb`. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. + +### On RHEL 7 + +You can use an RPM package to install Advanced Server on a RHEL 7 ppc64le host. - To install the Advance Toolchain repository: @@ -441,7 +512,7 @@ For more information about using `dnf` commands and options, visit: -## Installing Advanced Server on a SLES Host +## Installing on SLES You must have credentials that allow access to the EnterpriseDB repository to install Advanced Server on a SLES host. To request credentials for the repository, visit: @@ -680,11 +751,11 @@ Then: zypper refresh ``` -## Updating Components on a SLES Host: +### Updating Components on a SLES Host: To update components installed with zypper, use the `zypper update` command. -## Uninstalling Advanced Server on a SLES Host: +### Uninstalling Advanced Server on a SLES Host: To uninstall Advanced Server, assume the identity of a root user and invoke the following command: @@ -692,7 +763,7 @@ To uninstall Advanced Server, assume the identity of a root user and invoke the zypper remove edb-as11-server ``` -## Installing Advanced Server on a Debian or Ubuntu Host +## Installing on Debian or Ubuntu To install Advanced Server on a Debian or Ubuntu host, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit: @@ -841,7 +912,7 @@ Please note: The available package list is subject to change. The packages that install the database server component create a unit file (on version 7.x or 8.x hosts) and service startup scripts. -### Creating a Database Cluster and Starting the Service +## Creating a Database Cluster and Starting the Service The PostgreSQL `initdb` command creates a database cluster. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: @@ -901,7 +972,7 @@ To list all the available clusters, use the following command: -#### Specifying Cluster Options with INITDBOPTS +### Specifying Cluster Options with INITDBOPTS You can use the `INITDBOPTS` variable to specify your cluster configuration preferences. By default, the `INITDBOPTS` variable is commented out in the service configuration file; unless modified, when you run the service startup script, the new cluster will be created in a mode compatible with Oracle databases. Clusters created in this mode will contain a database named `edb`, and have a database superuser named `enterprisedb`. diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 930e133d97a..da3ef185990 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -94,7 +94,7 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -### Installing Advanced Server on a CentOS Host +## Installing on CentOS You can use an RPM package to install Advanced Server on a CentOS host. @@ -183,7 +183,7 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a RHEL Host +## Installing on RHEL You can use an RPM package to install Advanced Server on a RHEL host. @@ -282,9 +282,80 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a CentOS/RHEL 7 ppc64le Host +## Installing on IBM Power (ppc64le) -You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc64le host. +You can install EDB Postgres Advanced Server on the following operating systems on IBM Power (ppc64le): + +- RHEL 8 +- RHEL 7 + +### On RHEL 8 + +This topic describes how to install EDB Postgres Advanced Server and includes steps for getting started with your cluster and creating a database. + +There are three steps to completing an installation: + +- Setting up the repository +- Installing the package +- Performing the initial configuration + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as12-server +``` + +Installing the server package creates an operating system user named `enterprisedb`. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. + +### On RHEL 7 + +You can use an RPM package to install Advanced Server on a RHEL 7 ppc64le host. - To install the Advance Toolchain repository: @@ -499,7 +570,7 @@ For more information about using `dnf` commands and options, visit: -## Installing Advanced Server on a SLES Host +## Installing on SLES You must have credentials that allow access to the EnterpriseDB repository to install Advanced Server on a SLES host. To request credentials for the repository, visit: @@ -779,12 +850,12 @@ Install pgAgent: zypper -n install edb-as12-pgagent ``` -## Updating Components on a SLES Host: +### Updating Components on a SLES Host: To update components installed with zypper, use the `zypper update` command. -## Uninstalling Advanced Server on a SLES Host: +### Uninstalling Advanced Server on a SLES Host: To uninstall Advanced Server, assume the identity of a root user and invoke the following command: @@ -792,7 +863,7 @@ To uninstall Advanced Server, assume the identity of a root user and invoke the zypper remove edb-as12-server ``` -## Installing Advanced Server on a Debian or Ubuntu Host +## Installing on Debian or Ubuntu To install Advanced Server on a Debian or Ubuntu host, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit: @@ -941,7 +1012,7 @@ Please note: The available package list is subject to change. The packages that install the database server component create a unit file (on version 7.x or 8.x hosts) and service startup scripts. -### Creating a Database Cluster and Starting the Service +## Creating a Database Cluster and Starting the Service The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: @@ -1001,13 +1072,13 @@ To list all the available clusters, use the following command: -#### Specifying Cluster Options with INITDBOPTS +### Specifying Cluster Options with INITDBOPTS You can use the `INITDBOPTS` variable to specify your cluster configuration preferences. By default, the `INITDBOPTS` variable is commented out in the service configuration file; unless modified, when you run the service startup script, the new cluster will be created in a mode compatible with Oracle databases. Clusters created in this mode will contain a database named `edb`, and have a database superuser named `enterprisedb`. -##### Initializing the Cluster in Oracle Mode +#### Initializing the Cluster in Oracle Mode If you initialize the database using Oracle compatibility mode, the installation includes: @@ -1047,7 +1118,7 @@ If you initialize the database using Oracle compatibility mode, the installation -##### Initializing the Cluster in Postgres Mode +#### Initializing the Cluster in Postgres Mode Clusters created in PostgreSQL mode do not include compatibility features. To create a new cluster in PostgreSQL mode, remove the pound sign (#) in front of the `INITDBOPTS` variable, enabling the `"--no-redwood-compat"` option. Clusters created in PostgreSQL mode will contain a database named `postgres` and have a database superuser named `postgres`. diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 416abea3f34..e493f7dda6e 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -288,7 +288,7 @@ There are three steps to completing an installation: - Setting up the repository - Installing the package -- Performing the initial configuration +- Performing the initial configuration For each step, you must be logged in as superuser. From 8f33e45c2016ff7243cafddc99c349b5ab668fdc Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 13 Jan 2022 14:20:02 +0530 Subject: [PATCH 09/97] Minor fix Minor fix --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 5dc0781681a..ffe2ca8e220 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -316,7 +316,7 @@ sudo su - #### Installing the Package ```sh -dnf -y install edb-as12-server +dnf -y install edb-as11-server ``` Installing the server package creates an operating system user named `enterprisedb`. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as12`. From c191408fe7e24a938306d9d2dfa645307d2cd77d Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 13 Jan 2022 16:44:20 +0530 Subject: [PATCH 10/97] Added the PEM Agent installation steps for IBM Power RHEL8 Added the PEM Agent installation steps for IBM Power RHEL8 --- .../03_installing_pem_server_on_linux.mdx | 6 +- .../08_installing_pem_agent_on_linux.mdx | 64 +++++++++++++++++++ 2 files changed, 68 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index 1c10ee26349..bbbb67b9774 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -182,7 +182,7 @@ zypper install edb-pem After installing PEM Server using `zypper`, you must configure the PEM Server. For detailed information see [Configuring the PEM Server on Linux Platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). -## Installing the PEM Server on IBM Power (ppc64le) +## Installing the PEM Server on IBM Power (ppc64le) RHEL 8 This topic describes how to install Postgres Enteprise Manager (PEM) Server. @@ -245,4 +245,6 @@ sudo su - ``` !!! Note - The operating system user `pem` gets created while installing the PEM Server. The PEM Server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session gets saved to this user's home directory. \ No newline at end of file + The operating system user `pem` gets created while installing the PEM Server. The PEM Server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session gets saved to this user's home directory. + +After installing PEM Server using `yum` or `dnf`, you need to configure the PEM Server. For more detailed information see [Configuring the PEM Server on Linux platforms](05_configuring_the_pem_server_on_linux/#configuring_the_pem_server_on_linux). diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx index 8e1857f09a3..f34573afaca 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx @@ -165,3 +165,67 @@ zypper install edb-pem-agent ``` After installing the PEM Agent, you must register the agent. For more detailed information see [Registering a PEM Agent](09_registering_a_pem_agent/#registering-a-pem-agent). + +## Installing a PEM Agent on IBM Power (ppc64le) RHEL 8 + +This topic describes how to install Postgres Enteprise Manager (PEM) Agent. + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + + ```sh + dnf -qy module disable postgresql + ``` + +### Installing the Package + + ```sh + dnf -y install edb-pem-agent + ``` + +After installing the PEM Agent, you must register the agent. For more detailed information see [Registering a PEM Agent](09_registering_a_pem_agent/#registering-a-pem-agent). From 8814303c1ae633faf99f162e2a444cc8bfd599dc Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 18 Jan 2022 11:46:19 -0500 Subject: [PATCH 11/97] match docs with edb script --- .../01_preparing_azure/index.mdx | 29 +++++++++---------- 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index 563d5350cfe..001a0e70fb9 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -25,29 +25,26 @@ EDB recommends using the `biganimal-preflight-azure` script to check whether all EDB provides a shell script called [`biganimal-preflight-azure`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/biganimal-preflight-azure), which automatically checks whether requirements and resource limits are met in your Azure subscription based on the clusters you plan to deploy. 1. Open the [Azure Cloud Shell](https://shell.azure.com/) in your browser. -2. From the Azure Cloud Shell, use the following command to run the `biganimal-preflight-azure` script. +2. From the Azure Cloud Shell, use the following command to see the requirements for running the `biganimal-preflight-azure` script. ```sh - curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ - \ - --instance-type \ - --high-availability \ - --endpoint \ - --activate-region \ - --onboard + curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ ``` - Replace the variables in the arguments and options as follows: + The script lists options and required arguments. + + Required arguments are: + + - ``: Enter the Azure subscription ID of your BigAnimal deployment. + - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/support/03a_region_support) for a list of possible regions. - - ``: Enter the Azure subscription ID of your BigAnimal deployment. - - ``: Enter the Azure region where your clusters are being deployed. - - ``: Enter **e2s_v3**, which indicates the type of virtual machine instance (Esv3 with 2 cores) used in BigAnimal. - - `--high-availability` or `-a`: Indicates that high availability is enabled in your clusters. - - ``: Indicates either **public** or **private** endpoints. - - `--activate-region` or `-r`: Indicates that no clusters are currently deployed in the region. + Possible options are: + - ``: Enter the Azure VM instance type for the BigAnimal cluster. Running the `biganimal-preflight-azure` script with no options provides a list of possible VM instance types. + - ``: Enter the type of network endpoint for the BigAnimal cluster, either **public** or **private**. + - `--activate-region` or `-r`: Specifies region activation if no clusters currently exist in the region. - `--onboard`: Checks if the user and subscription are correctly configured. - For example, if you want to deploy a cluster in an Azure subscription having an ID of `12412ab3d-1515-2217-96f5-0338184fcc04`, in the `eastus2` region, in a `public` network, and with no existing cluster deployed, run the following command: + For example, if you want to deploy a cluster in an Azure subscription having an ID of `12412ab3d-1515-2217-96f5-0338184fcc04`, with an instance type of `e2s_v3`, in the `eastus2` region, in a `public` network, and with no existing cluster deployed, run the following command: ```sh curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ From b77f9bd4837fccd50a213bbdb01f58cba8e2a216 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 18 Jan 2022 12:19:52 -0500 Subject: [PATCH 12/97] Tweaked link to region support --- .../release/getting_started/01_preparing_azure/index.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index 001a0e70fb9..c0989b71215 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -39,6 +39,7 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/support/03a_region_support) for a list of possible regions. Possible options are: + - ``: Enter the Azure VM instance type for the BigAnimal cluster. Running the `biganimal-preflight-azure` script with no options provides a list of possible VM instance types. - ``: Enter the type of network endpoint for the BigAnimal cluster, either **public** or **private**. - `--activate-region` or `-r`: Specifies region activation if no clusters currently exist in the region. From f521f28ce2572363ea60709149db875f3d880d82 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 18 Jan 2022 12:24:18 -0500 Subject: [PATCH 13/97] another tweak to link --- .../release/getting_started/01_preparing_azure/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index c0989b71215..bf52506cb2c 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -36,7 +36,7 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. Required arguments are: - ``: Enter the Azure subscription ID of your BigAnimal deployment. - - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/support/03a_region_support) for a list of possible regions. + - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/03a_region_support) for a list of possible regions. Possible options are: From 3214868ad87455b1457517ab79e589bd9ea6a322 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 18 Jan 2022 12:29:52 -0500 Subject: [PATCH 14/97] Removed slash at end of line --- .../release/getting_started/01_preparing_azure/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index bf52506cb2c..dff8f79243a 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -28,7 +28,7 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. 2. From the Azure Cloud Shell, use the following command to see the requirements for running the `biganimal-preflight-azure` script. ```sh - curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ + curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s ``` The script lists options and required arguments. From d32651cc68bfe4e083e6935b01bbbf3015321363 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 19 Jan 2022 14:33:32 +0530 Subject: [PATCH 15/97] Added EPAS 14 Install steps for IBM Power RHEL 8 Added EPAS 14 Install steps for IBM Power RHEL 8 --- ...age_manager_to_install_advanced_server.mdx | 89 ++++++++++++++++--- 1 file changed, 76 insertions(+), 13 deletions(-) diff --git a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 324ad06d49e..10a1fb133fc 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -81,7 +81,7 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -### Installing Advanced Server on a CentOS Host +## Installing on CentOS You can use an RPM package to install Advanced Server on a CentOS host. @@ -170,7 +170,7 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a RHEL Host +## Installing on RHEL You can use an RPM package to install Advanced Server on a RHEL host. @@ -269,13 +269,82 @@ After installing Advanced Server, you must configure the installation. For more !!! Note During the installation, `yum` may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -### Installing Advanced Server on a CentOS/RHEL 7 ppc64le Host +## Installing on IBM Power (ppc64le) -You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc64le host. +You can install EDB Postgres Advanced Server on the following operating systems on IBM Power (ppc64le): -- To install the Advance Toolchain repository: +- RHEL 8 +- RHEL 7 + +### On RHEL 8 + +This topic describes how to install EDB Postgres Advanced Server and includes steps for getting started with your cluster and creating a database. + +There are three steps to completing an installation: + +- Setting up the repository +- Installing the package +- Performing the initial configuration + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Replace `'USERNAME:PASSWORD'` below with your username and password available from your + [EDB account](https://www.enterprisedb.com/user) in the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` - On CentOS or RHEL 7 ppc64le: +1. Install EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as14-server +``` + +Installing the server package creates an operating system user named `enterprisedb`. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash` and the user's home directory is `/var/lib/edb/as13`. + +### On RHEL 7 + +You can use an RPM package to install Advanced Server on a RHEL 7 ppc64le host. + +- To install the Advance Toolchain repository: ```text rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b @@ -298,8 +367,6 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 - To install the repository configuration file, assume superuser privileges and invoke the following command: - On CentOS or RHEL 7 ppc64le: - ```text yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` @@ -312,8 +379,6 @@ You can use an RPM package to install Advanced Server on a CentOS or RHEL 7 ppc6 - Before installing Advanced Server, you must install the `epel-release` package: - On CentOS or RHEL 7 ppc64le: - ```text # yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm @@ -344,8 +409,6 @@ rpm --import /etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY Then, you can use `yum install` command to install Advanced Server. For example, to install the server and its core components, use the command: -- On CentOS or RHEL 7 ppc64le: - ```text yum -y install edb-as14-server ``` @@ -491,7 +554,7 @@ For more information about using `dnf` commands and options, visit: -## Installing Advanced Server on a Debian or Ubuntu Host +## Installing on Debian or Ubuntu To install Advanced Server on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit: From fa6a614a8cfaf7d55cddb4ea8bcbbfa279f82e4f Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 10 Jan 2022 09:25:01 -0500 Subject: [PATCH 16/97] first draft of pgpool rhel8 power --- ...stalling_and_configuring_the_pgpool-II.mdx | 120 +++++++++++++----- 1 file changed, 88 insertions(+), 32 deletions(-) diff --git a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx index 5def372d045..007e1f3c0f9 100644 --- a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx +++ b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx @@ -10,34 +10,27 @@ legacyRedirectsGenerated: !!! Note Pgpool-II runs as a service on Linux systems. Pgpool-II is not supported on Windows. - -The following table lists the Pgpool version and their corresponding EDB Postgres Advanced Server and PostgreSQL versions. - -The Pgpool version required for your EDB Postgres Advanced Server and PostgreSQL installation is version-specific, but the documented and supported functionality of each version is the same. - -| **Pgpool Version** | **Postgres Version** | **Supported Platforms** | -|--------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Pgpool 4.2 | EDB Postgres Advanced Server and PostgreSQL 13 | RHEL 7 - x86_64, RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa | -| Pgpool 4.2 | EDB Postgres Advanced Server and PostgreSQL 12 | RHEL 7 - x86_64, and RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 4.2 | EDB Postgres Advanced Server and PostgreSQL 11 | RHEL 7 - x86_64, RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 4.2 | EDB Postgres Advanced Server and PostgreSQL 9.6 and 10 | RHEL 7 - x86_64 and RHEL 7 - ppc64le | -| Pgpool 4.1 | EDB Postgres Advanced Server 13 | RHEL 7 - x86_64, RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa | -| Pgpool 4.1 | EDB Postgres Advanced Server 12 | RHEL 7 - x86_64, and RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 4.1 | EDB Postgres Advanced Server 11 | RHEL 7 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 4.0 | EDB Postgres Advanced Server 12 | RHEL 7 - x86_64, and RHEL 8 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 4.0 | EDB Postgres Advanced Server 11 | RHEL 7 - x86_64
RHEL 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
SLES 12 | -| Pgpool 3.7 | EDB Postgres Advanced Server 10 and 11 | RHEL 7 - x86_64 and RHEL 7 - ppc64le | -| Pgpool 3.6 | EDB Postgres Advanced Server 9.6 and 10 | RHEL 7 - x86_64
RHEL 7 - ppc64le
Linux graphical installer | -!!! Note - - Pgpool is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform. - - Pgpool is certified with the Pgpool-II extensions shipped with EDB Postgres Advanced Server and PostgreSQL. +This table lists the latest Pgpool-II versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. Pgpool-II is supported on the same platforms as EDB Postgres Advanced Server. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas) for details. + +| Pgpool | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | EPAS 10 | EPAS 9.6 | +| ------ | ------- | ------- | ------- | ------- | ------- | -------- | +| 4.2 | N | Y | Y | Y | Y | Y | +| 4.1 | N | Y | Y | Y | N | N | +| 4.0 | N | N | Y | Y | N | N | +| 3.7 | N | N | N | Y | Y | N | + -This guide assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. +The documented and supported functionality of each version of Pgpool-II is the same. The information in this documentation applies to all supported versions of Pgpool-II. + +See the following topics to install Pgpool-II on specific hosts. + + +This documentation assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. Before installing the repository configuration, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). -## Installing Pgpool-II on a CentOS Host +## Installing Pgpool-II on a CentOS x86-64 Host Perform the following steps to install Pgpool-II on a CentOS host: @@ -103,7 +96,7 @@ Perform the following steps to install Pgpool-II on a CentOS host: dnf install edb-pgpool ``` - Where <xx> is the Pgpool release version. + where <xx> is the Pgpool release version. For example, to install the latest Pgpool Version 4.2, invoke the following command: @@ -125,7 +118,7 @@ Perform the following steps to install Pgpool-II on a CentOS host: -## Installing Pgpool-II on an RHEL Host +## Installing Pgpool-II on an RHEL x86-64 Host Before creating the repository configuration file, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -201,7 +194,7 @@ Perform the following steps to install Pgpool-II: dnf install edb-pgpool ``` - Where <xx> is the Pgpool release version. + where <xx> is the Pgpool release version. For example, to install the latest Pgpool Version 4.2, invoke the following command: @@ -223,7 +216,7 @@ Perform the following steps to install Pgpool-II: -## Installing Pgpool-II on an RHEL/CentOS 7 PPCLE Host +## Installing Pgpool-II on an RHEL 7 ppc64le Host Before creating the repository configuration file, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -277,11 +270,74 @@ Perform the following steps to install Pgpool-II on an RHEL/CentOS 7 PPC64LE Hos yum -y install edb-pgpool ``` - Where <xx> is the Pgpool-II version you want to install. + where <xx> is the Pgpool-II version you want to install. + +## Installing Pgpool-II on an RHEL 8 ppc64le Host + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-pgpool +``` + +where <xx> is the Pgpool-II version you want to install. -## Installing Pgpool-II on a Debian/Ubuntu Host +## Installing Pgpool-II on a x86-64 Debian/Ubuntu Host To install Pgpool-II on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit the [EDB website](https://www.enterprisedb.com/user). @@ -339,13 +395,13 @@ Perform the following steps to install a Debian package using the EDB apt reposi apt-get install -y edb-pgpool ``` -Where <xx> is the Pgpool release version. + where <xx> is the Pgpool release version. After installing Pgpool-II on a Debian host, the configuration files are located in the `/etc/edb/edb-pgpool` directory, where <x.y> is the Pgpool release version. -## Installing Pgpool-II on a SLES 12 Host +## Installing Pgpool-II on a x86-64 SLES 12 Host You can use the Zypper package manager to install Pgpool-II on a SLES 12 host. Zypper will attempt to satisfy package dependencies but requires access to specific repositories that EDB does not host. @@ -395,7 +451,7 @@ You can use the Zypper package manager to install Pgpool-II on a SLES 12 host. Z zypper install -n edb-pgpool ``` - Where <xx> is the Pgpool version you wish to install. + where <xx> is the Pgpool version you wish to install. From b47662bfff37d3dcdd9211dc54bf1a818fa9d00f Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Jan 2022 14:29:47 -0500 Subject: [PATCH 17/97] Replaced CentOS 8 with Rocky Linux 8 --- ...01_installing_and_configuring_the_pgpool-II.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx index 007e1f3c0f9..12678f14e58 100644 --- a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx +++ b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx @@ -30,9 +30,9 @@ This documentation assumes that the user has some knowledge of installation and Before installing the repository configuration, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). -## Installing Pgpool-II on a CentOS x86-64 Host +## Installing Pgpool-II on a CentOS/Rocky Linux x86-64 Host -Perform the following steps to install Pgpool-II on a CentOS host: +Perform the following steps: 1. To install the repository configuration, assume superuser privileges, and invoke the platform-specific command: @@ -42,7 +42,7 @@ Perform the following steps to install Pgpool-II on a CentOS host: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -62,13 +62,13 @@ Perform the following steps to install Pgpool-II on a CentOS host: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for CentOS 8: +4. The following steps are applicable only for Rocky Linux 8: a. Enable the PowerTools repository to satisfy additional package dependencies: @@ -90,7 +90,7 @@ Perform the following steps to install Pgpool-II on a CentOS host: yum install edb-pgpool ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf install edb-pgpool @@ -106,7 +106,7 @@ Perform the following steps to install Pgpool-II on a CentOS host: yum install edb-pgpool42 ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf install edb-pgpool42 From 844486f1c867e681c1e592951e55b17b91595f6a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Jan 2022 14:40:54 -0500 Subject: [PATCH 18/97] more CentOS->Rocky updates --- product_docs/docs/pgpool/4.2/02_extensions.mdx | 10 +++++----- .../pgpool/4.2/03_configuring_connection_pooling.mdx | 2 +- product_docs/docs/pgpool/4.2/05_upgrade.mdx | 4 ++-- .../docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx | 8 ++++---- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgpool/4.2/02_extensions.mdx b/product_docs/docs/pgpool/4.2/02_extensions.mdx index bab2659af11..49a0b84ca20 100644 --- a/product_docs/docs/pgpool/4.2/02_extensions.mdx +++ b/product_docs/docs/pgpool/4.2/02_extensions.mdx @@ -19,7 +19,7 @@ Before installing Pgpool-II extensions, install the EDB Postgres Advanced Server The following section walks you through the steps of installing Pgpool-II extensions. To request credentials for the repository, visit [the EDB website](https://www.enterprisedb.com/user). -### Installing Pgpool-II Extension on a CentOS Host +### Installing Pgpool-II Extension on a CentOS/Rocky Linux Host Assume superuser privileges and perform the following steps to install Pgpool-II extensions on a CentOS host: @@ -31,7 +31,7 @@ Assume superuser privileges and perform the following steps to install Pgpool-II yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -51,13 +51,13 @@ Assume superuser privileges and perform the following steps to install Pgpool-II yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. For CentOS 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ```text dnf config-manager --set-enabled PowerTools @@ -157,7 +157,7 @@ Perform the following steps to install Pgpool-II extensions on an RHEL host: yum -y install edb-as13-pgpool42-extensions ``` - On RHEL/CentOS 8: + On RHEL/Rocky Linux 8: ```text dnf install edb-as-pgpool-extensions diff --git a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx index 114c4696827..155f9421eee 100644 --- a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx +++ b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx @@ -164,7 +164,7 @@ Modify the `postgresql.conf` file (located in `/var/lib/edb/as13/data`), adding Save the configuration file, and restart the server: - To restart on RHEL/CentOS 7 and 8 platforms: + To restart on RHEL/CentOS 7 and 8 and Rocky Linux 8 platforms: ```text systemctl restart edb-as-13 diff --git a/product_docs/docs/pgpool/4.2/05_upgrade.mdx b/product_docs/docs/pgpool/4.2/05_upgrade.mdx index 75a0742fad3..6dfb901db6d 100644 --- a/product_docs/docs/pgpool/4.2/05_upgrade.mdx +++ b/product_docs/docs/pgpool/4.2/05_upgrade.mdx @@ -32,7 +32,7 @@ where <xx> is the Pgpool version you want to upgrade. For example, to upgrade yum upgrade edb-pgpool37 ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf upgrade edb-pgpool @@ -67,7 +67,7 @@ Where `` is the EDB Postgres Advanced Server version, and `` is the Pgpo !!! Note Only minor version upgrade is supported (for example, you can upgrade from 3.6.20 to 3.6.21 extension, but not 3.7.14). -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf upgrade edb-as-pgpool-extensions diff --git a/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx b/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx index 3f7b6a25d86..d564c4f8720 100644 --- a/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx +++ b/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx @@ -10,7 +10,7 @@ The following section outlines the process of uninstalling Pgpool-II and its ext ## Uninstalling Pgpool-II -### Uninstalling Pgpool-II on an RHEL/CentOS Host +### Uninstalling Pgpool-II on an RHEL//Rocky Linux Host To uninstall Pgpool-II, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum erase edb-pgpool ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf erase edb-pgpool @@ -60,7 +60,7 @@ The Pgpool-II graphical installer creates an uninstaller in the installation dir The following section outlines the process of uninstalling Pgpool-II and its extensions. -### Uninstalling Pgpool-II Extensions on an RHEL/CentOS Host +### Uninstalling Pgpool-II Extensions on an RHEL/CentOS/Rocky Linux Host To remove extensions from the server, execute the following command: @@ -70,7 +70,7 @@ On RHEL/CentOS 7: yum erase edb-as-pgpool-extensions ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf erase edb-as-pgpool-extensions From 77ee2f640bd063b86d4938ff121bf6cf07a1af2f Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 19 Jan 2022 15:34:00 -0500 Subject: [PATCH 19/97] Revised approach after conversation with Dee Dee --- .../getting_started/01_preparing_azure/index.mdx | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index dff8f79243a..080712711a1 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -25,25 +25,22 @@ EDB recommends using the `biganimal-preflight-azure` script to check whether all EDB provides a shell script called [`biganimal-preflight-azure`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/biganimal-preflight-azure), which automatically checks whether requirements and resource limits are met in your Azure subscription based on the clusters you plan to deploy. 1. Open the [Azure Cloud Shell](https://shell.azure.com/) in your browser. -2. From the Azure Cloud Shell, use the following command to see the requirements for running the `biganimal-preflight-azure` script. +2. From the Azure Cloud Shell, run the following command: ```sh - curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s + curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s [options] ``` - - The script lists options and required arguments. - - Required arguments are: + Where the required arguments are: - ``: Enter the Azure subscription ID of your BigAnimal deployment. - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/03a_region_support) for a list of possible regions. Possible options are: - - ``: Enter the Azure VM instance type for the BigAnimal cluster. Running the `biganimal-preflight-azure` script with no options provides a list of possible VM instance types. + - ``: Enter the Azure VM instance type for the BigAnimal cluster. Running the `biganimal-preflight-azure` script with no arguments provides a list of possible VM instance types. - ``: Enter the type of network endpoint for the BigAnimal cluster, either **public** or **private**. - `--activate-region` or `-r`: Specifies region activation if no clusters currently exist in the region. - - `--onboard`: Checks if the user and subscription are correctly configured. + - `--onboard`: Checks if the user and subscription are correctly configured. The behavior of the script defaults to `--onboard` if you provide no other options. For example, if you want to deploy a cluster in an Azure subscription having an ID of `12412ab3d-1515-2217-96f5-0338184fcc04`, with an instance type of `e2s_v3`, in the `eastus2` region, in a `public` network, and with no existing cluster deployed, run the following command: From fff22b54952902ec3d8d2a05e7525d6e4ba3dba3 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 10 Jan 2022 06:04:08 -0500 Subject: [PATCH 20/97] first draft of PostGIS rhel8 Power updates --- .../postgis/3.1.4/01a_installing_postgis.mdx | 118 +++++++++++++----- 1 file changed, 88 insertions(+), 30 deletions(-) diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index 87158ddc4d6..c178a8dc666 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -5,31 +5,26 @@ title: "Installing PostGIS" -The following table lists the latest PostGIS versions and their corresponding Advanced Server versions. +This table lists the latest PostGIS versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. PostGIS is supported on the same platforms as EDB Postgres Advanced Server. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas) for details. + +| PostGIS | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | EPAS 10 | EPAS 9.6 | +| ------- | ------- | ------- | ------- | ------- | ------- | -------- | +| 3.1 | Y | Y | Y | Y | Y | Y | +| 3.0 | Y | Y | Y | Y | N | N | +| 2.5 | N | N | Y | Y | N | Y | +| 2.4 | N | N | N | Y | Y | Y | +| 2.3 | N | N | N | N | Y | Y | + + +The documented and supported functionality of each version of PostGIS is the same. The information in this documentation applies to all supported versions of PostGIS. + +See the following sections to install EDB PostGIS on specific hosts. -!!! Note - The PostGIS version required by your Advanced Server installation is version-specific, but the documented and supported functionality of each version is the same. The information in this guide applies to each version listed in the table below. - -| **PostGIS Version** | **Supported Advanced Server Versions** | **Supported Platforms** | -| ------------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `PostGIS 3.1` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.1` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | -| `PostGIS 3.1` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | -| `PostGIS 3.1` | Advanced Server 9.6, 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 | -| `PostGIS 2.5` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | -| `PostGIS 2.5` | Advanced Server 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | -| `PostGIS 2.4` | Advanced Server 9.6, 10 and 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -| `PostGIS 2.3` | Advanced Server 9.6 and 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -!!! Note - PostGIS is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform. -## Installing PostGIS on a CentOS Host +## Installing PostGIS on a CentOS x86-64 Host Before creating the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -103,7 +98,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install edb-as-postgis ``` - Where *<xx>* denotes the Advanced Server version older than 13.0. + where <xx> denotes the Advanced Server version older than 13.0. On CentOS 7, to install PostGIS older versions (for example PostGIS 3.0.2) for EDB Advanced Server version 13.0: @@ -117,7 +112,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install edb-as-postgis- ``` - Where *<xx>* is the Advanced Server version older than 13.0 and*<y.y.y>* is the older PostGIS version. + where <xx> is the Advanced Server version older than 13.0 and <y.y.y> is the older PostGIS version. For example, to install PostGIS 2.5.4 on Advanced Server 12: @@ -132,7 +127,7 @@ Perform the following steps to install PostGIS on a CentOS Host: -## Installing PostGIS on an RHEL Host +## Installing PostGIS on an RHEL Host x86-64 Before installing the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -214,7 +209,7 @@ Perform the following steps to install PostGIS on an RHEL Host: yum -y install edb-as-postgis ``` - Where *<xx>* denotes the Advanced Server version older than 13.0 + where <xx> denotes the Advanced Server version older than 13.0. On RHEL 7, to install PostGIS older versions (for example PostGIS 3.0.2) for EDB Advanced Server version 13.0: @@ -228,7 +223,7 @@ Perform the following steps to install PostGIS on an RHEL Host: yum -y install edb-as-postgis- ``` - Where *<xx>* is the Advanced Server version older than 13.0 and*<y.y.y>* is the older PostGIS version. + where <xx> is the Advanced Server version older than 13.0 and <y.y.y> is the older PostGIS version. For example, to install PostGIS 2.5.4 on EDB Advanced Server version 12: @@ -243,11 +238,11 @@ Perform the following steps to install PostGIS on an RHEL Host: -## Installing PostGIS on an RHEL/CentOS 7 PPCLE Host +## Installing PostGIS on an RHEL 7 ppcl64le Host Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). -Perform the following steps to install PostGIS on an RHEL/CentOS 7 PPC64LE Host. +Perform the following steps to install PostGIS on an RHEL 7 PPC64LE Host. 1. Create the Advance Toolchain repository configuration file: @@ -305,7 +300,7 @@ Perform the following steps to install PostGIS on an RHEL/CentOS 7 PPC64LE Host. yum -y install edb-as-postgis ``` - Where *<xx>* denotes the Advanced Server version older than 13.0 + where <xx> denotes the Advanced Server version older than 13.0. To install PostGIS older versions (for example PostGIS 3.0.2) for EDB Advanced Server version 13.0: @@ -319,7 +314,7 @@ Perform the following steps to install PostGIS on an RHEL/CentOS 7 PPC64LE Host. yum -y install edb-as-postgis- ``` - Where *<xx>* is the Advanced Server version older than 13.0 and*<y.y.y>* is the older PostGIS version. + where <xx> is the Advanced Server version older than 13.0 and <y.y.y> is the older PostGIS version. For example, to install PostGIS 2.5.4 on EDB Advanced Server version 12: @@ -332,6 +327,69 @@ Perform the following steps to install PostGIS on an RHEL/CentOS 7 PPC64LE Host. !!! Note After installing PostGIS with a package manager, you must manually create a template database and the required PostGIS extension. +## Installing PostGIS on an RHEL 8 ppcl64le Host + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as-postgis3 +``` + +where <xx> is the version of the server. + ## Installing PostGIS on a Debian/Ubuntu Host @@ -400,7 +458,7 @@ Perform the following steps to install PostGIS Debian package using the Enterpri apt-get install edb-as-postgis ``` - Where *<xx>* is the Advanced Server version older than 13.0 + where <xx> is the Advanced Server version older than 13.0 For example, to install the latest version of PostGIS for EDB Advanced Server version 12: From fbb872f6a848acfed18fdcb836ae0efc6791e1fc Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 10 Jan 2022 08:07:59 -0500 Subject: [PATCH 21/97] commit to trigger deploy --- product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index c178a8dc666..50b1deb5487 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -20,7 +20,6 @@ The documented and supported functionality of each version of PostGIS is the sam See the following sections to install EDB PostGIS on specific hosts. - From 69b02a54c517f35e86833cdd521ec017def8864f Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 10 Jan 2022 09:54:35 -0500 Subject: [PATCH 22/97] minor cleanup --- product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index 50b1deb5487..92f6f99626f 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -126,7 +126,7 @@ Perform the following steps to install PostGIS on a CentOS Host: -## Installing PostGIS on an RHEL Host x86-64 +## Installing PostGIS on an RHEL x86-64 Host Before installing the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -492,7 +492,7 @@ Perform the following steps to install PostGIS Debian package using the Enterpri -## Installing PostGIS on a SLES 12 Host +## Installing PostGIS on a SLES 12 x86-64 Host Perform the following steps to install PostGIS on an SLES Host using the Zypper package manager: From 6ff36bdee240ea7e23908b623205e66be60d0665 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 11:40:00 -0500 Subject: [PATCH 23/97] CentOS 8 > Rocky Linux 8 --- .../postgis/3.1.2/01_installing_postgis.mdx | 24 +++++++++---------- .../postgis/3.1.2/05_uninstalling_postgis.mdx | 8 +++---- .../postgis/3.1.4/01a_installing_postgis.mdx | 12 +++++----- .../postgis/3.1.4/05_uninstalling_postgis.mdx | 6 ++--- 4 files changed, 24 insertions(+), 26 deletions(-) diff --git a/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx b/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx index e78768ab908..204cbe5b47c 100644 --- a/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx @@ -15,24 +15,22 @@ The following table lists the latest PostGIS versions and their corresponding Ad | **PostGIS Version** | **Supported Advanced Server Versions** | **Supported Platforms** | | ------------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `PostGIS 3.1` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.1` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | -| `PostGIS 3.1` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | +| `PostGIS 3.1` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | +| `PostGIS 3.1` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | +| `PostGIS 3.1` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | | `PostGIS 3.1` | Advanced Server 9.6, 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | +| `PostGIS 3.0` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | +| `PostGIS 3.0` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | `PostGIS 3.0` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 | -| `PostGIS 2.5` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | +| `PostGIS 2.5` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | | `PostGIS 2.5` | Advanced Server 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | | `PostGIS 2.4` | Advanced Server 9.6, 10 and 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | | `PostGIS 2.3` | Advanced Server 9.6 and 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -!!! Note - PostGIS is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform. -## Installing PostGIS on a CentOS Host +## Installing PostGIS on a CentOS/Rocky Linux Host Before creating the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -46,7 +44,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -66,13 +64,13 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for CentOS 8 platform: +4. The following steps are applicable only for Rocky Linux 8 platform: a. Enable the PowerTools repository to satisfy package dependencies: @@ -94,7 +92,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install edb-as13-postgis3 ``` - On CentOS 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: + On Rocky Linux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: ```text dnf -y install edb-as13-postgis3 diff --git a/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx b/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx index 554b96931b4..cc5ff6f1d5e 100644 --- a/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx +++ b/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx @@ -10,9 +10,9 @@ legacyRedirectsGenerated: This section walks you through the process of uninstalling PostGIS. -## Uninstalling PostGIS on a CentOS/RHEL Host +## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux Host -To uninstall PostGIS on a CentOS/RHEL host, assume the identity of the root user and invoke the following command: +To uninstall PostGIS on a CentOS/RHEL/Rocky Linux host, assume the identity of the root user and invoke the following command: On CentOS/RHEL 7 for EPAS version 13: @@ -28,13 +28,13 @@ yum erase edb-as-postgis-* Where *<xx>* is the Advanced Server version and <y.y.y> is the PostGIS version you want to uninstall. -On CentOS/RHEL 8 for EPAS version 13: +On Rocky Linux/RHEL 8 for EPAS version 13: ```text dnf -y erase edb-as13-postgis3* ``` -On CentOS/RHEL 8 for older vesions of EPAS: +On Rocky Linux/RHEL 8 for older vesions of EPAS: ```text dnf erase edb-as-postgis-* diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index 92f6f99626f..7eebaa73f1b 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -23,11 +23,11 @@ See the following sections to install EDB PostGIS on specific hosts. -## Installing PostGIS on a CentOS x86-64 Host +## Installing PostGIS on a CentOS/Rocky Linux x86-64 Host Before creating the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). -Perform the following steps to install PostGIS on a CentOS Host: +Perform the following steps: 1. To create the repository configuration file, assume superuser privileges, and invoke the platform-specific command: @@ -37,7 +37,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -57,13 +57,13 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for CentOS 8 platform: +4. The following steps are applicable only for Rocky Linux 8 platform: a. Enable the PowerTools repository to satisfy package dependencies: @@ -85,7 +85,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install edb-as13-postgis3 ``` - On CentOS 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: + On Rocky Linux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: ```text dnf -y install edb-as13-postgis3 diff --git a/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx b/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx index 4d9b90edb08..d72596b3ab5 100644 --- a/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx @@ -7,7 +7,7 @@ title: "Uninstalling PostGIS" This section walks you through the process of uninstalling PostGIS. -## Uninstalling PostGIS on a CentOS/RHEL Host +## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux Host To uninstall PostGIS on a CentOS/RHEL host, assume the identity of the root user and invoke the following command: @@ -25,13 +25,13 @@ yum erase edb-as-postgis-* Where *<xx>* is the Advanced Server version and <y.y.y> is the PostGIS version you want to uninstall. -On CentOS/RHEL 8 for EPAS version 13: +On Rocky Linux/RHEL 8 for EPAS version 13: ```text dnf -y erase edb-as13-postgis3* ``` -On CentOS/RHEL 8 for older vesions of EPAS: +On Rocky Linux/RHEL 8 for older versions of EPAS: ```text dnf erase edb-as-postgis-* From bcc11c544d17453ac55ae3bc424ba8a533de8d14 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 13:05:36 -0500 Subject: [PATCH 24/97] first draft OCL connector rhel 8 power updates --- .../14.1.0.1/02_supported_platforms.mdx | 7 +- ...ling_and_configuring_the_ocl_connector.mdx | 82 +++++++++++++++++-- 2 files changed, 77 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx index bef5c8c8f67..5cd3e2a8eec 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx @@ -7,11 +7,12 @@ title: "Supported Platforms" The EDB OCL Connector is certified with Advanced Server version 9.6 and above. The EDB OCL Connector native packages are supported on the following 64-bit platforms: -- Red Hat Enterprise Linux (x86_64) 7.x and 8.x -- CentOS (x86_64) 7.x and 8.x +- RHEL 7.x and 8.x (x86_64) +- CentOS 7.x and 8.x (x86_64) - OL Linux 7.x and 8.x -- PPC-LE 8 running RHEL or CentOS 7.x +- RHEL 7.x (ppc64le) - SLES 12.x +- RHEL 8.x (ppc64le) - Debian 9.x and 10.x - Ubuntu 18.04 and 20.04 LTS diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index 75e505f9b07..59daa503b49 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -11,14 +11,15 @@ You can use an RPM package, a native package, or a graphical installer to instal You can install the OCL Connector using an RPM package on the following platforms: -- [RHEL 7](#rhel7) -- [RHEL 8](#rhel8) -- [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [RHEL 7 (x86-64)](#rhel7) +- [RHEL 8 (x86-64)](#rhel8) +- [CentOS 7 (x86-64)](#centos7) +- [CentOS 8 (x86-64)](#centos8) +- [RHEL 8 (ppc64le)](#on-rhel-8-ppc64le) -### On RHEL 7 +### On RHEL 7 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -84,7 +85,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On RHEL 8 +### On RHEL 8 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -151,7 +152,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 7 +### On CentOS 7 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -214,7 +215,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On CentOS 8 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -278,6 +279,68 @@ When you install an RPM package that is signed by a source that is not recognize During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. +### On RHEL 8 ppc64le + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-oci +``` + + ### Updating an RPM Installation If you have an existing `OCL Connector` 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: @@ -304,7 +367,8 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `dnf upgrade edb-oci-devel` -## Installing the Connector on an SLES 12 Host + +## Installing the Connector on an SLES 12 x86-64 Host You can use the zypper package manager to install the connector on an SLES 12 host. zypper will attempt to satisfy package dependencies as it installs a package, but requires access to specific repositories that are not hosted at EDB. Before installing the connector, use the following commands to add EDB repository configuration files to your SLES host: From 9184f694ecfde22088b55d54b0322ed67f764835 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 17:08:02 -0500 Subject: [PATCH 25/97] fixed order in platform support --- .../docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx index 5cd3e2a8eec..1440764829b 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx @@ -11,8 +11,8 @@ The EDB OCL Connector is certified with Advanced Server version 9.6 and above. T - CentOS 7.x and 8.x (x86_64) - OL Linux 7.x and 8.x - RHEL 7.x (ppc64le) -- SLES 12.x - RHEL 8.x (ppc64le) +- SLES 12.x - Debian 9.x and 10.x - Ubuntu 18.04 and 20.04 LTS From a3b49f64f326057dc8365ecf1a811dcea4032a33 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 12:22:20 -0500 Subject: [PATCH 26/97] CentOS 8 > Rocky Linux 8 (latest version only) --- .../ocl_connector/14.1.0.1/02_supported_platforms.mdx | 3 ++- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx index 1440764829b..72c002d4658 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx @@ -8,7 +8,8 @@ title: "Supported Platforms" The EDB OCL Connector is certified with Advanced Server version 9.6 and above. The EDB OCL Connector native packages are supported on the following 64-bit platforms: - RHEL 7.x and 8.x (x86_64) -- CentOS 7.x and 8.x (x86_64) +- Rocky Linux 8.x (x86_64) +- CentOS 7.x (x86_64) - OL Linux 7.x and 8.x - RHEL 7.x (ppc64le) - RHEL 8.x (ppc64le) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index 59daa503b49..fd44119bdc3 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -14,7 +14,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7 (x86-64)](#rhel7) - [RHEL 8 (x86-64)](#rhel8) - [CentOS 7 (x86-64)](#centos7) -- [CentOS 8 (x86-64)](#centos8) +- [Rocky Linux 8 (x86-64)](#centos8) - [RHEL 8 (ppc64le)](#on-rhel-8-ppc64le) @@ -215,7 +215,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 x86-64 +### On Rocky Linux 8 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -349,7 +349,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -361,7 +361,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-oci` From 1a8110e3e267dc24ef88e6a23cb958573b327f84 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 13:27:27 -0500 Subject: [PATCH 27/97] first draft ODBC connector rhel8 power --- .../13.1.0.2/02_requirements_overview.mdx | 8 +- .../01_installing_edb-odbc.mdx | 80 +++++++++++++++++-- 2 files changed, 76 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx index 47c38d68fb9..30998867b8c 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx @@ -13,10 +13,10 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: -- Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- CentOS (x86_64) 8.x and 7.x -- OL Linux 8.x and 7.x -- PPC-LE 8 running RHEL or CentOS 7.x +- RHEL 8.x and 7.x (x86_64) +- CentOS 8.x and 7.x (x86_64) +- OL Linux 8.x and 7.x (x86_64) +- RHEL 8.x and 7.x (ppc64le) - SLES 12.x - Debian 10.x and 9.x - Ubuntu 20.04 and 18.04 LTS diff --git a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index cebeb3dab17..2f27646bc11 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -9,15 +9,16 @@ The EDB ODBC Connector is distributed and installed with the EDB Postgres Advanc You can install the ODBC Connector using an RPM package on the following platforms: -- [RHEL 7](#rhel7) -- [RHEL 7 PPCLE](#centos7_PPCLE) -- [RHEL 8](#rhel8) -- [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [RHEL 7 x86-64](#rhel7) +- [RHEL 7 ppc64le](#centos7_PPCLE) +- [RHEL 8 x86-64](#rhel8) +- [RHEL 8 ppc64le](#rhel8_PPCLE) +- [CentOS 7 x86-64](#centos7) +- [CentOS 8 x86-64](#centos8) -### On RHEL 7 +### On RHEL 7 x86-64 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -83,7 +84,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On RHEL 7 PPCLE +### On RHEL 7 ppc64le Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: 1. Use the following commands to install Advance Toolchain: @@ -163,7 +164,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On RHEL 8 +### On RHEL 8 x86-64 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -228,6 +229,69 @@ When you install an RPM package that is signed by a source that is not recognize During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. +### On RHEL 8 ppc64le + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-odbc +``` + + + From 15d8466a72cdf48f2b9a6272a258cb4510c729e6 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 17:11:39 -0500 Subject: [PATCH 28/97] fixed link --- .../13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 2f27646bc11..b9032a5a76c 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -12,7 +12,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7 x86-64](#rhel7) - [RHEL 7 ppc64le](#centos7_PPCLE) - [RHEL 8 x86-64](#rhel8) -- [RHEL 8 ppc64le](#rhel8_PPCLE) +- [RHEL 8 ppc64le](#on-rhel-8-ppc64le) - [CentOS 7 x86-64](#centos7) - [CentOS 8 x86-64](#centos8) From fccceaac5a5294717a1f69021c90de3fa0cbfcb5 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 12:14:18 -0500 Subject: [PATCH 29/97] CentOS 8 > Rocky Linux 8 (for 13.1.0.2 only) --- .../odbc_connector/13.1.0.2/02_requirements_overview.mdx | 3 ++- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx index 30998867b8c..56e6414f2ae 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx @@ -14,7 +14,8 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - RHEL 8.x and 7.x (x86_64) -- CentOS 8.x and 7.x (x86_64) +- Rocky Linux 8.x (x86_64) +- CentOS 7.x (x86_64) - OL Linux 8.x and 7.x (x86_64) - RHEL 8.x and 7.x (ppc64le) - SLES 12.x diff --git a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index b9032a5a76c..e158bfb6a74 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -14,7 +14,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 8 x86-64](#rhel8) - [RHEL 8 ppc64le](#on-rhel-8-ppc64le) - [CentOS 7 x86-64](#centos7) -- [CentOS 8 x86-64](#centos8) +- [Rocky Linux 8 x86-64](#centos8) @@ -358,7 +358,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -430,7 +430,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -442,7 +442,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-odbc` From b576e25ca2e5787fa3f92402e2699ef6c67c6656 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 09:15:23 -0500 Subject: [PATCH 30/97] first draft of JDBC Connector RHEL 8 Power updates --- .../42.2.24.1/02_requirements_overview.mdx | 4 +- ...ling_the_connector_with_an_rpm_package.mdx | 79 +++++++++++++++++-- .../index.mdx | 4 - 3 files changed, 73 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx index 4ecbc237475..9314c14a8fb 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx @@ -13,9 +13,9 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: -- Red Hat Enterprise Linux and CentOS (x86_64) 7.x and 8.x +- RHEL and CentOS 7.x and 8.x (x86_64) - OL Linux 7.x and 8.x -- PPC-LE 8 running RHEL or CentOS 7.x +- RHEL 8.x (ppc64le) - SLES 12.x - Debian 9.x and 10.x - Ubuntu 18.04 and Ubuntu 20.4 LTS diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 80f57eecb3f..d27ad855a17 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -7,14 +7,15 @@ title: "Installing the Connector with an RPM Package" You can install the JDBC Connector using an RPM package on the following platforms: -- [RHEL 7](#rhel7) -- [RHEL 8](#rhel8) -- [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [RHEL 7 x86-64](#rhel7) +- [RHEL 8 x86-64](#rhel8) +- [CentOS 7 x86-64](#centos7) +- [CentOS 8 x86-64](#centos8) +- [RHEL 8 ppcle]9 -## On RHEL 7 +## On RHEL 7 x86-64 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -78,7 +79,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On RHEL 8 +## On RHEL 8 x86-64 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -143,7 +144,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On CentOS 7 +## On CentOS 7 x86-64 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -204,7 +205,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On CentOS 8 +## On CentOS 8 x86-64 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -266,6 +267,68 @@ When you install an RPM package that is signed by a source that is not recognize During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. +## On RHEL ppc64le + +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-jdbc +``` + + ## Updating an RPM Installation If you have an existing JDBC Connector 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: diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/index.mdx index 9146ad75447..7655c8c8f9a 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/index.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/index.mdx @@ -13,8 +13,4 @@ You can use the Advanced Server graphical installer or an RPM package to add the The following sections describe these installation methods. -
-installing_the_connector_with_an_rpm_package installing_the_connector_on_an_sles_12_host installing_a_deb_package_on_a_debian_or_ubuntu_host using_the_graphical_installer_to_install_the_connector configuring_the_advanced_server_jdbc_connector - -
From 753d32f8a16aa0f28898a360110240a3f7214bdf Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 10:39:33 -0500 Subject: [PATCH 31/97] fixed typo --- .../01_installing_the_connector_with_an_rpm_package.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index d27ad855a17..75b8b0f0ce8 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -267,7 +267,7 @@ When you install an RPM package that is signed by a source that is not recognize During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. -## On RHEL ppc64le +## On RHEL 8 ppc64le There are two steps to completing an installation: From c0eeb6539aa734154f9116c4cdf056edfab35f5b Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 13:09:29 -0500 Subject: [PATCH 32/97] fixes --- .../01_installing_the_connector_with_an_rpm_package.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 75b8b0f0ce8..7d84f435c16 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -11,7 +11,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 8 x86-64](#rhel8) - [CentOS 7 x86-64](#centos7) - [CentOS 8 x86-64](#centos8) -- [RHEL 8 ppcle]9 +- [RHEL 8 ppc64le](#on-rhel-8-ppc64le) From a0c8adde60ee08943b3702311b238d8c4b531378 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 12:34:00 -0500 Subject: [PATCH 33/97] CentOS 8 > Rocky Linux 8 (latest version only) --- .../jdbc_connector/42.2.24.1/02_requirements_overview.mdx | 3 ++- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx index 9314c14a8fb..489cd3ea7b4 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx @@ -13,7 +13,8 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: -- RHEL and CentOS 7.x and 8.x (x86_64) +- RHEL and CentOS 7.x (x86_64) +- RHEL and Rocky Linux 8.x (x86_64) - OL Linux 7.x and 8.x - RHEL 8.x (ppc64le) - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 7d84f435c16..1db4e3742dc 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -10,7 +10,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7 x86-64](#rhel7) - [RHEL 8 x86-64](#rhel8) - [CentOS 7 x86-64](#centos7) -- [CentOS 8 x86-64](#centos8) +- [Rocky Linux 8 x86-64](#centos8) - [RHEL 8 ppc64le](#on-rhel-8-ppc64le) @@ -337,7 +337,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -347,6 +347,6 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-jdbc` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-jdbc` From c5e075250f49afb46988e42d0d93df26600e0424 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 9 Jan 2022 07:27:07 -0500 Subject: [PATCH 34/97] first draft of pgbouncer rhel8 power updates --- ...ng_pgbouncer_on_a_linux_or_centos_host.mdx | 2 +- ...g_pgbouncer_on_a_debian_or_ubuntu_host.mdx | 2 +- ...3_installing_pgbouncer_on_an_sles_host.mdx | 2 +- ...alling_pgbouncer_on_a_rhel8_ppcle_host.mdx | 61 +++++++++++++++++++ .../pgbouncer/1.16/01_installation/index.mdx | 49 ++++++--------- 5 files changed, 84 insertions(+), 32 deletions(-) create mode 100644 product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx index 836cd267eaa..5f64571cb2f 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PgBouncer on a CentOS Host" +title: "Installing PgBouncer on a CentOS x86-64 Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host.mdx index e9443cf0a69..071c6be0953 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/02_installing_pgbouncer_on_a_debian_or_ubuntu_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PgBouncer on a Debian or Ubuntu Host" +title: "Installing PgBouncer on a Debian or Ubuntu x86-64 Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/03_installing_pgbouncer_on_an_sles_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/03_installing_pgbouncer_on_an_sles_host.mdx index 9f21af19295..fd00b766464 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/03_installing_pgbouncer_on_an_sles_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/03_installing_pgbouncer_on_an_sles_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PgBouncer on an SLES 12 Host" +title: "Installing PgBouncer on an SLES 12 x86-64 Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx new file mode 100644 index 00000000000..106f8c3bf13 --- /dev/null +++ b/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx @@ -0,0 +1,61 @@ +--- +title: "Installing PgBouncer on a RHEL 8 ppc64le Host" +--- +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install pgbouncer +``` diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx index 71c2d9b599c..dcd95b52c4d 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx @@ -9,32 +9,23 @@ legacyRedirectsGenerated: -This section walks you through installing EDB PgBouncer on a CentOS, Debian/Ubuntu, or a Windows host. - -The following table lists the latest PgBouncer versions, their supported corresponding Advanced Server versions, and the supported platforms for each PgBouncer version. - -The PgBouncer version is version-specific, but the documented and supported functionality of each version is the same. The information in this guide applies to each version listed in the table below. - -| **Pgpool Version** | **Advanced Server Version** | **Supported Platforms** | -| ------------------ | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -| `PgBouncer 1.16` | PostgreSQL and Advanced Server 13 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.16` | PostgreSQL and Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer
SUSE Linux Enterprise Server 12 SP5| -| `PgBouncer 1.16` | PostgreSQL and Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer
SUSE Linux Enterprise Server 12 SP5| -| `PgBouncer 1.16` | PostgreSQL and Advanced Server 10 and 9.6 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.15` | PostgreSQL and Advanced Server 13 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.15` | PostgreSQL and Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer
SUSE Linux Enterprise Server 12 SP4| -| `PgBouncer 1.15` | PostgreSQL and Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer
SUSE Linux Enterprise Server 12 SP4| -| `PgBouncer 1.15` | PostgreSQL and Advanced Server 10 and 9.6 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.14` | Advanced Server 13 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.14` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and Debian 10x Buster
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.14` | Advanced Server 11, 10, and 9.6 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer
SUSE Linux Enterprise Server 12 SP4| -| `PgBouncer 1.13` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.12` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/CentOS 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer| -| `PgBouncer 1.9` | Advanced Server 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 Bionic Beaver
Windows 86 x64 Interactive Installer and Linux 86_64 Interactive Installer| -| `PgBouncer 1.7` | Advanced Server 10 and 9.6 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 86 x64 Interactive Installer and Linux 86_64 Interactive Installer| - -
- -installing\_pgbouncer\_on\_a\_linux\_or\_centos\_host installing\_pgbouncer\_on\_a\_debian\_or\_ubuntu\_host installing\_pgbouncer\_on\_an\_sles\_host installing\_pgbouncer\_on\_a\_windows\_host - -
+This table lists the latest PgBouncer versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. PgBouncer is supported on the same platforms as EDB Postgres Advanced Server. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas) for details. + +| pgBouncer | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | EPAS 10 | EPAS 9.6 | +| --------- | ------- | ------- | ------- | ------- | ------- | -------- | +| 1.16 | Y | Y | Y | Y | Y | Y | +| 1.15 | N | Y | Y | Y | Y | Y | +| 1.14 | N | Y | Y | Y | Y | Y | +| 1.13 | N | N | Y | N | N | N | +| 1.12 | N | N | Y | N | N | N | +| 1.9 | N | N | N | Y | Y | Y | +| 1.7 | N | N | N | N | Y | Y | + +The documented and supported functionality of each version of PgBouncer is the same. The information in this documentation applies to all supported versions of PgBouncer. + +See the following topics to install EDB PgBouncer on specific hosts: +- [CentOS x86-64](01_installing_pgbouncer_on_a_linux_or_centos_host) +- [Debian or Ubuntu x86-64](/02_installing_pgbouncer_on_a_debian_or_ubuntu_host) +- [SLES 12 x86-64](03_installing_pgbouncer_on_an_sles_host) +- [RHEL 8 ppcle](03a_installing_pgbouncer_on_a_rhel8_ppcle_host) +- [Windows](04_installing_pgbouncer_on_a_windows_host) \ No newline at end of file From 412b43b172b276bfa9cfa71412dca7a3cef8039e Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 12 Jan 2022 06:15:07 -0500 Subject: [PATCH 35/97] fixed install comman --- .../03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx index 106f8c3bf13..64496826a40 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/03a_installing_pgbouncer_on_a_rhel8_ppcle_host.mdx @@ -57,5 +57,6 @@ sudo su - #### Installing the Package ```sh -dnf -y install pgbouncer +dnf -y install edb-pgbouncer ``` +where `` is the PgBouncer version you want to install. \ No newline at end of file From 02e310ccfead4302b209ac3e852232b0f6649a38 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 12:39:46 -0500 Subject: [PATCH 36/97] CentOS 8 > Rocky Linux 8 --- ...talling_pgbouncer_on_a_linux_or_centos_host.mdx | 14 +++++++------- .../docs/pgbouncer/1.16/01_installation/index.mdx | 2 +- .../pgbouncer/1.16/02_configuration_and_usage.mdx | 2 +- .../docs/pgbouncer/1.16/03_uninstallation.mdx | 4 ++-- 4 files changed, 11 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx index 5f64571cb2f..a0c64dddbba 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PgBouncer on a CentOS x86-64 Host" +title: "Installing PgBouncer on a CentOS/Rocky Linux x86-64 Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -21,7 +21,7 @@ Follow the steps given below to install PgBouncer: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ``` text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -41,19 +41,19 @@ Follow the steps given below to install PgBouncer: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ``` text dnf -y install epel-release ``` -4. For CentOS 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ``` text dnf config-manager --set-enabled PowerTools ``` -5. For CentOS 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8, disable the built-in PostgreSQL module: ``` text dnf -qy module disable postgresql @@ -69,7 +69,7 @@ Follow the steps given below to install PgBouncer: Where <xx> is the PgBouncer version you want to install. - On CentOS 8: + On Rocky Linux 8: ``` text dnf -y install edb-pgbouncer @@ -77,7 +77,7 @@ Follow the steps given below to install PgBouncer: Where <xx> is the PgBouncer version you want to install. - To install PgBouncer 1.16 on CentOS 8, the command is: + To install PgBouncer 1.16 on Rocky Linux 8, the command is: ``` text dnf -y install edb-pgbouncer116 diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx index dcd95b52c4d..a9e56f77be6 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx @@ -24,7 +24,7 @@ This table lists the latest PgBouncer versions and their supported corresponding The documented and supported functionality of each version of PgBouncer is the same. The information in this documentation applies to all supported versions of PgBouncer. See the following topics to install EDB PgBouncer on specific hosts: -- [CentOS x86-64](01_installing_pgbouncer_on_a_linux_or_centos_host) +- [CentOS/Rocky Linux x86-64](01_installing_pgbouncer_on_a_linux_or_centos_host) - [Debian or Ubuntu x86-64](/02_installing_pgbouncer_on_a_debian_or_ubuntu_host) - [SLES 12 x86-64](03_installing_pgbouncer_on_an_sles_host) - [RHEL 8 ppcle](03a_installing_pgbouncer_on_a_rhel8_ppcle_host) diff --git a/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx b/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx index 67a4033eebe..720aed1a9cc 100644 --- a/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx +++ b/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx @@ -105,7 +105,7 @@ default_pool_size = 20 For more information about the settings used in the `pgbouncer.ini` file, click [here](https://pgbouncer.github.io/config.html). -After editing the PgBouncer configuration file to reflect your environment, you must restart the PgBouncer service for the changes to take effect. For CentOS, RHEL, SUSE, and Windows platforms, the PgBouncer service name is `edb-pgbouncer-1.16`, and for Deb packages, the PgBouncer service name is `edb-pgbouncer116`; use platform-specific commands to stop, start, or restart the service as needed. +After editing the PgBouncer configuration file to reflect your environment, you must restart the PgBouncer service for the changes to take effect. For CentOS, Rocky Linux, RHEL, SUSE, and Windows platforms, the PgBouncer service name is `edb-pgbouncer-1.16`, and for Deb packages, the PgBouncer service name is `edb-pgbouncer116`; use platform-specific commands to stop, start, or restart the service as needed. ## Using the PgBouncer Admin Console diff --git a/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx b/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx index e529b55e63b..37ff21405e1 100644 --- a/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx +++ b/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: This section walks you through uninstalling PgBouncer. -## Uninstalling PgBouncer on a RHEL/CentOS Host +## Uninstalling PgBouncer on a RHEL//Rocky Linux Host To uninstall PgBouncer on a CentOS host, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum -y erase edb-pgbouncer ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ``` text dnf -y erase edb-pgbouncer From 09911755caffd6d478a21865f10eda12f456db92 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 11:16:33 -0500 Subject: [PATCH 37/97] first draft of EFM rhel8 Power install instructions --- product_docs/docs/efm/4/03_installing_efm.mdx | 164 ++++++++++++------ 1 file changed, 114 insertions(+), 50 deletions(-) diff --git a/product_docs/docs/efm/4/03_installing_efm.mdx b/product_docs/docs/efm/4/03_installing_efm.mdx index 9be3600858d..fbaf0b5f5cf 100644 --- a/product_docs/docs/efm/4/03_installing_efm.mdx +++ b/product_docs/docs/efm/4/03_installing_efm.mdx @@ -30,57 +30,53 @@ Failover Manager must be installed by root. During the installation process, the After receiving your credentials, you must create the EnterpriseDB repository configuration file on each node of the cluster and then modify the file to enable access. -### RHEL or CentOS 7 PPCLE host - -1. Create a configuration file and install Advance Toolchain: +### RHEL or CentOS 8 x86-64 host +1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text - rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b - - cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -3. Replace ‘USERNAME:PASSWORD’ with your username and password for the EDB repositories: +3. Install the EPEL repository: +- On CentOS 8 ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + dnf -y install epel-release + ``` +- On RHEL 8 + ```text + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -4. Install the EPEL repository: +4. Enable the additional repositories to resolve dependencies: +- On CentOS 8 ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + dnf config-manager --set-enabled PowerTools ``` - -5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: +- On RHEL 8 ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -6. Install the selected package: +5. Disable the built-in PostgreSQL module: ```text - yum -y install edb-efm42 + dnf -qy module disable postgresql + ``` +6. Install the selected package: + ```text + dnf -y install edb-efm42 ``` -### RHEL or CentOS 7 host +### RHEL or CentOS 7 x86-64 host 1. To create the repository configuration file, assume superuser privileges and invoke the following command: @@ -112,52 +108,120 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm42 ``` -### RHEL or CentOS 8 host +### RHEL 8 ppc64le host +There are two steps to completing an installation: -1. To create the repository configuration file, assume superuser privileges and invoke the following command: - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` +- Setting up the repository +- Installing the package -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +For each step, you must be logged in as superuser. - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` +To log in as a superuser: -3. Install the EPEL repository: +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-efm +``` +where `` is the version number of Failover Manager. + +### RHEL 7 ppc64le host + +1. Create a configuration file and install Advance Toolchain: -- On CentOS 8 ```text - dnf -y install epel-release + rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + + cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -- On RHEL 8 + +4. Install the EPEL repository: ```text - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -5. Disable the built-in PostgreSQL module: +5. On RHEL 7 ppc64le, enable the additional repositories to resolve EPEL dependencies: ```text - dnf -qy module disable postgresql + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" ``` + 6. Install the selected package: + ```text - dnf -y install edb-efm42 + yum -y install edb-efm42 ``` + + + ## Debian or Ubuntu host To install Failover Manager, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, see the [EnterpriseDB website](https://www.enterprisedb.com/user/login). From 68dedbc2b6579f55d52203007ea41b6694344a2a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 13:16:00 -0500 Subject: [PATCH 38/97] CentOS 8 > Rocky Linux 8 --- .../efm/3/efm_pgpool_ha_guide/04_appendix_a.mdx | 2 +- product_docs/docs/efm/3/efm_quick_start/index.mdx | 8 +------- .../docs/efm/3/efm_user/03_installing_efm.mdx | 8 ++++---- .../01_encrypting_database_password.mdx | 2 +- product_docs/docs/efm/3/efm_user/05_using_efm.mdx | 14 +++++++------- .../efm/3/efm_user/08_controlling_efm_service.mdx | 6 +++--- .../3/efm_user/12_upgrading_existing_cluster.mdx | 2 +- product_docs/docs/efm/4/03_installing_efm.mdx | 8 ++++---- .../02_encrypting_database_password.mdx | 2 +- product_docs/docs/efm/4/05_using_efm.mdx | 14 +++++++------- .../docs/efm/4/08_controlling_efm_service.mdx | 6 +++--- .../docs/efm/4/12_upgrading_existing_cluster.mdx | 2 +- product_docs/docs/efm/4/efm_quick_start/index.mdx | 8 +------- 13 files changed, 35 insertions(+), 47 deletions(-) diff --git a/product_docs/docs/efm/3/efm_pgpool_ha_guide/04_appendix_a.mdx b/product_docs/docs/efm/3/efm_pgpool_ha_guide/04_appendix_a.mdx index 916c0f1929a..3f741c7a272 100644 --- a/product_docs/docs/efm/3/efm_pgpool_ha_guide/04_appendix_a.mdx +++ b/product_docs/docs/efm/3/efm_pgpool_ha_guide/04_appendix_a.mdx @@ -5,7 +5,7 @@ title: "EFM Pgpool Integration Using Azure Network Load Balancer" -This section describes a specific use case for EFM Pgpool integration, where the database, EFM, and Pgpool are installed on CentOS 8 Virtual Machines in Azure. For this specific use case, Azure Load Balancer (LNB) has been used to distribute the traffic amongst all the active Pgpool Instances instead of directing the traffic using Pgpool VIP. +This section describes a specific use case for EFM Pgpool integration, where the database, EFM, and Pgpool are installed on Rocky Linux 8 Virtual Machines in Azure. For this specific use case, Azure Load Balancer (LNB) has been used to distribute the traffic amongst all the active Pgpool Instances instead of directing the traffic using Pgpool VIP. ![Architecture diagram for EFM and Pgpool integration using Azure Load Balancer](images/EFM_PgPool_Azure.png) diff --git a/product_docs/docs/efm/3/efm_quick_start/index.mdx b/product_docs/docs/efm/3/efm_quick_start/index.mdx index 65cb920f844..6e799209816 100644 --- a/product_docs/docs/efm/3/efm_quick_start/index.mdx +++ b/product_docs/docs/efm/3/efm_quick_start/index.mdx @@ -107,18 +107,12 @@ Copy the `efm.properties` and `efm.nodes` files to the `/etc/edb/efm-3.10` direc **Step 6: Start the EFM Cluster** -On any node, start the Failover Manager agent. The agent is named `edb-efm-3.10`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or CentOS/RHEL 8.x host use the command: +On any node, start the Failover Manager agent. The agent is named `edb-efm-3.10`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/RHEL 8.x host use the command: ```text systemctl start edb-efm-3.10 ``` -On a a CentOS or RHEL 6.x host use the command: - -```text -service edb-efm-3.10 start -``` - After the agent starts, run the following command to see the status of the single-node cluster. You should see the addresses of the other nodes in the `Allowed node host` list. ```text diff --git a/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx b/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx index 1daf45bd3ba..80bf6f783cf 100644 --- a/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx +++ b/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx @@ -18,7 +18,7 @@ To request credentials that allow you to access an EnterpriseDB repository, visi -## RedHat or CentOS Host +## RedHat/CentOS/Rocky Linux Host When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter y, and press Return to continue. @@ -111,7 +111,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm310 ``` -### RHEL or CentOS 8 Host +### RHEL or Rocky Linux 8 Host 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: ```text @@ -126,7 +126,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 3. Install the EPEL repository: -- On CentOS 8 +- On Rocky Linux 8 ```text dnf -y install epel-release ``` @@ -137,7 +137,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 4. Enable the additional repositories to resolve dependencies: -- On CentOS 8 +- On Rocky Linux 8 ```text dnf config-manager --set-enabled PowerTools ``` diff --git a/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx b/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx index d577b590554..0214183045a 100644 --- a/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx +++ b/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx @@ -57,7 +57,7 @@ Job for edb-efm-3.10.service failed because the control process exited with erro If you receive this message when starting the Failover Manager service, please see the startup log (located in `/var/log/efm-3.10/startup-efm.log`) for more information. -If you are using RHEL/CentOS 7.x or RHEL/CentOS 8.x, startup information is also available with the following command: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, startup information is also available with the following command: ```text systemctl status edb-efm-3.10 diff --git a/product_docs/docs/efm/3/efm_user/05_using_efm.mdx b/product_docs/docs/efm/3/efm_user/05_using_efm.mdx index e88596331e3..76ab7be92da 100644 --- a/product_docs/docs/efm/3/efm_user/05_using_efm.mdx +++ b/product_docs/docs/efm/3/efm_user/05_using_efm.mdx @@ -36,7 +36,7 @@ By default, [some of the efm commands](07_using_efm_utility/#using_efm_utility) You can start the nodes of a Failover Manager cluster in any order. -To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/CentOS 8.x, assume superuser privileges, and invoke the command: +To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: ```text systemctl start edb-efm-3.10 @@ -71,7 +71,7 @@ You can add a node to a Failover Manager cluster at any time. When you add a nod 2. Configure the cluster members file on the new node, adding an entry for the Membership Coordinator. For more information about modifying the cluster members file, see [The Cluster Members File](04_configuring_efm/03_cluster_members/#cluster_members). -3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/CentOS 8.x, invoke the command: +3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, invoke the command: ```text systemctl start edb-efm-3.10 @@ -174,7 +174,7 @@ For more information about the efm utility, see [Using the EFM Utility](07_using When you stop an agent, Failover Manager will remove the node's address from the cluster members list on all of the running nodes of the cluster, but will not remove the address from the Failover Manager Allowed node host list. -To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/CentOS 8.x, assume superuser privileges, and invoke the command: +To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: ```text systemctl stop edb-efm-3.10 @@ -218,7 +218,7 @@ You can monitor multiple database clusters that reside on the same host by runni 1. Create a cluster properties file for each member of each cluster that defines a unique set of properties and the role of the node within the cluster. 2. Create a cluster members file for each member of each cluster that lists the members of the cluster. -3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/CentOS 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. +3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. 4. Start the services for each cluster. The examples that follow uses two database clusters (acctg and sales) running on the same node: @@ -274,14 +274,14 @@ The following parameters are used when assigning the virtual IP address to a nod This parameter value is determined by the virtual IP addresses being used and may or may not be the same for both `acctg.properties` and `sales.properties`. -After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files; this step is platform specific. If you are using RHEL/CentOS 7.x or RHEL/CentOS 8.x, see [RHEL/CentOS 7.x or RHEL/CentOS 8.x](#rhelcentos-7x-or-rhelcentos-8x). +After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files; this step is platform specific. If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x](#rhelcentos-7x-or-rhelcentos-8x). !!! Note If you are using a unit file, you must manually update the file to reflect the new service name when you upgrade Failover Manager. -### RHEL/CentOS 7.x or RHEL/CentOS 8.x +### RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x -If you are using RHEL/CentOS 7.x or RHEL/CentOS 8.x, you should copy the `edb-efm-3.10` unit file to new file with a name that is unique for each cluster. For example, if you have two clusters (named acctg and sales), the unit file names might be: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, you should copy the `edb-efm-3.10` unit file to new file with a name that is unique for each cluster. For example, if you have two clusters (named acctg and sales), the unit file names might be: ```text /usr/lib/systemd/system/efm-acctg.service diff --git a/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx b/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx index 752ce171dc1..70c5a18f0a4 100644 --- a/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx +++ b/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx @@ -23,11 +23,11 @@ The commands that control the Failover Manager service are platform-specific. -## Using the systemctl Utility on RHEL/CentOS 7.x and RHEL/CentOS 8.x +## Using the systemctl Utility on RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x -On RHEL/CentOS 7.x and RHEL/CentOS 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-3.10.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager will run a copy of the service on each node of the replication cluster. +On RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-3.10.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager will run a copy of the service on each node of the replication cluster. -Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/CentOS 8.x host: +Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x host: ```text systemctl start edb-efm-3.10 diff --git a/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx b/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx index 186bfa546c7..4eecccff627 100644 --- a/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx +++ b/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx @@ -63,7 +63,7 @@ After upgrading to Failover Manager 3.10, you can use your native package manage yum remove edb-efm39 ``` -- On RHEL or CentOS 8.x: +- On RHEL or Rocky Linux 8.x: ```text dnf remove edb-efm39 diff --git a/product_docs/docs/efm/4/03_installing_efm.mdx b/product_docs/docs/efm/4/03_installing_efm.mdx index fbaf0b5f5cf..3a11a226170 100644 --- a/product_docs/docs/efm/4/03_installing_efm.mdx +++ b/product_docs/docs/efm/4/03_installing_efm.mdx @@ -20,7 +20,7 @@ For information about the platforms and versions supported by Failover Manager, To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). -## RedHat or CentOS host +## RedHat/CentOS/Rocky Linux host When you install an RPM package that is signed by a source that isn't recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. @@ -30,7 +30,7 @@ Failover Manager must be installed by root. During the installation process, the After receiving your credentials, you must create the EnterpriseDB repository configuration file on each node of the cluster and then modify the file to enable access. -### RHEL or CentOS 8 x86-64 host +### RHEL Rocky Linux 8 x86-64 host 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -45,7 +45,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 3. Install the EPEL repository: -- On CentOS 8 +- On Rocky Linux 8 ```text dnf -y install epel-release ``` @@ -56,7 +56,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 4. Enable the additional repositories to resolve dependencies: -- On CentOS 8 +- On Rocky Linux 8 ```text dnf config-manager --set-enabled PowerTools ``` diff --git a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx index ec8546d8b1f..ac5757538c7 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx @@ -55,7 +55,7 @@ Job for edb-efm-4.4.service failed because the control process exited with error If you receive this message when starting the Failover Manager service, see the startup log `/var/log/efm-4.4/startup-efm.log` for more information. -If you are using RHEL/CentOS 7.x or RHEL/CentOS 8.x, startup information is also available with the following command: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, startup information is also available with the following command: ```text systemctl status edb-efm-4.4 diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index b62ec753b46..af7a7334502 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -34,7 +34,7 @@ By default, [some of the efm commands](07_using_efm_utility/#using_efm_utility) You can start the nodes of a Failover Manager cluster in any order. -To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/CentOS 8.x, assume superuser privileges, and invoke the command: +To start the Failover Manager cluster on RHEL/Rocky Linux 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: `systemctl start edb-efm-4.` @@ -66,7 +66,7 @@ You can add a node to a Failover Manager cluster at any time. When you add a nod 2. Configure the cluster members file on the new node, adding an entry for the membership coordinator. For more information about modifying the cluster members file, see [The cluster members file](04_configuring_efm/03_cluster_members/#cluster_members). -3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/CentOS 8.x, invoke the command: +3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, invoke the command: `systemctl start edb-efm-4.` @@ -162,7 +162,7 @@ For more information about the efm utility, see [Using the efm utility](07_using When you stop an agent, Failover Manager removes the node's address from the cluster members list on all of the running nodes of the cluster but doesn't remove the address from the Failover Manager Allowed node host list. -To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/CentOS 8.x, assume superuser privileges and invoke the command: +To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges and invoke the command: `systemctl stop edb-efm-4.` @@ -200,7 +200,7 @@ You can monitor multiple database clusters that reside on the same host by runni 1. Create a cluster properties file for each member of each cluster that defines a unique set of properties and the role of the node within the cluster. 2. Create a cluster members file for each member of each cluster that lists the members of the cluster. -3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/CentOS 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. +3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. 4. Start the services for each cluster. These examples use two database clusters (acctg and sales) running on the same node: @@ -256,14 +256,14 @@ Use the following parameters when assigning the virtual IP address to a node. If This parameter value is determined by the virtual IP addresses being used and can be the same for both `acctg.properties` and `sales.properties`. -After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/CentOS 7.x or RHEL/CentOS 8.x, see [RHEL/CentOS 7.x or RHEL/CentOS 8.x](#rhelcentos-7x-or-rhelcentos-8x). +After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x](#rhelcentos-7x-or-rhelcentos-8x). !!! Note If you're using a unit file, manually update the file to reflect the new service name when you upgrade Failover Manager. -### RHEL/CentOS 7.x or RHEL/CentOS 8.x +### RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x -If you're using RHEL/CentOS 7.x or RHEL/CentOS 8.x, copy the `edb-efm-4.` unit file to a new file with a name that is unique for each cluster. For example, if you have two clusters named acctg and sales, the unit file names might be: +If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, copy the `edb-efm-4.` unit file to a new file with a name that is unique for each cluster. For example, if you have two clusters named acctg and sales, the unit file names might be: ```text /usr/lib/systemd/system/efm-acctg.service diff --git a/product_docs/docs/efm/4/08_controlling_efm_service.mdx b/product_docs/docs/efm/4/08_controlling_efm_service.mdx index dd53bfbe82a..e87afff3dcf 100644 --- a/product_docs/docs/efm/4/08_controlling_efm_service.mdx +++ b/product_docs/docs/efm/4/08_controlling_efm_service.mdx @@ -21,11 +21,11 @@ The commands that control the Failover Manager service are platform specific. -## Using the systemctl utility on RHEL/CentOS 7.x and RHEL/CentOS 8.x +## Using the systemctl utility on RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x -On RHEL/CentOS 7.x and RHEL/CentOS 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-4..service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster. +On RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-4..service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster. -Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/CentOS 8.x host: +Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x host: `systemctl start edb-efm-4.` diff --git a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx index 176a224c371..e557344fd6f 100644 --- a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx +++ b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx @@ -70,7 +70,7 @@ After upgrading to Failover Manager 4.4, you can use your native package manager yum remove edb-efm41 ``` -- On RHEL or CentOS 8.x: +- On RHEL or Rocky Linux 8.x: ```text dnf remove edb-efm41 diff --git a/product_docs/docs/efm/4/efm_quick_start/index.mdx b/product_docs/docs/efm/4/efm_quick_start/index.mdx index c1ca6db591f..6b93ae0219a 100644 --- a/product_docs/docs/efm/4/efm_quick_start/index.mdx +++ b/product_docs/docs/efm/4/efm_quick_start/index.mdx @@ -88,18 +88,12 @@ Start the configuration process on a primary or standby node. Then, copy the con - Modify the `bind.address` property to use the node’s local address. - Set `is.witness` to `true` if the node is a witness node. If the node is a witness node, the properties relating to a local database installation are ignored. -1. Start the Failover Manager cluster. On any node, start the Failover Manager agent. The agent is named `edb-efm-4.4`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or CentOS/RHEL 8.x host, use the command: +1. Start the Failover Manager cluster. On any node, start the Failover Manager agent. The agent is named `edb-efm-4.4`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/RHEL 8.x host, use the command: ```text systemctl start edb-efm-4.4 ``` - On a CentOS or RHEL 6.x host, use the command: - - ```text - service edb-efm-4.4 start - ``` - 1. After the agent starts, run the following command to see the status of the single-node cluster. The addresses of the other nodes appear in the `Allowed node host` list. ```text From 014762bc15175a3514dda3950a78c6a4af763f3b Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 07:08:25 -0500 Subject: [PATCH 39/97] First draft of Replication Server RHEL8 Power updates --- .../04_supported_jdk_versions.mdx | 1 + .../03_installing_rpm_package.mdx | 65 ++++++++++++++++++- 2 files changed, 64 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx index 688608cf2c3..4816fa99645 100644 --- a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx @@ -10,6 +10,7 @@ The Replication Server is certified to work with the following Java platforms: | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `CentOS 7 and 8`
| Red Hat OpenJDK 8
| | `SLES 12`
| Red Hat OpenJDK 8
| +| `PPCLE RHEL 8` | - Red Hat OpenJDK 8

- Oracle JDK 8
| `PPCLE RHEL 7` | Red Hat OpenJDK 8
| | `RHEL 7 and 8`
| - Red Hat OpenJDK 8

- Oracle JDK 8
| | `Windows 2012 R2, 2016, and 2019`
| Red Hat OpenJDK 8
| diff --git a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx index 26c38829917..dbcddabfa08 100644 --- a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx @@ -36,7 +36,7 @@ The Advanced Server server libs package must be available for access by Yum when To install any of the packages, invoke the following command as the root account: -> `yum install package_name` +`yum install package_name` `package_name` is any of the packages listed under the Package Name column of the preceding table. @@ -55,7 +55,7 @@ To install only the publication server, invoke the following: !!! Note Though all Replication Server components are dependent upon and thus require installation of the server libs package, by using Yum, the dependency on the server libs is recognized when any Replication Server component is installed. Yum automatically installs the server libs package from the enabled Advanced Server repository along with your selected Replication Server RPM package. -## Installation Steps +## Installation Steps for Linux on x86-64 (amd64) The following are the steps to perform a complete Replication Server installation with all Replication Server components. @@ -250,6 +250,67 @@ Successful installation of Replication Server results in the creation of directo **Step 6:** The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the Replication Server Startup Configuration file. See [Post-Installation Host Environment](05_post_installation_host_environment/#post_installation_host_environment) for the location of this file. +## Installation Steps for Linux on IBM Power (ppc64le) +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-xdb +``` + + ## Updating an RPM Installation If you have an existing Replication Server RPM installation, you can use yum 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: From 1402309076f6669f650b96c5e0c1c9bbc3c38a81 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 08:14:13 -0500 Subject: [PATCH 40/97] tweaks --- .../docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx index dbcddabfa08..4058f1cdc19 100644 --- a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx @@ -250,7 +250,7 @@ Successful installation of Replication Server results in the creation of directo **Step 6:** The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the Replication Server Startup Configuration file. See [Post-Installation Host Environment](05_post_installation_host_environment/#post_installation_host_environment) for the location of this file. -## Installation Steps for Linux on IBM Power (ppc64le) +## Installation Steps for RHEL 8 on IBM Power (ppc64le) There are two steps to completing an installation: - Setting up the repository From c4962e10809e63e6cefd36e1648199d212520028 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 12 Jan 2022 06:00:41 -0500 Subject: [PATCH 41/97] fixed JDK version for v7 and drafted changes for 6.2 --- .../04_supported_jdk_versions.mdx | 3 +- .../03_installing_rpm_package.mdx | 2 +- .../03a_installing_rhel8_ppcle.mdx | 61 +++++++++++++++++++ .../04_supported_jdk_versions.mdx | 2 +- 4 files changed, 65 insertions(+), 3 deletions(-) create mode 100644 product_docs/docs/eprs/6.2/03_installation/03a_installing_rhel8_ppcle.mdx diff --git a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx index 1c933c5483f..1b4be726995 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx @@ -9,7 +9,8 @@ The xDB Replication Server is certified to work with the following Java platform | **Operating Systems** | **JDK Versions** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `CentOS 7 and 8`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| -| `PPCLE RHEL7` |


Red Hat OpenJDK 8

| +| `PPCLE RHEL 8` | Red Hat OpenJDK 8 | +| `PPCLE RHEL7` | Red Hat OpenJDK 8 | | `RHEL 7`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
- Oracle JDK 7
- Oracle JDK 8
| | `Windows 2012 R2, 2016, and 2019`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| | `Debian 10` |


Red Hat OpenJDK 11

| diff --git a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx index 40eaa45616e..e91adb49ea8 100644 --- a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the xDB RPM Package" +title: "Installing the xDB RPM Package on x86-64" --- diff --git a/product_docs/docs/eprs/6.2/03_installation/03a_installing_rhel8_ppcle.mdx b/product_docs/docs/eprs/6.2/03_installation/03a_installing_rhel8_ppcle.mdx new file mode 100644 index 00000000000..5dbc31fbb6e --- /dev/null +++ b/product_docs/docs/eprs/6.2/03_installation/03a_installing_rhel8_ppcle.mdx @@ -0,0 +1,61 @@ +--- +title: Installing the RHEL 8 xDB RPM Package on IBM Power (ppc64le) +--- +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-xdb +``` diff --git a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx index 4816fa99645..a958b70b1c9 100644 --- a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx @@ -10,7 +10,7 @@ The Replication Server is certified to work with the following Java platforms: | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `CentOS 7 and 8`
| Red Hat OpenJDK 8
| | `SLES 12`
| Red Hat OpenJDK 8
| -| `PPCLE RHEL 8` | - Red Hat OpenJDK 8

- Oracle JDK 8
+| `PPCLE RHEL 8` | Red Hat OpenJDK 8 | | `PPCLE RHEL 7` | Red Hat OpenJDK 8
| | `RHEL 7 and 8`
| - Red Hat OpenJDK 8

- Oracle JDK 8
| | `Windows 2012 R2, 2016, and 2019`
| Red Hat OpenJDK 8
| From bde068420d6ea284566367c8c24ad6a8abb5513c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 14:46:40 -0500 Subject: [PATCH 42/97] CentOS 8 > Rocky Linux 8 --- .../6.2/01_introduction/04_supported_jdk_versions.mdx | 4 ---- .../6.2/03_installation/03_installing_rpm_package.mdx | 2 +- .../05_post_installation_host_environment.mdx | 4 ++-- .../01_prerequisites/06_verifying_host_accessibility.mdx | 2 +- .../01_registering_subscription_server.mdx | 2 +- .../index.mdx | 2 +- .../7.0/01_introduction/04_supported_jdk_versions.mdx | 6 +----- .../7.0/03_installation/03_installing_rpm_package.mdx | 2 +- .../05_post_installation_host_environment.mdx | 4 ++-- .../01_prerequisites/06_verifying_host_accessibility.mdx | 2 +- .../01_registering_publication_server.mdx | 8 ++++---- .../01_registering_subscription_server.mdx | 2 +- .../index.mdx | 2 +- 13 files changed, 17 insertions(+), 25 deletions(-) diff --git a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx index 1b4be726995..dcaa2cb3c2c 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx @@ -15,7 +15,3 @@ The xDB Replication Server is certified to work with the following Java platform | `Windows 2012 R2, 2016, and 2019`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| | `Debian 10` |


Red Hat OpenJDK 11

| -**Certified Java Platforms** - -!!! Note - EDB Postgres Replication Server 6.2 is no longer supported on `CentOS/RHEL/OL 6.x` platforms. It is strongly recommended that EDB products running on these platforms should be migrated to a supported platform. diff --git a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx index e91adb49ea8..691f99b6d53 100644 --- a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx @@ -82,7 +82,7 @@ As the `root` account, run the following command to install this repository conf > `yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` -**On RHEL or CentOS 8:** +**On RHEL or Rocky Linux 8:** > `dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` diff --git a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx index 61fe37b6fab..34b66c37485 100644 --- a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx @@ -24,9 +24,9 @@ The following files are created that you may need during the configuration proce | `edb-repl.conf` (Linux) | `/etc` | xDB Replication Configuration file | | `edb-repl.conf` (Windows) | `XDB_HOME\etc` | xDB Replication Configuration file | | `edb-xdbpubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the publication server | -| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, CentOS 8, RHEL 8) | +| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | | `edb-xdbsubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the subscription server | -| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, CentOS 8, RHEL 8) | +| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | | `xdb_pubserver.conf` | `XDB_HOME/etc` | Publication server configuration file | | `xdb_subserver.conf` | `XDB_HOME/etc` | Subscription server configuration file | | `xdbReplicationServer-xx.config` | `XDB_HOME/etc/sysconfig` | xDB Startup Configuration file | diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index 495c4132fb0..3250512fe30 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -107,7 +107,7 @@ Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] ``` -Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: `systemctl restart network` diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index c69dd1f5ffa..e9c2a853eb0 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -13,7 +13,7 @@ It is important that you record the login information for the subscription serve !!! Note If you are using Oracle publication or subscription databases, and the subscription server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your xDB Replication Server installation, you must restart the subscription server. -**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. +**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. Use the Start or Restart link for the service named Subscription Service for xDB Replication Server. diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index 78ebdf8fbfd..e5e28584cf2 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -41,7 +41,7 @@ nullReplacementChar = ? **Step 2:** Restart the publication or subscription server. -Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: `systemctl restart edb-xdbpubserver` diff --git a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx index a958b70b1c9..9a0cf28e81b 100644 --- a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx @@ -8,7 +8,7 @@ The Replication Server is certified to work with the following Java platforms: | **Operating Systems** | **JDK Versions** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -| `CentOS 7 and 8`
| Red Hat OpenJDK 8
| +| `CentOS 7 and Rocky Linux 8`
| Red Hat OpenJDK 8
| | `SLES 12`
| Red Hat OpenJDK 8
| | `PPCLE RHEL 8` | Red Hat OpenJDK 8 | | `PPCLE RHEL 7` | Red Hat OpenJDK 8
| @@ -18,7 +18,3 @@ The Replication Server is certified to work with the following Java platforms: | `Ubuntu 18 and 20` | OpenJDK 11

| | `Debian 9` | OpenJDK 8

| -**Certified Java Platforms** - -!!! Note - Replication Server 7.0 is no longer supported on `CentOS/RHEL/OL 6.x` platforms. It is strongly recommended that EDB products running on these platforms should be migrated to a supported platform. diff --git a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx index 4058f1cdc19..2caaa478c72 100644 --- a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx @@ -76,7 +76,7 @@ As the `root` account, run the following command to install this repository conf > `yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` -**On RHEL or CentOS 8:** +**On RHEL or Rocky Linux 8:** > `dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` diff --git a/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx index a9d1017d49b..11978aebb22 100644 --- a/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx @@ -24,9 +24,9 @@ The following files are created that you may need during the configuration proce | `edb-repl.conf` (Linux) | `/etc` | EPRS Replication Configuration file | | `edb-repl.conf` (Windows) | `XDB_HOME\etc` | EPRS Replication Configuration file | | `edb-xdbpubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the publication server | -| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, CentOS 8, RHEL 8) | +| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | | `edb-xdbsubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the subscription server | -| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, CentOS 8, RHEL 8) | +| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | | `xdb_pubserver.conf` | `XDB_HOME/etc` | Publication server configuration file | | `xdb_subserver.conf` | `XDB_HOME/etc` | Subscription server configuration file | | `xdbReplicationServer-xx.config` | `XDB_HOME/etc/sysconfig` | Replication Server Startup Configuration file | diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index 44161c5d54c..85e87737f49 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -107,7 +107,7 @@ Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] ``` -Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: `systemctl restart network` diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx index e3d9e6c17df..c48a8a6d06b 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx @@ -13,9 +13,9 @@ It is important that you record the login information for the publication server !!! Note If you are using Oracle publication or subscription databases, and the publication server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, you must restart the publication server. -**For Linux only:** You can verify the publication server is running by using the `systemctl` command for CentOS 7 or RHEL 7 and CentOS or RHEL 8, and the service command for previous Linux versions. +**For Linux only:** You can verify the publication server is running by using the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux or RHEL 8, and the service command for previous Linux versions. -Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: ```text systemctl status edb-xdbpubserver @@ -29,7 +29,7 @@ service edb-xdbpubserver status If the publication server is running and you wish to restart it, use the restart option. -For CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +For CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: ```text systemctl restart edb-xdbpubserver @@ -43,7 +43,7 @@ service edb-xdbpubserver restart If the publication server is not running, use the start option. -For CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +For CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: ```text systemctl start edb-xdbpubserver diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index ac403d5ec13..40918538925 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -13,7 +13,7 @@ It is important that you record the login information for the subscription serve !!! Note If you are using Oracle publication or subscription databases, and the subscription server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, you must restart the subscription server. -**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. +**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. Use the Start or Restart link for the service named Subscription Service for Replication Server. diff --git a/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index 051489d4cfc..61fb5d1cb0a 100644 --- a/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -41,7 +41,7 @@ nullReplacementChar = ? **Step 2:** Restart the publication or subscription server. -Use the following command for CentOS 7 or RHEL 7 and CentOS 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: `systemctl restart edb-xdbpubserver` From 7cb5ebee6cb275f63f646512b28d57c20a3ebbdc Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 06:31:07 -0500 Subject: [PATCH 43/97] First draft for MKT RHEL 8 Power updates --- ...perating_systems_and_database_versions.mdx | 7 +- .../55/05_installing_mtk.mdx | 76 ++++++++++++++++++- 2 files changed, 77 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx index 20f062d1626..0cc2a4bb431 100644 --- a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx +++ b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx @@ -31,11 +31,12 @@ Contact your EnterpriseDB Account Manager or [sales@enterprisedb.com](mailto:sal ## Supported operating systems versions -- Centos or RHEL or OL 7 and 8 -- CentOS or RHEL PPCLE 7 +- RHEL 8/Centos 8/OL 8 +- RHEL 7/Centos 7/OL 7 - SLES 12 SP5 -- Debian 9 and 10 - Ubuntu 18.04 and 20 +- Debian 9 and 10 +- RHEL 7 ppc64le - Windows (64-bit), 2016, and 2019 - Mac OS X 10.12+ diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx index f4d2a700d92..a610e34a74d 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx @@ -21,7 +21,7 @@ To install Migration Toolkit, you must have credentials that allow access to the The following are the various installation methods: - [Installing Migration Toolkit on a CentOS or RHEL Host](#rpm_installation) -- [Installing Migration Toolkit on a CentOS, or RHEL 7 ppc64le Host](#rhel_centos_ppcle_installation) +- [Installing Migration Toolkit on a RHEL 7 or 8 ppc64le Host](#installing-migration-toolkit-on-a-rhel-7-or-8-ppc64le-host) - [Installing Migration Toolkit on a Debian or Ubuntu Host](#debian_or_ubuntu_installation) - [Installing Migration Toolkit on a SLES Host](#sles_installation) - [Installing Migration Toolkit on Windows](#windows_installation) @@ -191,9 +191,79 @@ yum will update the edb.repo file to enable access to the current EnterpriseDB r yum upgrade edb-migrationtoolkit ``` - +## Installing Migration Toolkit on a RHEL 7 or 8 ppc64le Host + +You can install the Migration Toolkit on the following operating systems: + +- [RHEL 8](#on-rhel-8) +- [RHEL 7](#on-rhel-7) + +### On RHEL 8 +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-migrationtoolkit +``` + + + + + +### On RHEL 7 -## Installing Migration Toolkit on a CentOS, or RHEL 7 ppc64le Host You can use an RPM package to install Migration Toolkit on a CentOS or RHEL ppc64le host. From ce68e1a33a62f33a130984f0550c10d8646ddf33 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 07:19:55 -0500 Subject: [PATCH 44/97] fixes --- .../02_supported_operating_systems_and_database_versions.mdx | 2 +- product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx index 0cc2a4bb431..da2927ff00e 100644 --- a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx +++ b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx @@ -36,7 +36,7 @@ Contact your EnterpriseDB Account Manager or [sales@enterprisedb.com](mailto:sal - SLES 12 SP5 - Ubuntu 18.04 and 20 - Debian 9 and 10 -- RHEL 7 ppc64le +- RHEL 7 and 8 ppc64le - Windows (64-bit), 2016, and 2019 - Mac OS X 10.12+ diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx index a610e34a74d..034839b3c96 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx @@ -265,9 +265,9 @@ dnf -y install edb-migrationtoolkit ### On RHEL 7 -You can use an RPM package to install Migration Toolkit on a CentOS or RHEL ppc64le host. +You can use an RPM package to install Migration Toolkit on a RHEL ppc64le host. -Before installing Migration toolkit , you must: +Before installing Migration toolkit: 1. Create the Advance Toolchain repository configuration file; assume superuser privileges and invoke the following command: From 1a92fa1194cca6c8a41f77253890082a8876f863 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 10 Jan 2022 15:17:48 -0500 Subject: [PATCH 45/97] replaced platform support info with link --- ...pported_operating_systems_and_database_versions.mdx | 8 +------- ...pported_operating_systems_and_database_versions.mdx | 10 ++-------- 2 files changed, 3 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/migration_toolkit/54/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/54/02_supported_operating_systems_and_database_versions.mdx index dd3ea3148de..692ba0eea8c 100644 --- a/product_docs/docs/migration_toolkit/54/02_supported_operating_systems_and_database_versions.mdx +++ b/product_docs/docs/migration_toolkit/54/02_supported_operating_systems_and_database_versions.mdx @@ -30,13 +30,7 @@ Please contact your EnterpriseDB Account Manager or [sales@enterprisedb.com](mai **Supported Operating Systems Versions** -- Centos or RHEL or OL 7 and 8 -- CentOS or RHEL PPCLE 7 -- SLES 12 SP5 -- Debian 9 and 10 -- Ubuntu 18.04 and 20 -- Windows (64-bit), 2016, and 2019 -- Mac OS X 10.12+ +Migration Toolkit supports installations on Linux, Windows, and MacOS platforms. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#mtk) for details. !!! Note The ojdbc7.jar can cause large data migrations to be incomplete due to a limit on records over Integer.MAX_VALUE (2147483647) while fetching from the ResultSet. To avoid this issue, we recommend upgrading to ojdbc8.jar. diff --git a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx index da2927ff00e..ce673e79be5 100644 --- a/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx +++ b/product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx @@ -31,14 +31,8 @@ Contact your EnterpriseDB Account Manager or [sales@enterprisedb.com](mailto:sal ## Supported operating systems versions -- RHEL 8/Centos 8/OL 8 -- RHEL 7/Centos 7/OL 7 -- SLES 12 SP5 -- Ubuntu 18.04 and 20 -- Debian 9 and 10 -- RHEL 7 and 8 ppc64le -- Windows (64-bit), 2016, and 2019 -- Mac OS X 10.12+ +Migration Toolkit supports installations on Linux, Windows, and MacOS platforms. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#mtk) for details. + !!! Note The ojdbc7.jar can cause large data migrations to be incomplete due to a limit on records over Integer.MAX_VALUE (2147483647) while fetching from the ResultSet. To avoid this issue, we recommend upgrading to ojdbc8.jar. From fa27b6b4573025381fe5cab906cf38ac4cfc4737 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 16:15:19 -0500 Subject: [PATCH 46/97] CentOS 8 > Rocky Linux 8 --- .../docs/migration_toolkit/54/05_installing_mtk.mdx | 10 +++++----- .../docs/migration_toolkit/55/05_installing_mtk.mdx | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx index d0bd6beaf72..039b5f38bda 100644 --- a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx @@ -23,7 +23,7 @@ To install Migration Toolkit, you must have credentials that allow access to the The following are the various installation methods: -- [Installing Migration Toolkit on a CentOS or RHEL Host](#rpm_installation) +- [Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL Host](#rpm_installation) - [Installing Migration Toolkit on a CentOS, or RHEL 7 ppc64le Host](#rhel_centos_ppcle_installation) - [Installing Migration Toolkit on a Debian or Ubuntu Host](#debian_or_ubuntu_installation) - [Installing Migration Toolkit on a SLES Host](#sles_installation) @@ -32,9 +32,9 @@ The following are the various installation methods: -## Installing Migration Toolkit on a CentOS or RHEL 7 and 8 Host +## Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL 7 and 8 Host -You can use an RPM package to install Migration Toolkit on a CentOS or RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. **Creating a Repository Configuration File** @@ -85,9 +85,9 @@ You can use an RPM package to install Migration Toolkit on a CentOS or RHEL host epel-release-latest-8.noarch.rpm ``` -4. If you are using RHEL or CentOS 8.x, you must enable an additional repository to resolve dependencies: +4. If you are using RHEL or Rocky Linux 8.x, you must enable an additional repository to resolve dependencies: -- On CentOS 8 (Powertools repo): +- On Rocky Linux 8 (Powertools repo): ```text dnf config-manager --set-enabled PowerTools diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx index 034839b3c96..a43fc6f6cbc 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx @@ -20,7 +20,7 @@ To install Migration Toolkit, you must have credentials that allow access to the The following are the various installation methods: -- [Installing Migration Toolkit on a CentOS or RHEL Host](#rpm_installation) +- [Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL Host](#rpm_installation) - [Installing Migration Toolkit on a RHEL 7 or 8 ppc64le Host](#installing-migration-toolkit-on-a-rhel-7-or-8-ppc64le-host) - [Installing Migration Toolkit on a Debian or Ubuntu Host](#debian_or_ubuntu_installation) - [Installing Migration Toolkit on a SLES Host](#sles_installation) @@ -29,9 +29,9 @@ The following are the various installation methods: -## Installing Migration Toolkit on a CentOS or RHEL 7 and 8 Host +## Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL 7 and 8 Host -You can use an RPM package to install Migration Toolkit on a CentOS or RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. **Creating a Repository Configuration File** @@ -82,9 +82,9 @@ You can use an RPM package to install Migration Toolkit on a CentOS or RHEL host epel-release-latest-8.noarch.rpm ``` -4. If you are using RHEL or CentOS 8.x, you must enable an additional repository to resolve dependencies: +4. If you are using RHEL or Rocky Linux 8.x, you must enable an additional repository to resolve dependencies: -- On CentOS 8 (Powertools repo): +- On Rocky Linux 8 (Powertools repo): ```text dnf config-manager --set-enabled PowerTools From cdd9c8cfcc6eb8b1b6e5781c89b77389251f5bb2 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 20 Jan 2022 16:23:11 -0500 Subject: [PATCH 47/97] CentOS 8 > Rocky Linux 8 (latest version onle\y) --- .../mysql_data_adapter/2.7.0/02_requirements_overview.mdx | 3 ++- .../2.7.0/04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.7.0/05_updating_the_mysql_data_adapter.mdx | 2 +- .../2.7.0/12_uninstalling_the_mysql_data_adapter.mdx | 2 +- 4 files changed, 6 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx index 76e502543e2..b4d76583c8b 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx @@ -13,7 +13,8 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. **Linux x86-64** - RHEL 8.x/7.x -- CentOS 8.x/7.x +- CentOS 7.x +- Rocky Linux 8.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx index ad0d3572656..01dc6088998 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -311,7 +311,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx index e0730522270..cf79c1a23ba 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx @@ -14,7 +14,7 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can ```text sudo yum -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` - - On RHEL or CentOS 8: + - On RHEL or Rocky Linux 8: ```text sudo dnf -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx index 1757e93c803..cd52d6c158b 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ Where `xx` is the server version number, and `x` is the supported release versio `yum remove edb-as-mysql5_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mysql8_fdw` From 80f7d16984512ed1c80a1a701edd7ab9fcb60126 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 13:10:50 -0500 Subject: [PATCH 48/97] first draft of Mongo FDW updates for RHEL 8 Power --- .../5.3.0/02_requirements_overview.mdx | 14 +- .../04_installing_the_mongo_data_adapter.mdx | 241 ++++++++++++------ 2 files changed, 164 insertions(+), 91 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx index 6078203da1c..9e129b4259d 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx @@ -12,12 +12,12 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** -> - RHEL 8.x/7.x -> - CentOS 8.x/7.x -> - OL 8.x/7.x -> - Ubuntu 20.04/18.04 LTS -> - Debian 10.x/9.x + - RHEL 8/CentOS 8/OL 8 + - RHEL 7/CentOS 7/OL 7 + - Ubuntu 20.04/18.04 LTS + - Debian 10.x/9.x -**Linux on IBM Power8/9 (LE)** +**Linux on IBM Power8/9 (ppc64le)** -> - RHEL 7.x + - RHEL 8 + - RHEL 7/CentOS 7 diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index 5f94de4e76f..d4813d2fccd 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -5,74 +5,63 @@ title: "Installing the MongoDB Foreign Data Wrapper" -The MongoDB Foreign Data Wrapper can be installed with an RPM package. During the installation process, the installer will satisfy software prerequisites. If yum encounters a dependency that it cannot resolve, it will provide a list of the required dependencies that you must manually resolve. -## Installing the MongoDB Foreign Data Wrapper using an RPM Package +## Installing on Linux x86-64 (amd64) -You can install the MongoDB Foreign Data Wrapper using an RPM package on the following platforms: +You can install the MongoDB Foreign Data Wrapper on the following operating systems: -- [RHEL or CentOS 7 PPCLE](#rhel_centos7_PPCLE) -- [RHEL 7](#rhel7) - [RHEL 8](#rhel8) -- [CentOS 7](#centos7) +- [RHEL 7](#rhel7) - [CentOS 8](#centos8) +- [CentOS 7](#centos7) +- [Ubuntu/Debian](#on-debian-or-ubuntu) - -### On RHEL or CentOS 7 PPCLE -1. Use the following command to create a configuration file and install Advance Toolchain: - ```text - rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b - cat > /etc/yum.repos.d/advance-toolchain.repo < -2. Install the EDB repository: +### On RHEL 8 +1. To create the repository configuration file, assume superuser privileges, and invoke the following command: + ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -3. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: +2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: ```text sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` -4. Install the EPEL repository: +3. Install the EPEL repository: ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: +4. Enable the additional repositories to resolve dependencies: ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` -6. Install the selected package: +5. Disable the built-in PostgreSQL module: + ```text + dnf -qy module disable postgresql + ``` +6. Install the selected package: + ```text dnf install edb-as-mongo_fdw ``` - where `xx` is the server version number. - + where `xx` is the server version number. @@ -113,9 +102,12 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol - -### On RHEL 8 + + + +### On CentOS 8 + 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: @@ -132,13 +124,13 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol 3. Install the EPEL repository: ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf -y install epel-release ``` 4. Enable the additional repositories to resolve dependencies: ```text - ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + dnf config-manager --set-enabled PowerTools ``` 5. Disable the built-in PostgreSQL module: @@ -154,8 +146,6 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol where `xx` is the server version number. - - ### On CentOS 7 @@ -186,51 +176,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol where `xx` is the server version number. - - - -### On CentOS 8 - - -1. To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -2. Replace ‘USERNAME:PASSWORD’ below with your username and password for the EDB repositories: - - ```text - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo - ``` - -3. Install the EPEL repository: - - ```text - dnf -y install epel-release - ``` - -4. Enable the additional repositories to resolve dependencies: - - ```text - dnf config-manager --set-enabled PowerTools - ``` - -5. Disable the built-in PostgreSQL module: - - ```text - dnf -qy module disable postgresql - ``` -6. Install the selected package: - - ```text - dnf install edb-as-mongo_fdw - ``` - - where `xx` is the server version number. - - -## Installing the MongoDB Foreign Data Wrapper on a Debian or Ubuntu Host +### On Ubuntu/Debian To install the MongoDB Foreign Data Wrapper on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit the [EDB website](https://www.enterprisedb.com/repository-access-request/). @@ -289,3 +235,130 @@ The following steps will walk you through using the EDB apt repository to instal ``` where `xx` is the server version number. + +## Installing on IBM Power (ppc64le) + +You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): + + - [RHEL 8](/#on-rhel-8-1) + - [RHEL 7/CentOS 7](#rhel_centos7_PPCLE) + +### On RHEL 8 +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as-mongo_fdw +``` + +Where `xx` is the server version number. + + + + + + + +### On RHEL 7/CentOS 7 + +1. Use the following command to create a configuration file and install Advance Toolchain: + + ```text + rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + + cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +4. Install the EPEL repository: + + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ``` + +5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: + + ```text + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` + +6. Install the selected package: + + ```text + dnf install edb-as-mongo_fdw + ``` + + where `xx` is the server version number. \ No newline at end of file From 6a9f5adc2a6f007ac34ac46f694ebcadbf37129d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 13:25:18 -0500 Subject: [PATCH 49/97] removed CentOS 7 Power per Kelly --- .../mongo_data_adapter/5.3.0/02_requirements_overview.mdx | 2 +- .../5.3.0/04_installing_the_mongo_data_adapter.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx index 9e129b4259d..3ef4f5b31d4 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx @@ -20,4 +20,4 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux on IBM Power8/9 (ppc64le)** - RHEL 8 - - RHEL 7/CentOS 7 + - RHEL 7 diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index d4813d2fccd..b2b691150f5 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -241,7 +241,7 @@ The following steps will walk you through using the EDB apt repository to instal You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): - [RHEL 8](/#on-rhel-8-1) - - [RHEL 7/CentOS 7](#rhel_centos7_PPCLE) + - [RHEL 7](#rhel_centos7_PPCLE) ### On RHEL 8 There are two steps to completing an installation: @@ -311,7 +311,7 @@ Where `xx` is the server version number. -### On RHEL 7/CentOS 7 +### On RHEL 7 1. Use the following command to create a configuration file and install Advance Toolchain: From 0b02476b26dae32cc46c3e107b26a3881ee626b6 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 14:31:43 -0500 Subject: [PATCH 50/97] tweaks --- .../docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx | 2 +- .../5.3.0/04_installing_the_mongo_data_adapter.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx index 3ef4f5b31d4..6322c7516dc 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx @@ -17,7 +17,7 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x -**Linux on IBM Power8/9 (ppc64le)** +**Linux on IBM Power (ppc64le)** - RHEL 8 - RHEL 7 diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index b2b691150f5..c3dc3b8c0e5 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -303,7 +303,7 @@ sudo su - dnf -y install edb-as-mongo_fdw ``` -Where `xx` is the server version number. +where `xx` is the server version number. From f9026496217887eb6d3c58780eeba9b7176d0e75 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 15:08:57 -0500 Subject: [PATCH 51/97] fixed jump link and tweaks --- .../5.3.0/04_installing_the_mongo_data_adapter.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index c3dc3b8c0e5..4190de6c675 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -240,7 +240,7 @@ The following steps will walk you through using the EDB apt repository to instal You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): - - [RHEL 8](/#on-rhel-8-1) + - [RHEL 8](#on-rhel-8-1) - [RHEL 7](#rhel_centos7_PPCLE) ### On RHEL 8 @@ -275,7 +275,7 @@ sudo su - sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo ``` - Where `USERNAME:PASSWORD` is the username and password available from your + where `USERNAME:PASSWORD` is the username and password available from your [EDB account](https://www.enterprisedb.com/user). 1. Install the EPEL repository and refresh the cache: From 0f02b1965064aa4664f0ebd33849af7fec0d298d Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 21 Jan 2022 06:27:34 -0500 Subject: [PATCH 52/97] CentOS 8 > Rocky Linux 8 --- .../5.2.8/02_requirements_overview.mdx | 13 +++++++------ .../5.2.8/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.8/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../11_uninstalling_the_mongo_data_adapter.mdx | 2 +- .../5.2.9/02_requirements_overview.mdx | 13 +++++++------ .../5.2.9/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.9/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../11_uninstalling_the_mongo_data_adapter.mdx | 2 +- .../5.3.0/02_requirements_overview.mdx | 2 +- .../5.3.0/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.3.0/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../11_uninstalling_the_mongo_data_adapter.mdx | 2 +- 12 files changed, 30 insertions(+), 28 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx index 7a3bc310c26..72393e6ea2a 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx @@ -15,12 +15,13 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** -> - RHEL 8.x/7.x -> - CentOS 8.x/7.x -> - OL 8.x/7.x -> - Ubuntu 20.04/18.04 LTS -> - Debian 10.x/9.x + - RHEL 8.x/7.x + - Rocky Linux 8.x + - CentOS 7.x + - OL 8.x/7.x + - Ubuntu 20.04/18.04 LTS + - Debian 10.x/9.x **Linux on IBM Power8/9 (LE)** -> - RHEL 7.x + - RHEL 7.x diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx index 435cced7de5..0868ce70219 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the MongoDB Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx index aa29e7403f9..b39260285ae 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca > `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: > `dnf upgrade edb-repo` @@ -22,7 +22,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r > `yum upgrade edb-as-mongo_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: > `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx index 8313284a962..c18c4d250c5 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx index 6078203da1c..ff10ce55df4 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx @@ -12,12 +12,13 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** -> - RHEL 8.x/7.x -> - CentOS 8.x/7.x -> - OL 8.x/7.x -> - Ubuntu 20.04/18.04 LTS -> - Debian 10.x/9.x + - RHEL 8.x/7.x + - Rocky Linux 8.x + - CentOS 7.x + - OL 8.x/7.x + - Ubuntu 20.04/18.04 LTS + - Debian 10.x/9.x **Linux on IBM Power8/9 (LE)** -> - RHEL 7.x + - RHEL 7.x diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx index 5f94de4e76f..372140873f0 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx @@ -17,7 +17,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -189,7 +189,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol -### On CentOS 8 +### On Rocky Linux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx index 63a59b8c5ef..6f1898befab 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx @@ -16,7 +16,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -30,7 +30,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-as-mongo_fdw edb-libmongoc-libs` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx index d0d4f05040a..e5fa5c65ef4 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx index 6322c7516dc..22b7f9c354d 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx @@ -12,7 +12,7 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - - RHEL 8/CentOS 8/OL 8 + - RHEL 8/Rocky Linux 8/OL 8 - RHEL 7/CentOS 7/OL 7 - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index 4190de6c675..6b1e631b5df 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -14,7 +14,7 @@ You can install the MongoDB Foreign Data Wrapper on the following operating syst - [RHEL 8](#rhel8) - [RHEL 7](#rhel7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) - [CentOS 7](#centos7) - [Ubuntu/Debian](#on-debian-or-ubuntu) @@ -106,7 +106,7 @@ You can install the MongoDB Foreign Data Wrapper on the following operating syst -### On CentOS 8 +### On Rocky Linux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx index 6030c7a2d7d..0b5808d3a66 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx @@ -16,7 +16,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -34,7 +34,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number and `yy` is Advance Toolchain major version number. For EDB Postgres Advanced Server versions 9.6 to 11, `yy` must be 10 and for EDB Postgres Advanced Server version 12 and later, `yy` must be 11. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx index d0d4f05040a..e5fa5c65ef4 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mongo_fdw` From 1b8c9caf5b9080ff881bcf8d89e66c3bb3f1a8a7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 21 Jan 2022 08:37:51 -0500 Subject: [PATCH 53/97] CentOS 8 > Rocky 8 --- .../hadoop_data_adapter/2.0.7/02_requirements_overview.mdx | 3 ++- .../2.0.7/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.7/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- .../hadoop_data_adapter/2.0.8/02_requirements_overview.mdx | 3 ++- .../2.0.8/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.8/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- .../hadoop_data_adapter/2.1.0/02_requirements_overview.mdx | 2 +- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.1.0/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- 12 files changed, 20 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx index 02d660f0868..179e5089bab 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx @@ -16,7 +16,8 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x and 7.x - - CentOS 8.x and 7.x + - Rocky Linux 8.x + - CentOS 7.x - OL 8.x and 7.x - Ubuntu 20.04 and 18.04 LTS - Debian 10.x and 9.x diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx index 658c10d97bb..c9391508451 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the Hadoop Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx index 17040838963..94ec393e182 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can > `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: > `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: > `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx index 2ce7ab1ca46..090fd306dc4 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx index 13360808b72..820634fc433 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx @@ -13,7 +13,8 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x and 7.x - - CentOS 8.x and 7.x + - Rocky Linux 8.x + - CentOS 7.x - OL 8.x and 7.x - Ubuntu 20.04 and 18.04 LTS - Debian 10.x and 9.x diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx index 9ec328fdbf5..a1785889167 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -190,7 +190,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll -### On CentOS 8 +### On Rocky Linux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx index 400a0b649a0..836367cb076 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx index 5264a389c50..8644c6dac94 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx index a949e4ed2fa..ee9ad75891d 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx @@ -12,7 +12,7 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - - RHEL 8/CentOS 8/OL 8 + - RHEL 8/Rocky Linux 8/OL 8 - RHEL 7/CentOS 7/OL 7 - Ubuntu 20.04 and 18.04 LTS - Debian 10.x and 9.x diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index d6ac92250f4..790a6fcb817 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -13,7 +13,7 @@ You can install the Hadoop Foreign Data Wrapper on the following operating syste - [RHEL 8](#rhel8) - [RHEL 7](#rhel7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) - [CentOS 7](#centos7) - [Ubuntu/Debian](#on-debian-or-ubuntu) @@ -98,7 +98,7 @@ You can install the Hadoop Foreign Data Wrapper on the following operating syste -### On CentOS 8 +### On Rocky Linux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx index 400a0b649a0..836367cb076 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx index 5264a389c50..8644c6dac94 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-hdfs_fdw` From ad19bac1bd035d99bebd99db61384874267cca32 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 11:05:36 -0500 Subject: [PATCH 54/97] CentOS 8 > Rocky Linux 8 for older versions --- .../jdbc_connector/42.2.19.1/02_requirements_overview.mdx | 4 +++- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx index 4ecbc237475..9fdd3c41619 100644 --- a/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx @@ -13,7 +13,9 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: -- Red Hat Enterprise Linux and CentOS (x86_64) 7.x and 8.x + +- RHEL and CentOS (x86_64) 7.x +- RHEL and Rocky Linux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 80f57eecb3f..617831ed54d 100644 --- a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -10,7 +10,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -204,7 +204,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On CentOS 8 +## On Rocky Linux 8 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -274,7 +274,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` From 2e607066b70cef1e35ad21fd9f738c663eb60136 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 11:08:03 -0500 Subject: [PATCH 55/97] one more older version --- .../jdbc_connector/42.2.12.3/02_requirements_overview.mdx | 3 ++- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx index effb8f1fce4..df528e61e8d 100644 --- a/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx @@ -17,7 +17,8 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: -- Red Hat Enterprise Linux and CentOS (x86_64) 7.x and 8.x +- RHEL and CentOS (x86_64) 7.x +- RHEL and Rocky Linux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 18380edb6bd..a0df158d553 100644 --- a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -14,7 +14,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -208,7 +208,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On CentOS 8 +## On Rocky Linux 8 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -278,7 +278,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` From 5b504082d5c78c5ce0cbb2feeae5b0655880e7d1 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 11:30:26 -0500 Subject: [PATCH 56/97] updated older versions --- .../ocl_connector/12.1.2.1/02_supported_platforms.mdx | 3 ++- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- .../ocl_connector/13.1.4.2/02_supported_platforms.mdx | 5 +++-- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- 4 files changed, 13 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx index 54bb3d4781c..0d8c04e51d6 100644 --- a/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx @@ -10,7 +10,8 @@ legacyRedirectsGenerated: The EDB OCL Connector is certified with Advanced Server version 9.5 and above. The EDB OCL Connector native packages are supported on the following 64-bit platforms: - Red Hat Enterprise Linux (x86_64) 7.x and 8.x -- CentOS (x86_64) 7.x and 8.x +- CentOS (x86_64) 7.x +- Rocky Linux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index 5fabcd3b768..ae4f9f3a321 100644 --- a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -16,7 +16,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -288,7 +288,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -300,7 +300,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-oci` diff --git a/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx index 1c14962e31e..6591e801959 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx @@ -11,8 +11,9 @@ legacyRedirectsGenerated: The EDB OCL Connector is certified with Advanced Server version 9.6 and above. The EDB OCL Connector native packages are supported on the following 64-bit platforms: -- Red Hat Enterprise Linux (x86_64) 7.x and 8.x -- CentOS (x86_64) 7.x and 8.x +- RHEL (x86_64) 7.x and 8.x +- CentOS (x86_64) 7.x +- Rocky Linux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index ec483b074e0..15aa8fc93a4 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -18,7 +18,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -218,7 +218,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -290,7 +290,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -302,7 +302,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-oci` From fd8f05a5a53d13ad9c458d7d415f4194c6d5b4ee Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 11:38:19 -0500 Subject: [PATCH 57/97] updated older versions --- .../12.0.0.2/02_requirements_overview.mdx | 5 ++--- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 10 +++++----- .../12.2.0.2/02_requirements_overview.mdx | 3 ++- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- .../13.0.0.1/02_requirements_overview.mdx | 3 ++- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- .../13.1.0.1/02_requirements_overview.mdx | 3 ++- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- 8 files changed, 25 insertions(+), 23 deletions(-) diff --git a/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx index 7bdba0bb1d3..f14f2276a6b 100644 --- a/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx @@ -18,15 +18,14 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- CentOS (x86_64) 8.x and 7.x +- Rocky Linux (x86_64) 8.x +- CentOS (x86_64) 7.x - OL Linux 7.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x - Debian 9.x - Ubuntu 18.04 LTS -!!! Note - EDB ODBC Connector, version 12.00.0000.02 is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform The EDB ODBC Connector graphical installers are supported on the following Windows platforms: diff --git a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 6ef4ba92868..8e2f4a03ddd 100644 --- a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -22,7 +22,7 @@ Install the epel-release package: yum -y install https://dl.fedoraproject.org/pub/epel/ epel-release-latest-7.noarch.rpm ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install https://dl.fedoraproject.org/pub/epel/ epel-release-latest-7.noarch.rpm @@ -51,7 +51,7 @@ To create the repository configuration file, assume superuser privileges, and in yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -85,7 +85,7 @@ yum install edb-odbc yum install edb-odbc-devel ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf install edb-odbc @@ -109,7 +109,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or yum upgrade edb-repo ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-repo @@ -125,7 +125,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r yum upgrade edb-odbc-devel ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-odbc diff --git a/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx index cecd5d751f3..60aa4787390 100644 --- a/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx @@ -18,7 +18,8 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- CentOS (x86_64) 8.x and 7.x +- Rocky Linux (x86_64) 8.x +- CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 8e3ac848b9b..b8449c4fd1e 100644 --- a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -16,7 +16,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -288,7 +288,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -300,7 +300,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-odbc` diff --git a/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx index 47c38d68fb9..2278fe9f640 100644 --- a/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx @@ -14,7 +14,8 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- CentOS (x86_64) 8.x and 7.x +- Rocky Linux (x86_64) 8.x +- CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx index cebeb3dab17..bfc911896cf 100644 --- a/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -13,7 +13,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -294,7 +294,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -366,7 +366,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -378,7 +378,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-odbc` diff --git a/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx index 47c38d68fb9..2278fe9f640 100644 --- a/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx @@ -14,7 +14,8 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- CentOS (x86_64) 8.x and 7.x +- Rocky Linux (x86_64) 8.x +- CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx index cebeb3dab17..bfc911896cf 100644 --- a/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -13,7 +13,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -294,7 +294,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -366,7 +366,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-repo` @@ -378,7 +378,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf upgrade edb-odbc` From 1b021437d85f65d8d1387e8cc36178f18006b290 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 13:00:06 -0500 Subject: [PATCH 58/97] CentOS 8 to Rocky Linux 8 --- .../bart/2.5/bart_inst/02_installing_bart.mdx | 18 +++++++++--------- .../2.5/bart_inst/05_uninstalling_bart.mdx | 6 +++--- product_docs/docs/bart/2.5/bart_inst/index.mdx | 4 ---- product_docs/docs/bart/2.5/bart_qs_8/index.mdx | 10 +++++----- .../bart/2.6/bart_inst/02_installing_bart.mdx | 16 ++++++++-------- .../2.6/bart_inst/05_uninstalling_bart.mdx | 6 +++--- product_docs/docs/bart/2.6/bart_qs_8/index.mdx | 8 ++++---- ...talling_slony_on_a_linux_or_centos_host.mdx | 16 ++++++++-------- .../slony/2.2.10/01_installation/index.mdx | 2 +- .../2.2.10/02_configuration_and_usage.mdx | 2 +- .../docs/slony/2.2.10/04_uninstallation.mdx | 4 ++-- 11 files changed, 44 insertions(+), 48 deletions(-) diff --git a/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx b/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx index ab6f2ba8571..2b345a5564b 100644 --- a/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx +++ b/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: This section will walk you through performing a fresh installation of BART on a host. Installation instructions are organized into the following platform/installer specific sections: -- [Installing BART on a CentOS Host](#installing-bart-on-a-centos-host) +- [Installing BART on a CentOS/Rocky Linux Host](#installing-bart-on-a-centos-host) - [Installing BART on a RHEL Host](#installing-bart-on-a-rhel-host) - [Installing BART on a RHEL/CentOS 7 PPCLE Host](#installing-bart-on-a-rhelcentos-7-ppcle-host) - [Installing BART on a Debian or Ubuntu Host](#installing-bart-on-a-debian-or-ubuntu-host) @@ -19,9 +19,9 @@ This section will walk you through performing a fresh installation of BART on a !!! Note If you are using the pdf version of this document, using the cut/paste command to copy may result in extra spaces or carriage returns in the pasted command. If a command fails, check the command carefully for additional characters. -## Installing BART on a CentOS Host +## Installing BART on a CentOS/Rocky Linux Host -The following section demonstrates installing BART on a CentOS host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. +The following section demonstrates installing BART on a CentOS/Rocky Linux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. 1. To install the repository configuration, assume superuser privileges and invoke one of the following platform-specific commands: @@ -31,7 +31,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -53,19 +53,19 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. For CentOS 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` -5. For CentOS 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -79,7 +79,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum install edb-as-server-client ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf install edb-as-server-client @@ -95,7 +95,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install edb-bart-2.5.9 ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install edb-bart-2.5.9 diff --git a/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx b/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx index 4a8be5ddbc2..dfacde7fed1 100644 --- a/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx +++ b/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx @@ -12,9 +12,9 @@ legacyRedirectsGenerated: This section walks you through uninstalling BART. -## Uninstalling BART on a RHEL/CentOS Host +## Uninstalling BART on a RHEL/CentOS/Rocky Linux Host -To uninstall BART on a RHEL/CentOS host, assume the identity of the `root` user and invoke the following command: +To uninstall BART on a RHEL/CentOS/Rocky Linux host, assume the identity of the `root` user and invoke the following command: On RHEL/CentOS 7: @@ -22,7 +22,7 @@ On RHEL/CentOS 7: yum remove edb-bart ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf remove edb-bart diff --git a/product_docs/docs/bart/2.5/bart_inst/index.mdx b/product_docs/docs/bart/2.5/bart_inst/index.mdx index 14c8002cc8f..025e4d9d669 100644 --- a/product_docs/docs/bart/2.5/bart_inst/index.mdx +++ b/product_docs/docs/bart/2.5/bart_inst/index.mdx @@ -35,10 +35,6 @@ This guide provides information about how to install and configure the EDB Backu - To view a complete list of platforms that EDB supports, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility). - !!! Note - - BART 2.5 is no longer supported on CentOS/RHEL/OL 6.x platforms. It is strongly recommended that EDB products running on these platforms be migrated to a supported platform. - - BART supports the following database versions: - Advanced Server versions 9.6, 10, 11, and 12. diff --git a/product_docs/docs/bart/2.5/bart_qs_8/index.mdx b/product_docs/docs/bart/2.5/bart_qs_8/index.mdx index dff3f88d024..be21d871cc2 100644 --- a/product_docs/docs/bart/2.5/bart_qs_8/index.mdx +++ b/product_docs/docs/bart/2.5/bart_qs_8/index.mdx @@ -1,5 +1,5 @@ --- -title: "Quick Start Guide for RHEL/CentOS 8" +title: "Quick Start Guide for RHEL/Rocky Linux 8" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -11,7 +11,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-backup-and-recovery-tool/quick-start/quick-start-guide-for-rhelcentos-8/2.5.7/genindex.html" --- -This tutorial demonstrates using the `dnf` command to install and configure the EDB Backup and Recovery Tool (BART) 2.5 on a CentOS 8 host with minimal configuration settings.  The tutorial assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. +This tutorial demonstrates using the `dnf` command to install and configure the EDB Backup and Recovery Tool (BART) 2.5 on a Rocky Linux 8 host with minimal configuration settings.  The tutorial assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. For detailed information about BART installation and configuration, see the *BART Installation and Upgrade Guide* available at the [EDB website](/bart/latest/bart_inst/). @@ -22,7 +22,7 @@ For detailed information about BART installation and configuration, see the *BAR **Installing BART** -The following steps describe installing BART on CentOS 8.x OS. +The following steps describe installing BART on Rocky Linux 8.x OS. 1. Assume superuser privileges and use `dnf` to create the repository configuration file: @@ -73,7 +73,7 @@ The following steps describe installing BART on CentOS 8.x OS. ``` !!! Note - The BART host server is not required to have an Advanced Server or PostgreSQL installation, but must include a copy of the Postgres `libpq` library, the `pg_basebackup` utility program, and Boost Libraries 1.66 version for CentOS 8. + The BART host server is not required to have an Advanced Server or PostgreSQL installation, but must include a copy of the Postgres `libpq` library, the `pg_basebackup` utility program, and Boost Libraries 1.66 version for Rocky Linux 8. 6. If you do not already have the `pg_basebackup` program installed on the BART host, you can use the following command to install a limited number of files that include the `pg_basebackup` program: @@ -194,7 +194,7 @@ The following table describes only mandatory parameters: **Creating a Passwordless Connection** -The following example enables SSH/SCP access on a CentOS 8.x host; similar (platform-specific) steps will apply to other platforms/versions. You must create a passwordless connection between the BART host (SSH/SCP client) and the database server (target SSH/SCP server), as well as a passwordless connection between the database server (SSH/SCP client) and the BART host (target SSH/SCP server). +The following example enables SSH/SCP access on a Rocky Linux 8.x host; similar (platform-specific) steps will apply to other platforms/versions. You must create a passwordless connection between the BART host (SSH/SCP client) and the database server (target SSH/SCP server), as well as a passwordless connection between the database server (SSH/SCP client) and the BART host (target SSH/SCP server). 1. Log in as the user account on the BART host that will be initiating the SSH or SCP connection and navigate to the user account’s home directory and check for an existing `.ssh` subdirectory. If the `.ssh` directory does not exist, create one with the required privileges. diff --git a/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx b/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx index c1f3087d6c6..5b6c9be4a5a 100644 --- a/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx +++ b/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: This section will walk you through performing a fresh installation of BART on a host. Installation instructions are organized into the following platform/installer specific sections: -- [Installing BART on a CentOS](#installing-bart-on-a-centos-host) +- [Installing BART on a CentOS/Rocky Linux Host](#installing-bart-on-a-centos-host) - [Installing BART on a RHEL Host](#installing-bart-on-a-rhel-host) - [Installing BART on a CentOS or RHEL Host](#installing-bart-on-a-rhelcentos-7-ppcle-host) - [Installing BART on a Debian or Ubuntu Host](#installing-bart-on-a-debian-or-ubuntu-host) @@ -17,9 +17,9 @@ This section will walk you through performing a fresh installation of BART on a !!! Note If you are using the pdf version of this document, using cut/paste to copy command may result in extra spaces or carriage returns in the pasted command. If a command fails, check the command carefully for additional characters. -## Installing BART on a CentOS Host +## Installing BART on a CentOS/Rocky Linux Host -The following section demonstrates installing BART on a CentOS host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. +The following section demonstrates installing BART on a CentOS/Rocky Linux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. 1. To install the repository configuration, assume superuser privileges and invoke one of the following platform-specific commands: @@ -29,7 +29,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -51,7 +51,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release @@ -63,7 +63,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM dnf config-manager --set-enabled PowerTools ``` -5. For CentOS 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -77,7 +77,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum install edb-as-server-client ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf install edb-as-server-client @@ -93,7 +93,7 @@ The following section demonstrates installing BART on a CentOS host using an RPM yum -y install edb-bart ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install edb-bart diff --git a/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx b/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx index 2a39540b89a..4fecf6b9d84 100644 --- a/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx +++ b/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx @@ -10,9 +10,9 @@ legacyRedirectsGenerated: This section walks you through uninstalling BART. -## Uninstalling BART on a RHEL/CentOS Host +## Uninstalling BART on a RHEL/CentOS/Rocky Linux Host -To uninstall BART on a RHEL/CentOS host, assume the identity of the `root` user and invoke the following command: +To uninstall BART on a RHEL/CentOS/Rocky Linux host, assume the identity of the `root` user and invoke the following command: On RHEL/CentOS 7: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum remove edb-bart ``` -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf remove edb-bart diff --git a/product_docs/docs/bart/2.6/bart_qs_8/index.mdx b/product_docs/docs/bart/2.6/bart_qs_8/index.mdx index 4fe8f78604e..0d2d06a4cd1 100644 --- a/product_docs/docs/bart/2.6/bart_qs_8/index.mdx +++ b/product_docs/docs/bart/2.6/bart_qs_8/index.mdx @@ -1,5 +1,5 @@ --- -title: "Quick Start Guide for RHEL/CentOS 8" +title: "Quick Start Guide for RHEL/Rocky Linux 8" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-backup-and-recovery-tool/quick-start/quick-start-guide-for-rhelcentos-8/2.6/index.html" @@ -8,7 +8,7 @@ legacyRedirectsGenerated: - "/edb-docs/d/edb-backup-and-recovery-tool/quick-start/quick-start-guide-for-rhelcentos-8/2.6.1/index.html" --- -This tutorial demonstrates using the `dnf` command to install and configure the EDB Backup and Recovery Tool (BART) 2.6 on a CentOS 8 host with minimal configuration settings.  The tutorial assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. +This tutorial demonstrates using the `dnf` command to install and configure the EDB Backup and Recovery Tool (BART) 2.6 on a Rocky Linux 8 host with minimal configuration settings.  The tutorial assumes that the user has some knowledge of installation and system administration procedures and has administrative privileges on the host. For detailed information about BART installation and configuration, see the *BART Installation and Upgrade Guide* available at the [EDB website](/bart/latest/bart_inst/). @@ -19,7 +19,7 @@ For detailed information about BART installation and configuration, see the *BAR **Installing BART** -The following steps describe installing BART on CentOS 8.x OS. +The following steps describe installing BART on Rocky Linux 8.x OS. 1. Assume superuser privileges and use `dnf` to create the repository configuration file: @@ -70,7 +70,7 @@ The following steps describe installing BART on CentOS 8.x OS. ``` !!! Note - The BART host server is not required to have an Advanced Server or PostgreSQL installation, but must include a copy of the Postgres `libpq` library, the `pg_basebackup` utility program, and Boost Libraries 1.66 version for CentOS 8. + The BART host server is not required to have an Advanced Server or PostgreSQL installation, but must include a copy of the Postgres `libpq` library, the `pg_basebackup` utility program, and Boost Libraries 1.66 version for Rocky Linux 8. 6. If you do not already have the `pg_basebackup` program installed on the BART host, you can use the following command to install a limited number of files that include the `pg_basebackup` program: diff --git a/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx b/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx index d4be604054e..1155492345b 100644 --- a/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx +++ b/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Slony Replication on a CentOS Host" +title: "Installing Slony Replication on a CentOS/Rocky Linux Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -20,7 +20,7 @@ Follow the steps given below to install Slony Replication: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -40,19 +40,19 @@ Follow the steps given below to install Slony Replication: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install epel-release ``` -4. For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +4. For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` -5. For CentOS 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -68,7 +68,7 @@ Follow the steps given below to install Slony Replication: Where <xx> is the Slony version you want to install. - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install edb-as-slony-replication @@ -76,7 +76,7 @@ Follow the steps given below to install Slony Replication: Where <xx> is the Slony version you want to install. - To install Slony 2.2.10 on CentOS 8 for EDB Postgres Advanced Server version 13, the command is: + To install Slony 2.2.10 on Rocky Linux 8 for EDB Postgres Advanced Server version 13, the command is: ```text dnf -y install edb-as13-slony-replication @@ -174,7 +174,7 @@ Follow the steps given below to install Slony Replication: | **Platform** | **Service File Path** | **Installation File Path** | **Configuration File Path** | | --------------------- | ------------------------------------------------------------ | -------------------------- | --------------------------------------------------------------------------------------------- | -| `RHEL/CentOS 7 and 8` | `/usr/lib/systemd/system/edb-slony-replication-.service` | `/usr/edb/as` | The configuration file `slony-replication.ini` is located in `/etc/edb/slony-replication` | +| `RHEL/CentOS 7 and RHEL/Rocky Linux 8` | `/usr/lib/systemd/system/edb-slony-replication-.service` | `/usr/edb/as` | The configuration file `slony-replication.ini` is located in `/etc/edb/slony-replication` | In the above table, <xx> represents the EDB Postgres Advanced Server version. diff --git a/product_docs/docs/slony/2.2.10/01_installation/index.mdx b/product_docs/docs/slony/2.2.10/01_installation/index.mdx index 826dcbd6041..7e590a2558c 100644 --- a/product_docs/docs/slony/2.2.10/01_installation/index.mdx +++ b/product_docs/docs/slony/2.2.10/01_installation/index.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -This section walks you through installing EDB Slony Replication on an RHEL/CentOS host, a Debian/Ubuntu host, and a Windows host. +This section walks you through installing EDB Slony Replication on an RHEL/CentOS/Rocky Linux host, a Debian/Ubuntu host, and a Windows host. The EDB Slony Replication version required by your EDB Postgres Advanced and PostgreSQL Server installation is version-specific, but the documented and supported functionality of each version is the same. diff --git a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx index 067e1c2bfc5..aece6d75d58 100644 --- a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx +++ b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -On a CentOS and Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. +On a CentOS/Rocky Linux and Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. On a Windows host, the configuration files are named `master.conf.sample` and `slave.conf.sample`. They are located in the `/etc` directory under the EDB Postgres Advanced Server installation. Before configuring Slony Replication, you must rename the configuration files to `master.conf` and `slave.conf`. diff --git a/product_docs/docs/slony/2.2.10/04_uninstallation.mdx b/product_docs/docs/slony/2.2.10/04_uninstallation.mdx index c886c585ea7..10215129d1c 100644 --- a/product_docs/docs/slony/2.2.10/04_uninstallation.mdx +++ b/product_docs/docs/slony/2.2.10/04_uninstallation.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: This section walks you through uninstalling Slony Replication. -## Uninstalling Slony Replication on an RHEL/CentOS Host +## Uninstalling Slony Replication on an RHEL/CentOS/Rocky Linux Host To uninstall Slony Replication on an RHEL/CentOS host, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ yum remove edb-as-slony-replication* where <xx> is the EDB Postgres Advanced Server version. -On RHEL/CentOS 8: +On RHEL/Rocky Linux 8: ```text dnf remove edb-as-slony-replication* From 40d55e9c4bc89a8daa8702f399994d513277326f Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 24 Jan 2022 17:02:30 +0530 Subject: [PATCH 59/97] Replaced CentOS 8 to Rocky Linux 8 Replaced CentOS 8 to Rocky Linux 8 in EPAS v11, 12, 13 and 14 Linux Installation guide --- ...age_manager_to_install_advanced_server.mdx | 38 +++++++-------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- .../06_uninstalling_advanced_server.mdx | 6 +-- ...age_manager_to_install_advanced_server.mdx | 40 ++++++++-------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- .../06_uninstalling_advanced_server.mdx | 6 +-- ...age_manager_to_install_advanced_server.mdx | 46 +++++++++---------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- ...06_installing_and_configuring_pgadmin4.mdx | 2 +- .../07_uninstalling_advanced_server.mdx | 6 +-- ...age_manager_to_install_advanced_server.mdx | 42 ++++++++--------- .../epas_inst_linux/04_enabling_core_dump.mdx | 4 +- .../05_installing_troubleshooting.mdx | 2 +- ...06_installing_and_configuring_pgadmin4.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 2 +- .../08_uninstalling_advanced_server.mdx | 6 +-- 19 files changed, 110 insertions(+), 110 deletions(-) diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index ffe2ca8e220..ff9b9ea2dd3 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -74,7 +74,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text # dnf -y install java @@ -94,9 +94,9 @@ After receiving your repository credentials you can: - Modify the file, providing your user name and password. - Install Advanced Server. -## Installing on CentOS +## Installing on CentOS 7 or Rocky Linux 8 -You can use an RPM package to install Advanced Server on a CentOS host. +You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -106,7 +106,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -126,19 +126,19 @@ You can use an RPM package to install Advanced Server on a CentOS host. # yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text # dnf -y install epel-release ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On CentOS 8, disable the built-in PostgreSQL module: + On Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -154,7 +154,7 @@ After saving your changes to the configuration file, you can use `yum install` o yum -y install edb-as11-server ``` -- On CentOS 8: +- On Rocky Linux 8: ```text dnf -y install edb-as11-server @@ -399,7 +399,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or CentOS 8: +On RHEL or Rocky Linux 8: ```text dnf search @@ -482,7 +482,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-repo @@ -496,7 +496,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb* @@ -917,7 +917,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -925,9 +925,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -1014,9 +1014,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -On a CentOS or RedHat version 7.x | 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as11/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -1044,7 +1044,7 @@ By default, data files reside under `/var/lib/edb/as11/data` directory. To use a You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** The `edb-as11-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1096,7 +1096,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or CentOS 8.x: + On RHEL or Rocky Linux 8.x: ```bash dnf install epel-release @@ -1139,7 +1139,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as11-server ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install edb-as11-server diff --git a/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx index 82b7e934ef6..2ab5bf46c4b 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x or 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index d580ad8ac66..7d9987f5a90 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -32,9 +32,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on CentOS or RHEL 7.x | 8.x +### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -If your installation of Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx index 722eca76dc9..3104ca0c0ed 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx @@ -32,7 +32,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove @@ -43,7 +43,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or CentOS 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or CentOS 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + In RHEL or Rocky Linux 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 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: @@ -53,7 +53,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as11-server* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove edb-as11-server* diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index da3ef185990..0fcf57655c8 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -20,7 +20,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` - On SLES: `zypper search --requires --verbose ` @@ -73,7 +73,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text # dnf -y install java @@ -94,9 +94,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS +## Installing on CentOS 7 or Rocky Linux 8 -You can use an RPM package to install Advanced Server on a CentOS host. +You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -106,7 +106,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -128,7 +128,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. # yum makecache ``` - On CentOS 8: + On Rocky Linux 8: ```text # dnf -y install epel-release @@ -136,13 +136,13 @@ You can use an RPM package to install Advanced Server on a CentOS host. # dnf makecache ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On CentOS 8, disable the built-in PostgreSQL module: + On Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -170,7 +170,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as12-server ``` -- On CentOS 8: +- On Rocky Linux 8: ```text dnf -y install edb-as12-server @@ -445,7 +445,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or CentOS 8: +On RHEL or Rocky Linux 8: ```text dnf search @@ -540,7 +540,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-repo @@ -554,7 +554,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb* @@ -1017,7 +1017,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -1025,9 +1025,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -1174,9 +1174,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -On a CentOS or RedHat version 7.x | 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as12/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -1204,7 +1204,7 @@ By default, data files reside under `/var/lib/edb/as12/data` directory. To use a You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** The `edb-as12-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1256,7 +1256,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or CentOS 8.x: + On RHEL or Rocky Linux 8.x: ```bash dnf install epel-release @@ -1299,7 +1299,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as12-server ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install edb-as12-server diff --git a/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx index c4d025b09b1..d75461ecb14 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x or 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x or RHEL or Rocky Linux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index 08ee32d580a..5360d07865b 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -33,9 +33,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on CentOS or RHEL 7.x | 8.x +### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -If your installation of Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx index 41e38add5e8..e08c5ff20f4 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx @@ -32,7 +32,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove @@ -43,7 +43,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or CentOS 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or CentOS 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + In RHEL or Rocky Linux 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 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: @@ -53,7 +53,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as12-server* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove edb-as12-server* diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index e493f7dda6e..b71d367f48a 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -12,7 +12,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` Where, `package_name` is the name of the package that you want to install. @@ -64,7 +64,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text # dnf -y install java @@ -85,9 +85,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS +## Installing on CentOS 7 or Rocky Linux 8 -You can use an RPM package to install Advanced Server on a CentOS host. +You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -97,7 +97,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -119,7 +119,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. # yum makecache ``` - On CentOS 8: + On Rocky Linux 8: ```text # dnf -y install epel-release @@ -127,13 +127,13 @@ You can use an RPM package to install Advanced Server on a CentOS host. # dnf makecache ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On CentOS 8, disable the built-in PostgreSQL module: + On Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -161,7 +161,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as13-server ``` -- On CentOS 8: +- On Rocky Linux 8: ```text dnf -y install edb-as13-server @@ -432,7 +432,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or CentOS 8: +On RHEL or Rocky Linux 8: ```text dnf search @@ -527,7 +527,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-repo @@ -541,7 +541,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb* @@ -717,7 +717,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -725,9 +725,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -874,9 +874,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -On a CentOS or RedHat version 7.x | 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as13/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -919,7 +919,7 @@ By default, data files reside under `/var/lib/edb/as13/data` directory. To use a systemctl start edb-as-13 ``` -### Configuring SELinux Policy to Change the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Configuring SELinux Policy to Change the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x By default, the data files resides under `/var/lib/edb/as13/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps: @@ -1003,9 +1003,9 @@ By default, the data files resides under `/var/lib/edb/as13/data` directory. To You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination. -**Enabling Core Dumps on a CentOS or RHEL Host** +**Enabling Core Dumps on a RHEL orCentOS or Rocky Linux Host** -On a CentOS or RHEL 7.x or 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: - Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled. @@ -1230,7 +1230,7 @@ On Debian 9, 10 or Ubuntu 18, 20, core file creation is disabled by default. To You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** The `edb-as13-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1282,7 +1282,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or CentOS 8.x: + On RHEL or Rocky Linux 8.x: ```bash dnf install epel-release @@ -1325,7 +1325,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as13-server ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install edb-as13-server diff --git a/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx index 81de9f1960e..f3acb6151b2 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and RHEL or Rocky Linux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index de8bc028360..b11ef253354 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -27,9 +27,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on CentOS or RHEL 7.x | 8.x +### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -If your installation of Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx index c721a4b791b..7ecf6b7cee0 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: pgAdmin 4 is the leading Open Source management tool for Postgres databases. EDB pgAdmin 4 is an enhanced version of open source pgAdmin 4 specifically for Advanced Server databases. It is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance, and use of database objects. -You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or CentOS 8.x platform. +You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or Rocky Linux 8.x platform. diff --git a/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx index 9dae7506abe..f4abed45c23 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx @@ -30,7 +30,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove @@ -41,7 +41,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or CentOS 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or CentOS 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + In RHEL or Rocky Linux 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 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: @@ -51,7 +51,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as13-server* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove edb-as13-server* diff --git a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 10a1fb133fc..96e5a2fe455 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -8,7 +8,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` Where, `package_name` is the name of the package that you want to install. @@ -60,7 +60,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text # dnf -y install java @@ -81,9 +81,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS +## Installing on CentOS 7 or Rocky Linux 8 -You can use an RPM package to install Advanced Server on a CentOS host. +You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -93,7 +93,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -115,7 +115,7 @@ You can use an RPM package to install Advanced Server on a CentOS host. # yum makecache ``` - On CentOS 8: + On Rocky Linux 8: ```text # dnf -y install epel-release @@ -123,13 +123,13 @@ You can use an RPM package to install Advanced Server on a CentOS host. # dnf makecache ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On CentOS 8, disable the built-in PostgreSQL module: + On Rocky Linux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -157,7 +157,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as14-server ``` -- On CentOS 8: +- On Rocky Linux 8: ```text dnf -y install edb-as14-server @@ -430,7 +430,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or CentOS 8: +On RHEL or Rocky Linux 8: ```text dnf search @@ -525,7 +525,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb-repo @@ -539,7 +539,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf upgrade edb* @@ -715,7 +715,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -723,9 +723,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL or CentOS 7.x | Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -872,9 +872,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -On a CentOS or RedHat version 7.x | 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as14/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -917,7 +917,7 @@ By default, data files reside under `/var/lib/edb/as14/data` directory. To use a systemctl start edb-as-14 ``` -### Configuring SELinux Policy to Change the Data Directory Location on CentOS or Redhat 7.x | 8.x +### Configuring SELinux Policy to Change the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x By default, the data files resides under `/var/lib/edb/as14/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps: @@ -1001,7 +1001,7 @@ By default, the data files resides under `/var/lib/edb/as14/data` directory. To You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | 8.x** +**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** The `edb-as14-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1053,7 +1053,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or CentOS 8.x: + On RHEL or Rocky Linux 8.x: ```bash dnf install epel-release @@ -1096,7 +1096,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as14-server ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf -y install edb-as14-server diff --git a/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx b/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx index 1992e03472a..37bc053b744 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx @@ -6,9 +6,9 @@ title: "Enabling Core Dumps" You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination. -## Enabling Core Dumps on a CentOS or RHEL Host +## Enabling Core Dumps on a RHEL or CentOS or Rocky Linux Host -On a CentOS or RHEL 7.x or 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: +On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: - Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled. diff --git a/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx b/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx index b0fefceafe2..49fd42390f5 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx @@ -20,7 +20,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and RHEL or Rocky Linux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx b/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx index 13ac91ebc39..58d291f1404 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx @@ -6,7 +6,7 @@ title: "Installing and Configuring pgAdmin4" pgAdmin 4 is the leading Open Source management tool for Postgres databases. EDB pgAdmin 4 is an enhanced version of open source pgAdmin 4 specifically for Advanced Server databases. It is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance, and use of database objects. -You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or CentOS 8.x platform. +You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or Rocky Linux 8.x platform. diff --git a/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx index d794b032ab5..f1e6afa38a5 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx @@ -23,7 +23,7 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on CentOS or RHEL 7.x | 8.x +### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x If your installation of Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the Advanced Server service and supporting components. diff --git a/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx b/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx index 23ccfee23d5..421dad16b2a 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx @@ -28,7 +28,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove @@ -39,7 +39,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or CentOS 8, removing a package also removes all its dependencies that are not required by other packages. To override this default behavior of RHEL or CentOS 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + In RHEL or Rocky Linux 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 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: @@ -49,7 +49,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as14-server* ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: ```text dnf remove edb-as14-server* From f74bce40880ab4b44e37f3df1e1e4251bc9a425c Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 24 Jan 2022 06:34:27 -0500 Subject: [PATCH 60/97] tweak --- product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx index aece6d75d58..cebdb66e4a5 100644 --- a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx +++ b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -On a CentOS/Rocky Linux and Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. +On a CentOS/Rocky Linux/Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. On a Windows host, the configuration files are named `master.conf.sample` and `slave.conf.sample`. They are located in the `/etc` directory under the EDB Postgres Advanced Server installation. Before configuring Slony Replication, you must rename the configuration files to `master.conf` and `slave.conf`. From c7c8b2cb47aeb16a36f739d535446f07956160b8 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 24 Jan 2022 06:52:55 -0500 Subject: [PATCH 61/97] tweak --- .../docs/pgpool/4.2/03_configuring_connection_pooling.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx index 155f9421eee..7ef3c2dc56c 100644 --- a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx +++ b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx @@ -164,7 +164,7 @@ Modify the `postgresql.conf` file (located in `/var/lib/edb/as13/data`), adding Save the configuration file, and restart the server: - To restart on RHEL/CentOS 7 and 8 and Rocky Linux 8 platforms: + To restart on RHEL/CentOS 7 and RHEL/Rocky Linux 8 platforms: ```text systemctl restart edb-as-13 From b687f499d90d47abe2ac81963ece1447c3d44be6 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 24 Jan 2022 06:59:21 -0500 Subject: [PATCH 62/97] typo --- product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index 7eebaa73f1b..4fddc9d4beb 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -237,7 +237,7 @@ Perform the following steps to install PostGIS on an RHEL Host: -## Installing PostGIS on an RHEL 7 ppcl64le Host +## Installing PostGIS on an RHEL 7 ppc64le Host Before installing the repository configuration, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). From dd755787e0d6d965eecff564fdfb3384c6d8f710 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 10:25:28 -0500 Subject: [PATCH 63/97] more alignment and formatting changes --- .../01_preparing_azure/index.mdx | 22 +++++++++++++------ 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index 080712711a1..53e5396c244 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -32,15 +32,23 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. ``` Where the required arguments are: - - ``: Enter the Azure subscription ID of your BigAnimal deployment. - - ``: Enter the Azure region where your clusters are being deployed. See [Supported regions](../../overview/03a_region_support) for a list of possible regions. - + | Argument | Description | + | -------- | ----------- | + | <target-subscription> | Azure subscription ID of your BigAnimal deployment. | + | <region> | Azure region where your clusters are being deployed. See [Supported regions](../../overview/03a_region_support) for a list of possible regions. | + Possible options are: - - ``: Enter the Azure VM instance type for the BigAnimal cluster. Running the `biganimal-preflight-azure` script with no arguments provides a list of possible VM instance types. - - ``: Enter the type of network endpoint for the BigAnimal cluster, either **public** or **private**. - - `--activate-region` or `-r`: Specifies region activation if no clusters currently exist in the region. - - `--onboard`: Checks if the user and subscription are correctly configured. The behavior of the script defaults to `--onboard` if you provide no other options. + | Options | Description | + | ------- | ----------- | + | `-h` or `--help`| Displays the command help. | + | `-i` or `--instance-type` | Azure VM instance type for the BigAnimal cluster. The command help provides a list of possible VM instance types. | + | `-a` or `--high-availability` | Enables high availability for the cluster. See [Supported architectures](../../overview/02_high_availability) for more information.| + | `-e` or `--endpoint` | Type of network endpoint for the BigAnimal cluster, either **public** or **private**. See [Cluster networking architecture](../creating_a_cluster/01_cluster_networking) for more information. | + | `-r` or `--activate-region` | Specifies region activation if no clusters currently exist in the region. | + | `--onboard` | Checks if the user and subscription are correctly configured. + + The behavior of the script defaults to `--onboard` if you provide no other options. For example, if you want to deploy a cluster in an Azure subscription having an ID of `12412ab3d-1515-2217-96f5-0338184fcc04`, with an instance type of `e2s_v3`, in the `eastus2` region, in a `public` network, and with no existing cluster deployed, run the following command: From f5c73ae73bf782dc8f71a3d06f246301c7a69f88 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 24 Jan 2022 22:37:26 +0530 Subject: [PATCH 64/97] Replaced CentOS 8 to Rocky Linux 8 Replaced CentOS 8 to Rocky Linux 8 in PEM Linux Installation guide 7 and 8 --- .../01_prerequisites_for_installing_pem_server.mdx | 2 +- .../03_installing_pem_server_on_linux.mdx | 10 +++++----- .../06_installing_pem_agent_on_linux.mdx | 10 +++++----- .../07_registering_a_pem_agent.mdx | 2 +- .../01_prerequisites_for_installing_pem_server.mdx | 2 +- .../03_installing_pem_server_on_linux.mdx | 10 +++++----- ...g_the_pem_server_to_use_kerberos_authentication.mdx | 4 ++-- ...g_the_pem_server_to_use_windows_kerberos_server.mdx | 4 ++-- .../08_installing_pem_agent_on_linux.mdx | 10 +++++----- .../09_registering_a_pem_agent.mdx | 2 +- .../06_uninstalling_pem_components.mdx | 6 +++--- .../07_reference_linux_service_script.mdx | 2 +- 12 files changed, 32 insertions(+), 32 deletions(-) diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx index d22b77dfb4a..ee241d61eb9 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx @@ -64,7 +64,7 @@ legacyRedirectsGenerated: yum upgrade ``` - To upgrade packages on a CentOS or RHEL 8.x host + To upgrade packages on a Rocky Linux or RHEL 8.x host ```text dnf upgrade diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index 40c9b3eec0b..94d96411caa 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -9,9 +9,9 @@ legacyRedirectsGenerated: Before following the detailed instructions that install the PEM server on your specific platform, you must perform the prerequisite steps detailed in [Prerequisites for installing PEM Server](01_prerequisites_for_installing_pem_server/#prerequisites_for_installing_pem_server). -## Installing the PEM Server on a CentOS or RHEL Host +## Installing the PEM Server on a CentOS or RHEL or Rocky Linux Host -On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. **Install Version-Specific Software** @@ -23,7 +23,7 @@ Follow the version-specific instructions listed below to prepare your host syste yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a CentOS or RHEL 8.x host: +- On a Rocky Linux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -56,13 +56,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo After meeting the platform-specific prerequisites listed above, you can use `yum` or `dnf` to install the PEM Server: -- On CentOS or RHEL 7.x or 8.x, you can use `yum` to install the PEM server : +- On CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x, you can use `yum` to install the PEM server : ```text yum install edb-pem ``` -- On CentOS or RHEL 8.x, you can use `dnf` to install the PEM Server: +- On Rocky Linux or RHEL 8.x, you can use `dnf` to install the PEM Server: ```text dnf install edb-pem diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx index fa87d6205fb..8b62006f59b 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx @@ -9,9 +9,9 @@ legacyRedirectsGenerated: A PEM Agent may monitor one or more servers on one or more hosts. For comprehensive information about managing a PEM Agent, see the [PEM Agent User Guide](https://www.enterprisedb.com/docs/pem/latest/pem_agent/). -## Installing a PEM Agent on a CentOS or RHEL Host +## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux Host -On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. **Install Platform-Specific Software** @@ -21,7 +21,7 @@ On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` comma yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a CentOS or RHEL 8.x host: +- On a Rocky Linux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -52,13 +52,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo **Installing the PEM Agent** -- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x or 8.x: +- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x: ```text yum install edb-pem-agent ``` -- Also, you can use `dnf` command to install the PEM Agent on CentOS or RHEL 8.x: +- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux or RHEL 8.x: ```text dnf install edb-pem-agent diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx index 3faf59ffb10..18dae45f24e 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx @@ -60,7 +60,7 @@ By default, `heartbeat_connection` value is `false` but you can override the val Then, use a platform-specific command to start the PEM Agent service; -On a CentOS or RHEL 7.x or 8.x host, use `systemctl` to start the service: +On a CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x host, use `systemctl` to start the service: ```text systemctl start pemagent diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx index 79894fd79b9..80f173c06c0 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx @@ -66,7 +66,7 @@ legacyRedirectsGenerated: yum upgrade ``` - To upgrade packages on a CentOS or RHEL 8.x host + To upgrade packages on a Rocky Linux or RHEL 8.x host ```text dnf upgrade diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index bbbb67b9774..6c2f6423c89 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -7,9 +7,9 @@ legacyRedirectsGenerated: Before following the detailed instructions that install the PEM server on your specific platform, you must perform the prerequisite steps detailed in [Prerequisites for installing PEM Server](01_prerequisites_for_installing_pem_server/#prerequisites_for_installing_pem_server). -## Installing the PEM Server on a CentOS or RHEL Host +## Installing the PEM Server on a CentOS or RHEL or Rocky Linux Host -On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. **Install Version-Specific Software** @@ -21,7 +21,7 @@ Follow the version-specific instructions listed below to prepare your host syste yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a CentOS or RHEL 8.x host: +- On a Rocky Linux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -54,13 +54,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo After meeting the platform-specific prerequisites listed above, you can use yum or dnf to install the PEM Server: -- On CentOS or RHEL 7.x or 8.x, you can use `yum` to install the PEM server : +- On CentOS or RHEL 7.x, you can use `yum` to install the PEM server : ```text yum install edb-pem ``` -- On CentOS or RHEL 8.x, you can use `dnf` to install the PEM Server: +- On Rocky Linux or RHEL 8.x, you can use `dnf` to install the PEM Server: ```text dnf install edb-pem diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx index c047fc11a8a..a68d53efe5f 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx @@ -116,7 +116,7 @@ chown enterprisedb /.keytab Where, - - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. + - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL or Rocky Linux platforms. ## 5. Obtain and view the initial ticket @@ -183,7 +183,7 @@ It will display the principal along with the Kerberos ticket. Where, -- `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. +- `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL or Rocky Linux platforms. !!! Note If you are using PostgreSQL OR EDB Postgres Advanced Server 12 or later then you can specify connection type as `hostgssenc` to allow only gss encrypted connection. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx index 416a2bc6aae..4f539be348e 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx @@ -141,7 +141,7 @@ chown enterprisedb /pemdb.keytab Where, - - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. + - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL or Rocky Linux platforms. ## 5. Obtain and view the initial ticket @@ -208,7 +208,7 @@ It will display the principal along with the kerberos ticket. Where, -- `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. +- `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL or Rocky Linux platforms. !!! Note You cannot specify connection type as `hostgssenc` as windows does not support gss encrypted connection. diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx index f34573afaca..2b57870847a 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx @@ -7,9 +7,9 @@ legacyRedirectsGenerated: A PEM Agent may monitor one or more servers on one or more hosts. For comprehensive information about managing a PEM Agent, see the [PEM Agent User Guide](https://www.enterprisedb.com/docs/pem/latest/pem_agent/). -## Installing a PEM Agent on a CentOS or RHEL Host +## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux Host -On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. **Install Platform-Specific Software** @@ -19,7 +19,7 @@ On a CentOS or RHEL system, you can use the `yum` package manager or `dnf` comma yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a CentOS or RHEL 8.x host: +- On a Rocky Linux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -50,13 +50,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo **Installing the PEM Agent** -- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x or 8.x: +- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x | RHEL or Rocky Linux 8.x: ```text yum install edb-pem-agent ``` -- Also, you can use `dnf` command to install the PEM Agent on CentOS or RHEL 8.x: +- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux or RHEL 8.x: ```text dnf install edb-pem-agent diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx index 2b23e4576ce..c44d3a5c6f8 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx @@ -59,7 +59,7 @@ By default, `heartbeat_connection` value is `false` but you can override the val Then, use a platform-specific command to start the PEM Agent service; -On a CentOS or RHEL 7.x or 8.x host, use `systemctl` to start the service: +On a CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x host, use `systemctl` to start the service: ```text systemctl start pemagent diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx index ef74c67064b..e7b660b70e0 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx @@ -12,9 +12,9 @@ If you uninstall the PEM server package from a host, the PEM Agent package insta !!! Note Before uninstalling the PEM Agent, you need to de-register the agent first. You can de-register the agent using the `pemworker` command-line utility. After that, you can proceed with the uninstallation steps. -## Uninstalling PEM components from CentOS or RHEL Hosts +## Uninstalling PEM components from CentOS or RHEL or Rocky Linux Hosts -You can use variations of the `rpm`, `yum remove`, or `yum erase`, commands to remove the installed packages from CentOS or RHEL 7.x or 8.x hosts. Also you use `dnf remove` command to remove the installed package from CentOS or RHEL 8.x host. Note that removing a package does not damage the PEM data directory. +You can use variations of the `rpm`, `yum remove`, or `yum erase`, commands to remove the installed packages from CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x hosts. Also you use `dnf remove` command to remove the installed package from Rocky Linux or RHEL 8.x host. Note that removing a package does not damage the PEM data directory. - Include the `-e` option when invoking the rpm command to remove an installed package; the command syntax is: @@ -36,7 +36,7 @@ You can use variations of the `rpm`, `yum remove`, or `yum erase`, commands to r Where `package_name` is the name of the package that you would like to remove. -- You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on CentOS or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command: +- You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on Rocky Linux or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command: ```text dnf remove package_name diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx index ba003ed59f9..4e51946b014 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/07_reference_linux_service_script.mdx @@ -9,7 +9,7 @@ legacyRedirectsGenerated: - The Postgres server on which the PEM server resides must contain a service script. Postgres installers in Windows generated by EDB create a service script for you; if you are using a Postgres server from another source like native packages, you must provide a service script. - On **CentOS or RHEL 7.x or 8.x**, the service script resides in the `/usr/lib/systemd/system` directory. + On **CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x**, the service script resides in the `/usr/lib/systemd/system` directory. - Service scripts are platform-specific. From 89afffe363b9f21536c787a30a80db44fa08a077 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 12:49:32 -0500 Subject: [PATCH 65/97] added link to platform compatibility page --- .../eprs/6.2/01_introduction/04_supported_jdk_versions.mdx | 3 ++- .../eprs/7.0/01_introduction/04_supported_jdk_versions.mdx | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx index dcaa2cb3c2c..ee9cb3987f4 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx @@ -8,10 +8,11 @@ The xDB Replication Server is certified to work with the following Java platform | **Operating Systems** | **JDK Versions** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -| `CentOS 7 and 8`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| +| `CentOS 7 and Rocky Linux 8`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| | `PPCLE RHEL 8` | Red Hat OpenJDK 8 | | `PPCLE RHEL7` | Red Hat OpenJDK 8 | | `RHEL 7`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
- Oracle JDK 7
- Oracle JDK 8
| | `Windows 2012 R2, 2016, and 2019`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| | `Debian 10` |


Red Hat OpenJDK 11

| +See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#eprs) for more information. \ No newline at end of file diff --git a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx index 9a0cf28e81b..fa674b69218 100644 --- a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx @@ -18,3 +18,4 @@ The Replication Server is certified to work with the following Java platforms: | `Ubuntu 18 and 20` | OpenJDK 11

| | `Debian 9` | OpenJDK 8

| +See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#eprs) for more information. \ No newline at end of file From 0a874e8eae113ae9d6f382fc34eacc465dd05a93 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 15:29:13 -0500 Subject: [PATCH 66/97] added AlmaLinux --- .../bart/2.5/bart_inst/02_installing_bart.mdx | 18 +++++++++--------- .../2.5/bart_inst/05_uninstalling_bart.mdx | 6 +++--- .../bart/2.6/bart_inst/02_installing_bart.mdx | 16 ++++++++-------- .../2.6/bart_inst/05_uninstalling_bart.mdx | 6 +++--- ...talling_slony_on_a_linux_or_centos_host.mdx | 16 ++++++++-------- .../slony/2.2.10/01_installation/index.mdx | 2 +- .../2.2.10/02_configuration_and_usage.mdx | 2 +- .../docs/slony/2.2.10/04_uninstallation.mdx | 4 ++-- 8 files changed, 35 insertions(+), 35 deletions(-) diff --git a/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx b/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx index 2b345a5564b..09fbd867bbf 100644 --- a/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx +++ b/product_docs/docs/bart/2.5/bart_inst/02_installing_bart.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: This section will walk you through performing a fresh installation of BART on a host. Installation instructions are organized into the following platform/installer specific sections: -- [Installing BART on a CentOS/Rocky Linux Host](#installing-bart-on-a-centos-host) +- [Installing BART on a CentOS/Rocky Linux/AlmaLinux Host](#installing-bart-on-a-centos-host) - [Installing BART on a RHEL Host](#installing-bart-on-a-rhel-host) - [Installing BART on a RHEL/CentOS 7 PPCLE Host](#installing-bart-on-a-rhelcentos-7-ppcle-host) - [Installing BART on a Debian or Ubuntu Host](#installing-bart-on-a-debian-or-ubuntu-host) @@ -19,9 +19,9 @@ This section will walk you through performing a fresh installation of BART on a !!! Note If you are using the pdf version of this document, using the cut/paste command to copy may result in extra spaces or carriage returns in the pasted command. If a command fails, check the command carefully for additional characters. -## Installing BART on a CentOS/Rocky Linux Host +## Installing BART on a CentOS/Rocky Linux/AlmaLinux Host -The following section demonstrates installing BART on a CentOS/Rocky Linux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. +The following section demonstrates installing BART on a CentOS/Rocky Linux/AlmaLinux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. 1. To install the repository configuration, assume superuser privileges and invoke one of the following platform-specific commands: @@ -31,7 +31,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -53,19 +53,19 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8 or AlmaLinux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` -5. For Rocky Linux 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8 or AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -79,7 +79,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum install edb-as-server-client ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf install edb-as-server-client @@ -95,7 +95,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install edb-bart-2.5.9 ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install edb-bart-2.5.9 diff --git a/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx b/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx index dfacde7fed1..adc34d7f9c6 100644 --- a/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx +++ b/product_docs/docs/bart/2.5/bart_inst/05_uninstalling_bart.mdx @@ -12,9 +12,9 @@ legacyRedirectsGenerated: This section walks you through uninstalling BART. -## Uninstalling BART on a RHEL/CentOS/Rocky Linux Host +## Uninstalling BART on a RHEL/CentOS/Rocky Linux/AlmaLinux Host -To uninstall BART on a RHEL/CentOS/Rocky Linux host, assume the identity of the `root` user and invoke the following command: +To uninstall BART on a RHEL/CentOS/Rocky Linux/AlmaLinux host, assume the identity of the `root` user and invoke the following command: On RHEL/CentOS 7: @@ -22,7 +22,7 @@ On RHEL/CentOS 7: yum remove edb-bart ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf remove edb-bart diff --git a/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx b/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx index 5b6c9be4a5a..dd29e5383aa 100644 --- a/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx +++ b/product_docs/docs/bart/2.6/bart_inst/02_installing_bart.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: This section will walk you through performing a fresh installation of BART on a host. Installation instructions are organized into the following platform/installer specific sections: -- [Installing BART on a CentOS/Rocky Linux Host](#installing-bart-on-a-centos-host) +- [Installing BART on a CentOS/Rocky Linux/AlmaLinux Host](#installing-bart-on-a-centos-host) - [Installing BART on a RHEL Host](#installing-bart-on-a-rhel-host) - [Installing BART on a CentOS or RHEL Host](#installing-bart-on-a-rhelcentos-7-ppcle-host) - [Installing BART on a Debian or Ubuntu Host](#installing-bart-on-a-debian-or-ubuntu-host) @@ -17,9 +17,9 @@ This section will walk you through performing a fresh installation of BART on a !!! Note If you are using the pdf version of this document, using cut/paste to copy command may result in extra spaces or carriage returns in the pasted command. If a command fails, check the command carefully for additional characters. -## Installing BART on a CentOS/Rocky Linux Host +## Installing BART on a CentOS/Rocky Linux/AlmaLinux Host -The following section demonstrates installing BART on a CentOS/Rocky Linux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. +The following section demonstrates installing BART on a CentOS/Rocky Linux/AlmaLinux host using an RPM package.  This section assumes that the user has some knowledge of installation and system administration procedures, and has administrative privileges on the host. 1. To install the repository configuration, assume superuser privileges and invoke one of the following platform-specific commands: @@ -29,7 +29,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -51,7 +51,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release @@ -63,7 +63,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host dnf config-manager --set-enabled PowerTools ``` -5. For Rocky Linux 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8 or AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -77,7 +77,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum install edb-as-server-client ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf install edb-as-server-client @@ -93,7 +93,7 @@ The following section demonstrates installing BART on a CentOS/Rocky Linux host yum -y install edb-bart ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install edb-bart diff --git a/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx b/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx index 4fecf6b9d84..d61d2b140e5 100644 --- a/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx +++ b/product_docs/docs/bart/2.6/bart_inst/05_uninstalling_bart.mdx @@ -10,9 +10,9 @@ legacyRedirectsGenerated: This section walks you through uninstalling BART. -## Uninstalling BART on a RHEL/CentOS/Rocky Linux Host +## Uninstalling BART on a RHEL/CentOS/Rocky Linux/AlmaLinux Host -To uninstall BART on a RHEL/CentOS/Rocky Linux host, assume the identity of the `root` user and invoke the following command: +To uninstall BART on a RHEL/CentOS/Rocky Linux/AlmaLinux host, assume the identity of the `root` user and invoke the following command: On RHEL/CentOS 7: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum remove edb-bart ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf remove edb-bart diff --git a/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx b/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx index 1155492345b..6b9f7ed1c1c 100644 --- a/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx +++ b/product_docs/docs/slony/2.2.10/01_installation/01_installing_slony_on_a_linux_or_centos_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing Slony Replication on a CentOS/Rocky Linux Host" +title: "Installing Slony Replication on a CentOS/Rocky Linux/AlmaLinux Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -20,7 +20,7 @@ Follow the steps given below to install Slony Replication: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -40,19 +40,19 @@ Follow the steps given below to install Slony Replication: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: +4. For Rocky Linux 8 or AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` -5. For Rocky Linux 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8 or AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -68,7 +68,7 @@ Follow the steps given below to install Slony Replication: Where <xx> is the Slony version you want to install. - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install edb-as-slony-replication @@ -76,7 +76,7 @@ Follow the steps given below to install Slony Replication: Where <xx> is the Slony version you want to install. - To install Slony 2.2.10 on Rocky Linux 8 for EDB Postgres Advanced Server version 13, the command is: + To install Slony 2.2.10 on Rocky Linux 8 or AlmaLinux 8 for EDB Postgres Advanced Server version 13, the command is: ```text dnf -y install edb-as13-slony-replication @@ -174,7 +174,7 @@ Follow the steps given below to install Slony Replication: | **Platform** | **Service File Path** | **Installation File Path** | **Configuration File Path** | | --------------------- | ------------------------------------------------------------ | -------------------------- | --------------------------------------------------------------------------------------------- | -| `RHEL/CentOS 7 and RHEL/Rocky Linux 8` | `/usr/lib/systemd/system/edb-slony-replication-.service` | `/usr/edb/as` | The configuration file `slony-replication.ini` is located in `/etc/edb/slony-replication` | +| `RHEL/CentOS 7 and RHEL/Rocky Linux/AlmaLinux 8` | `/usr/lib/systemd/system/edb-slony-replication-.service` | `/usr/edb/as` | The configuration file `slony-replication.ini` is located in `/etc/edb/slony-replication` | In the above table, <xx> represents the EDB Postgres Advanced Server version. diff --git a/product_docs/docs/slony/2.2.10/01_installation/index.mdx b/product_docs/docs/slony/2.2.10/01_installation/index.mdx index 7e590a2558c..6a8b6cc62a5 100644 --- a/product_docs/docs/slony/2.2.10/01_installation/index.mdx +++ b/product_docs/docs/slony/2.2.10/01_installation/index.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -This section walks you through installing EDB Slony Replication on an RHEL/CentOS/Rocky Linux host, a Debian/Ubuntu host, and a Windows host. +This section walks you through installing EDB Slony Replication on an RHEL/CentOS/Rocky Linux/AlmaLinux host, a Debian/Ubuntu host, and a Windows host. The EDB Slony Replication version required by your EDB Postgres Advanced and PostgreSQL Server installation is version-specific, but the documented and supported functionality of each version is the same. diff --git a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx index cebdb66e4a5..a0cedb9dbe0 100644 --- a/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx +++ b/product_docs/docs/slony/2.2.10/02_configuration_and_usage.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: -On a CentOS/Rocky Linux/Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. +On a CentOS/Rocky Linux/AlmaLinux/Debian host, the configuration file (`slony-replication.ini`) is located in the `/etc/edb/slony-replication` directory. Use the configuration file to specify connection information for the master and standby nodes. On a Windows host, the configuration files are named `master.conf.sample` and `slave.conf.sample`. They are located in the `/etc` directory under the EDB Postgres Advanced Server installation. Before configuring Slony Replication, you must rename the configuration files to `master.conf` and `slave.conf`. diff --git a/product_docs/docs/slony/2.2.10/04_uninstallation.mdx b/product_docs/docs/slony/2.2.10/04_uninstallation.mdx index 10215129d1c..ca984637468 100644 --- a/product_docs/docs/slony/2.2.10/04_uninstallation.mdx +++ b/product_docs/docs/slony/2.2.10/04_uninstallation.mdx @@ -8,7 +8,7 @@ legacyRedirectsGenerated: This section walks you through uninstalling Slony Replication. -## Uninstalling Slony Replication on an RHEL/CentOS/Rocky Linux Host +## Uninstalling Slony Replication on an RHEL/CentOS/Rocky Linux/AlmaLinux Host To uninstall Slony Replication on an RHEL/CentOS host, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ yum remove edb-as-slony-replication* where <xx> is the EDB Postgres Advanced Server version. -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf remove edb-as-slony-replication* From a33b5382904ab9cc8681209b1865c3b835f2f1e9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 17:52:39 -0500 Subject: [PATCH 67/97] added AlmaLinux --- .../01_installing_and_configuring_the_pgpool-II.mdx | 12 ++++++------ product_docs/docs/pgpool/4.2/02_extensions.mdx | 10 +++++----- .../pgpool/4.2/03_configuring_connection_pooling.mdx | 2 +- product_docs/docs/pgpool/4.2/05_upgrade.mdx | 4 ++-- .../docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx | 8 ++++---- 5 files changed, 18 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx index 12678f14e58..f137650b778 100644 --- a/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx +++ b/product_docs/docs/pgpool/4.2/01_installing_and_configuring_the_pgpool-II.mdx @@ -30,7 +30,7 @@ This documentation assumes that the user has some knowledge of installation and Before installing the repository configuration, you must have credentials that allow access to the EDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). -## Installing Pgpool-II on a CentOS/Rocky Linux x86-64 Host +## Installing Pgpool-II on a CentOS/Rocky Linux/AlmaLinux x86-64 Host Perform the following steps: @@ -42,7 +42,7 @@ Perform the following steps: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -62,13 +62,13 @@ Perform the following steps: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for Rocky Linux 8: +4. The following steps are applicable only for Rocky Linux 8 or AlmaLinux 8: a. Enable the PowerTools repository to satisfy additional package dependencies: @@ -90,7 +90,7 @@ Perform the following steps: yum install edb-pgpool ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf install edb-pgpool @@ -106,7 +106,7 @@ Perform the following steps: yum install edb-pgpool42 ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf install edb-pgpool42 diff --git a/product_docs/docs/pgpool/4.2/02_extensions.mdx b/product_docs/docs/pgpool/4.2/02_extensions.mdx index 49a0b84ca20..f893b6eb620 100644 --- a/product_docs/docs/pgpool/4.2/02_extensions.mdx +++ b/product_docs/docs/pgpool/4.2/02_extensions.mdx @@ -19,7 +19,7 @@ Before installing Pgpool-II extensions, install the EDB Postgres Advanced Server The following section walks you through the steps of installing Pgpool-II extensions. To request credentials for the repository, visit [the EDB website](https://www.enterprisedb.com/user). -### Installing Pgpool-II Extension on a CentOS/Rocky Linux Host +### Installing Pgpool-II Extension on a CentOS/Rocky Linux/AlmaLinux Host Assume superuser privileges and perform the following steps to install Pgpool-II extensions on a CentOS host: @@ -31,7 +31,7 @@ Assume superuser privileges and perform the following steps to install Pgpool-II yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -51,13 +51,13 @@ Assume superuser privileges and perform the following steps to install Pgpool-II yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8 or AlmaLinux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ```text dnf config-manager --set-enabled PowerTools @@ -157,7 +157,7 @@ Perform the following steps to install Pgpool-II extensions on an RHEL host: yum -y install edb-as13-pgpool42-extensions ``` - On RHEL/Rocky Linux 8: + On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf install edb-as-pgpool-extensions diff --git a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx index 7ef3c2dc56c..6b56d3012e7 100644 --- a/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx +++ b/product_docs/docs/pgpool/4.2/03_configuring_connection_pooling.mdx @@ -164,7 +164,7 @@ Modify the `postgresql.conf` file (located in `/var/lib/edb/as13/data`), adding Save the configuration file, and restart the server: - To restart on RHEL/CentOS 7 and RHEL/Rocky Linux 8 platforms: + To restart on RHEL/CentOS 7 and RHEL/Rocky Linux/AlmaLinux 8 platforms: ```text systemctl restart edb-as-13 diff --git a/product_docs/docs/pgpool/4.2/05_upgrade.mdx b/product_docs/docs/pgpool/4.2/05_upgrade.mdx index 6dfb901db6d..7547345d82e 100644 --- a/product_docs/docs/pgpool/4.2/05_upgrade.mdx +++ b/product_docs/docs/pgpool/4.2/05_upgrade.mdx @@ -32,7 +32,7 @@ where <xx> is the Pgpool version you want to upgrade. For example, to upgrade yum upgrade edb-pgpool37 ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf upgrade edb-pgpool @@ -67,7 +67,7 @@ Where `` is the EDB Postgres Advanced Server version, and `` is the Pgpo !!! Note Only minor version upgrade is supported (for example, you can upgrade from 3.6.20 to 3.6.21 extension, but not 3.7.14). -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf upgrade edb-as-pgpool-extensions diff --git a/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx b/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx index d564c4f8720..1d0dd2e269f 100644 --- a/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx +++ b/product_docs/docs/pgpool/4.2/06_uninstalling_pgpool-II.mdx @@ -10,7 +10,7 @@ The following section outlines the process of uninstalling Pgpool-II and its ext ## Uninstalling Pgpool-II -### Uninstalling Pgpool-II on an RHEL//Rocky Linux Host +### Uninstalling Pgpool-II on an RHEL//Rocky Linux/AlmaLinux Host To uninstall Pgpool-II, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum erase edb-pgpool ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf erase edb-pgpool @@ -60,7 +60,7 @@ The Pgpool-II graphical installer creates an uninstaller in the installation dir The following section outlines the process of uninstalling Pgpool-II and its extensions. -### Uninstalling Pgpool-II Extensions on an RHEL/CentOS/Rocky Linux Host +### Uninstalling Pgpool-II Extensions on an RHEL/CentOS/Rocky Linux/AlmaLinux Host To remove extensions from the server, execute the following command: @@ -70,7 +70,7 @@ On RHEL/CentOS 7: yum erase edb-as-pgpool-extensions ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf erase edb-as-pgpool-extensions From e4ef450b1abaf9f544154446108cc76ec2419526 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 19:23:09 -0500 Subject: [PATCH 68/97] added AlmaLinux --- .../postgis/3.1.2/01_installing_postgis.mdx | 22 +++++++++---------- .../postgis/3.1.2/05_uninstalling_postgis.mdx | 8 +++---- .../postgis/3.1.4/01a_installing_postgis.mdx | 10 ++++----- .../postgis/3.1.4/05_uninstalling_postgis.mdx | 6 ++--- 4 files changed, 23 insertions(+), 23 deletions(-) diff --git a/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx b/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx index 204cbe5b47c..d498a57079f 100644 --- a/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.2/01_installing_postgis.mdx @@ -15,14 +15,14 @@ The following table lists the latest PostGIS versions and their corresponding Ad | **PostGIS Version** | **Supported Advanced Server Versions** | **Supported Platforms** | | ------------------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `PostGIS 3.1` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.1` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | -| `PostGIS 3.1` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | +| `PostGIS 3.1` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | +| `PostGIS 3.1` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | +| `PostGIS 3.1` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | | `PostGIS 3.1` | Advanced Server 9.6, 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | -| `PostGIS 3.0` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | +| `PostGIS 3.0` | Advanced Server 13 | RHEL/CentOS 7 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver and Ubuntu 20.04 LTS Focal Fossa
Windows 64 x86 Interactive Installer | +| `PostGIS 3.0` | Advanced Server 12 | RHEL/CentOS 7 x86_64 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer | | `PostGIS 3.0` | Advanced Server 11 | RHEL/CentOS 7 - x86_64 | -| `PostGIS 2.5` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | +| `PostGIS 2.5` | Advanced Server 12 | RHEL/CentOS 7 - x86_64 and RHEL/Rocky Linux/AlmaLinux 8 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch and 10x Buster
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | | `PostGIS 2.5` | Advanced Server 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Debian 9x Stretch
Ubuntu 18.04 LTS Bionic Beaver
Windows 64 x86 Interactive Installer
SLES 12 | | `PostGIS 2.4` | Advanced Server 9.6, 10 and 11 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | | `PostGIS 2.3` | Advanced Server 9.6 and 10 | RHEL/CentOS 7 - x86_64
RHEL/CentOS 7 - ppc64le
Windows 64 x86 Interactive Installer | @@ -30,7 +30,7 @@ The following table lists the latest PostGIS versions and their corresponding Ad -## Installing PostGIS on a CentOS/Rocky Linux Host +## Installing PostGIS on a CentOS/Rocky Linux/AlmaLinux Host Before creating the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -44,7 +44,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -64,13 +64,13 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for Rocky Linux 8 platform: +4. The following steps are applicable only for Rocky Linux/AlmaLinux 8 platform: a. Enable the PowerTools repository to satisfy package dependencies: @@ -92,7 +92,7 @@ Perform the following steps to install PostGIS on a CentOS Host: yum -y install edb-as13-postgis3 ``` - On Rocky Linux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: + On Rocky Linux 8 or AlmaLinux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: ```text dnf -y install edb-as13-postgis3 diff --git a/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx b/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx index cc5ff6f1d5e..488602c978c 100644 --- a/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx +++ b/product_docs/docs/postgis/3.1.2/05_uninstalling_postgis.mdx @@ -10,9 +10,9 @@ legacyRedirectsGenerated: This section walks you through the process of uninstalling PostGIS. -## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux Host +## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux/AlmaLinux Host -To uninstall PostGIS on a CentOS/RHEL/Rocky Linux host, assume the identity of the root user and invoke the following command: +To uninstall PostGIS on a CentOS/RHEL/Rocky Linux/AlmaLinux host, assume the identity of the root user and invoke the following command: On CentOS/RHEL 7 for EPAS version 13: @@ -28,13 +28,13 @@ yum erase edb-as-postgis-* Where *<xx>* is the Advanced Server version and <y.y.y> is the PostGIS version you want to uninstall. -On Rocky Linux/RHEL 8 for EPAS version 13: +On Rocky Linux/AlmaLinux/RHEL 8 for EPAS version 13: ```text dnf -y erase edb-as13-postgis3* ``` -On Rocky Linux/RHEL 8 for older vesions of EPAS: +On Rocky Linux/AlmaLinux/RHEL 8 for older vesions of EPAS: ```text dnf erase edb-as-postgis-* diff --git a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx index 4fddc9d4beb..3fc3e2509a0 100644 --- a/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/01a_installing_postgis.mdx @@ -23,7 +23,7 @@ See the following sections to install EDB PostGIS on specific hosts. -## Installing PostGIS on a CentOS/Rocky Linux x86-64 Host +## Installing PostGIS on a CentOS/Rocky Linux/AlmaLinux x86-64 Host Before creating the repository configuration file, you must have credentials that allow access to the EnterpriseDB repository. For information about requesting credentials, visit the [EDB website](https://www.enterprisedb.com/user). @@ -37,7 +37,7 @@ Perform the following steps: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -57,13 +57,13 @@ Perform the following steps: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ```text dnf -y install epel-release ``` -4. The following steps are applicable only for Rocky Linux 8 platform: +4. The following steps are applicable only for Rocky Linux 8 or AlmaLinux 8 platform: a. Enable the PowerTools repository to satisfy package dependencies: @@ -85,7 +85,7 @@ Perform the following steps: yum -y install edb-as13-postgis3 ``` - On Rocky Linux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: + On Rocky Linux 8 or AlmaLinux 8, to install the latest version of PostGIS version for EDB Advanced Server version 13.0: ```text dnf -y install edb-as13-postgis3 diff --git a/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx b/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx index d72596b3ab5..acdbfe3fa06 100644 --- a/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx +++ b/product_docs/docs/postgis/3.1.4/05_uninstalling_postgis.mdx @@ -7,7 +7,7 @@ title: "Uninstalling PostGIS" This section walks you through the process of uninstalling PostGIS. -## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux Host +## Uninstalling PostGIS on a CentOS/RHEL/Rocky Linux/AlmaLinux Host To uninstall PostGIS on a CentOS/RHEL host, assume the identity of the root user and invoke the following command: @@ -25,13 +25,13 @@ yum erase edb-as-postgis-* Where *<xx>* is the Advanced Server version and <y.y.y> is the PostGIS version you want to uninstall. -On Rocky Linux/RHEL 8 for EPAS version 13: +On Rocky Linux/AlmaLinux/RHEL 8 for EPAS version 13: ```text dnf -y erase edb-as13-postgis3* ``` -On Rocky Linux/RHEL 8 for older versions of EPAS: +On Rocky Linux/AlmaLinux/RHEL 8 for older versions of EPAS: ```text dnf erase edb-as-postgis-* From 5d277bb796ffd9f5702ccbe12a97b9ed3f645352 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 24 Jan 2022 19:37:59 -0500 Subject: [PATCH 69/97] added AlmaLinux --- .../12.0.0.2/02_requirements_overview.mdx | 2 +- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 10 +++++----- .../12.2.0.2/02_requirements_overview.mdx | 2 +- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- .../13.0.0.1/02_requirements_overview.mdx | 2 +- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- .../13.1.0.1/02_requirements_overview.mdx | 2 +- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- .../13.1.0.2/02_requirements_overview.mdx | 2 +- .../03_edb-odbc_overview/01_installing_edb-odbc.mdx | 8 ++++---- 10 files changed, 26 insertions(+), 26 deletions(-) diff --git a/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx index f14f2276a6b..9b8898ba7c0 100644 --- a/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/12.0.0.2/02_requirements_overview.mdx @@ -18,7 +18,7 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux or AlmaLinux (x86_64) 8.x - CentOS (x86_64) 7.x - OL Linux 7.x - PPC-LE 8 running RHEL or CentOS 7.x diff --git a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 8e2f4a03ddd..5ea9f937e6e 100644 --- a/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.0.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -22,7 +22,7 @@ Install the epel-release package: yum -y install https://dl.fedoraproject.org/pub/epel/ epel-release-latest-7.noarch.rpm ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install https://dl.fedoraproject.org/pub/epel/ epel-release-latest-7.noarch.rpm @@ -51,7 +51,7 @@ To create the repository configuration file, assume superuser privileges, and in yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -85,7 +85,7 @@ yum install edb-odbc yum install edb-odbc-devel ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf install edb-odbc @@ -109,7 +109,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or yum upgrade edb-repo ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb-repo @@ -125,7 +125,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r yum upgrade edb-odbc-devel ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb-odbc diff --git a/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx index 60aa4787390..8065da89679 100644 --- a/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/12.2.0.2/02_requirements_overview.mdx @@ -18,7 +18,7 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux/AlmaLinux (x86_64) 8.x - CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x diff --git a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index b8449c4fd1e..5e71faf807d 100644 --- a/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/12.2.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -16,7 +16,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux or AlmaLinux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux or Alma Linux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -288,7 +288,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -300,7 +300,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-odbc` diff --git a/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx index 2278fe9f640..7532080ca1f 100644 --- a/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.0.0.1/02_requirements_overview.mdx @@ -14,7 +14,7 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux/AlmaLinux (x86_64) 8.x - CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x diff --git a/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx index bfc911896cf..73582468151 100644 --- a/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.0.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -13,7 +13,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -294,7 +294,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux 8 or AlmaLinux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -366,7 +366,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -378,7 +378,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-odbc` diff --git a/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx index 2278fe9f640..7532080ca1f 100644 --- a/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.1/02_requirements_overview.mdx @@ -14,7 +14,7 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - Red Hat Enterprise Linux (x86_64) 8.x and 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux/AlmaLinux (x86_64) 8.x - CentOS (x86_64) 7.x - OL Linux 8.x and 7.x - PPC-LE 8 running RHEL or CentOS 7.x diff --git a/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx index bfc911896cf..73582468151 100644 --- a/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.1/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -13,7 +13,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -294,7 +294,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux 8 or AlmaLinux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -366,7 +366,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -378,7 +378,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-odbc` diff --git a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx index 56e6414f2ae..e76be40faf5 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/02_requirements_overview.mdx @@ -14,7 +14,7 @@ The EDB ODBC Connector native packages are supported on the following platforms: 64 bit Linux: - RHEL 8.x and 7.x (x86_64) -- Rocky Linux 8.x (x86_64) +- Rocky Linux/AlmaLinux 8.x (x86_64) - CentOS 7.x (x86_64) - OL Linux 8.x and 7.x (x86_64) - RHEL 8.x and 7.x (ppc64le) diff --git a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index e158bfb6a74..2edf00d2980 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -14,7 +14,7 @@ You can install the ODBC Connector using an RPM package on the following platfor - [RHEL 8 x86-64](#rhel8) - [RHEL 8 ppc64le](#on-rhel-8-ppc64le) - [CentOS 7 x86-64](#centos7) -- [Rocky Linux 8 x86-64](#centos8) +- [Rocky Linux/AlmaLinux 8 x86-64](#centos8) @@ -358,7 +358,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux 8 or AlmaLinux 8 Before installing the ODBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -430,7 +430,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -442,7 +442,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-odbc-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-odbc` From cc8ab442e6e594304a8e8dfb2b803560c6d9f56d Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 24 Jan 2022 19:41:37 -0500 Subject: [PATCH 70/97] removed extra space --- .../13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx index 2edf00d2980..0878dbad202 100644 --- a/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx +++ b/product_docs/docs/odbc_connector/13.1.0.2/03_edb-odbc_overview/01_installing_edb-odbc.mdx @@ -430,7 +430,7 @@ If you have an existing EDB ODBC connector RPM installation, you can use yum or `yum upgrade edb-repo` -- On RHEL or Rocky Linux or AlmaLinux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` From 23f16070b1f2b4fcb4281a29e913c6c08c41fbc3 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 04:43:30 -0500 Subject: [PATCH 71/97] added AlmaLinux --- .../ocl_connector/12.1.2.1/02_supported_platforms.mdx | 2 +- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- .../ocl_connector/13.1.4.2/02_supported_platforms.mdx | 2 +- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- .../ocl_connector/14.1.0.1/02_supported_platforms.mdx | 2 +- .../01_installing_and_configuring_the_ocl_connector.mdx | 8 ++++---- 6 files changed, 15 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx index 0d8c04e51d6..7ad2b1dbf71 100644 --- a/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/12.1.2.1/02_supported_platforms.mdx @@ -11,7 +11,7 @@ The EDB OCL Connector is certified with Advanced Server version 9.5 and above. T - Red Hat Enterprise Linux (x86_64) 7.x and 8.x - CentOS (x86_64) 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux/AlmaLinux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index ae4f9f3a321..d56f2e658b1 100644 --- a/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/12.1.2.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -16,7 +16,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux 8 or AlmaLinux 8 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -288,7 +288,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -300,7 +300,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-oci` diff --git a/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx index 6591e801959..b295a9e9bcf 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/02_supported_platforms.mdx @@ -13,7 +13,7 @@ The EDB OCL Connector is certified with Advanced Server version 9.6 and above. T - RHEL (x86_64) 7.x and 8.x - CentOS (x86_64) 7.x -- Rocky Linux (x86_64) 8.x +- Rocky Linux/AlmaLinux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index 15aa8fc93a4..6ed8d532b02 100644 --- a/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/13.1.4.2/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -18,7 +18,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -218,7 +218,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux 8 or AlmaLinux 8 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -290,7 +290,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux 8 or AlmaLinux 8: `dnf upgrade edb-repo` @@ -302,7 +302,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux 8 or AlmaLinux 8: `dnf upgrade edb-oci` diff --git a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx index 72c002d4658..27e0b0a5958 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/02_supported_platforms.mdx @@ -8,7 +8,7 @@ title: "Supported Platforms" The EDB OCL Connector is certified with Advanced Server version 9.6 and above. The EDB OCL Connector native packages are supported on the following 64-bit platforms: - RHEL 7.x and 8.x (x86_64) -- Rocky Linux 8.x (x86_64) +- Rocky Linux/AlmaLinux 8.x (x86_64) - CentOS 7.x (x86_64) - OL Linux 7.x and 8.x - RHEL 7.x (ppc64le) diff --git a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx index fd44119bdc3..81d2a3bd665 100644 --- a/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx +++ b/product_docs/docs/ocl_connector/14.1.0.1/04_open_client_library/01_installing_and_configuring_the_ocl_connector.mdx @@ -14,7 +14,7 @@ You can install the OCL Connector using an RPM package on the following platform - [RHEL 7 (x86-64)](#rhel7) - [RHEL 8 (x86-64)](#rhel8) - [CentOS 7 (x86-64)](#centos7) -- [Rocky Linux 8 (x86-64)](#centos8) +- [Rocky Linux/AlmaLinux 8 (x86-64)](#centos8) - [RHEL 8 (ppc64le)](#on-rhel-8-ppc64le) @@ -215,7 +215,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 x86-64 +### On Rocky Linux/AlmaLinux 8 x86-64 Before installing the OCL Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -349,7 +349,7 @@ If you have an existing `OCL Connector` RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -361,7 +361,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-oci-devel` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-oci` From d838cdd2f6a1cda6eea2aa086f6f480f6a49e281 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 04:55:34 -0500 Subject: [PATCH 72/97] Added AlmaLinux --- .../jdbc_connector/42.2.12.3/02_requirements_overview.mdx | 2 +- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- .../jdbc_connector/42.2.19.1/02_requirements_overview.mdx | 2 +- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- .../jdbc_connector/42.2.24.1/02_requirements_overview.mdx | 2 +- .../01_installing_the_connector_with_an_rpm_package.mdx | 6 +++--- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx index df528e61e8d..6a11bcd8b98 100644 --- a/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.12.3/02_requirements_overview.mdx @@ -18,7 +18,7 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: - RHEL and CentOS (x86_64) 7.x -- RHEL and Rocky Linux (x86_64) 8.x +- RHEL and Rocky Linux and AlmaLinux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index a0df158d553..3761c890fcf 100644 --- a/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.12.3/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -14,7 +14,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -208,7 +208,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On Rocky Linux 8 +## On Rocky Linux 8 or AlmaLinux 8 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -278,7 +278,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` diff --git a/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx index 9fdd3c41619..0f3ad1c25fc 100644 --- a/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.19.1/02_requirements_overview.mdx @@ -15,7 +15,7 @@ The EDB JDBC Connector native packages are supported on the following 64 bit Lin - RHEL and CentOS (x86_64) 7.x -- RHEL and Rocky Linux (x86_64) 8.x +- RHEL and Rocky Linux and AlmaLinux (x86_64) 8.x - OL Linux 7.x and 8.x - PPC-LE 8 running RHEL or CentOS 7.x - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 617831ed54d..ae1928a3909 100644 --- a/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.19.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -10,7 +10,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -204,7 +204,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -## On Rocky Linux 8 +## On Rocky Linux 8 or AlmaLinux 8 Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: @@ -274,7 +274,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linu or AlmaLinux 8: `dnf upgrade edb-repo` diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx index 489cd3ea7b4..f714374ef7a 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/02_requirements_overview.mdx @@ -14,7 +14,7 @@ The EDB JDBC Connector is certified with Advanced Server version 9.6 and above. The EDB JDBC Connector native packages are supported on the following 64 bit Linux platforms: - RHEL and CentOS 7.x (x86_64) -- RHEL and Rocky Linux 8.x (x86_64) +- RHEL and Rocky Linux and AlmaLinux 8.x (x86_64) - OL Linux 7.x and 8.x - RHEL 8.x (ppc64le) - SLES 12.x diff --git a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx index 1db4e3742dc..63d3288ddcf 100644 --- a/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx +++ b/product_docs/docs/jdbc_connector/42.2.24.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package.mdx @@ -10,7 +10,7 @@ You can install the JDBC Connector using an RPM package on the following platfor - [RHEL 7 x86-64](#rhel7) - [RHEL 8 x86-64](#rhel8) - [CentOS 7 x86-64](#centos7) -- [Rocky Linux 8 x86-64](#centos8) +- [Rocky Linux/AlmaLinux 8 x86-64](#centos8) - [RHEL 8 ppc64le](#on-rhel-8-ppc64le) @@ -337,7 +337,7 @@ If you have an existing JDBC Connector RPM installation, you can use yum or dnf `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -347,6 +347,6 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-jdbc` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-jdbc` From 76ca5e6f7bd6f593f0c3b9c04379a5ec0b1a7828 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 05:05:33 -0500 Subject: [PATCH 73/97] added AlmaLinux --- ...talling_pgbouncer_on_a_linux_or_centos_host.mdx | 14 +++++++------- .../docs/pgbouncer/1.16/01_installation/index.mdx | 2 +- .../pgbouncer/1.16/02_configuration_and_usage.mdx | 2 +- .../docs/pgbouncer/1.16/03_uninstallation.mdx | 4 ++-- 4 files changed, 11 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx index a0c64dddbba..82d2b7a17b1 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/01_installing_pgbouncer_on_a_linux_or_centos_host.mdx @@ -1,5 +1,5 @@ --- -title: "Installing PgBouncer on a CentOS/Rocky Linux x86-64 Host" +title: "Installing PgBouncer on a CentOS/Rocky Linux/AlmaLinux x86-64 Host" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -21,7 +21,7 @@ Follow the steps given below to install PgBouncer: yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ``` text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -41,19 +41,19 @@ Follow the steps given below to install PgBouncer: yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ``` text dnf -y install epel-release ``` -4. For Rocky Linux 8, enable the PowerTools repository to satisfy EPEL package dependencies: +4. For Rocky Linux 8 or AlmaLinux 8, enable the PowerTools repository to satisfy EPEL package dependencies: ``` text dnf config-manager --set-enabled PowerTools ``` -5. For Rocky Linux 8, disable the built-in PostgreSQL module: +5. For Rocky Linux 8 or AlmaLinux 8, disable the built-in PostgreSQL module: ``` text dnf -qy module disable postgresql @@ -69,7 +69,7 @@ Follow the steps given below to install PgBouncer: Where <xx> is the PgBouncer version you want to install. - On Rocky Linux 8: + On Rocky Linux 8 or AlmaLinux 8: ``` text dnf -y install edb-pgbouncer @@ -77,7 +77,7 @@ Follow the steps given below to install PgBouncer: Where <xx> is the PgBouncer version you want to install. - To install PgBouncer 1.16 on Rocky Linux 8, the command is: + To install PgBouncer 1.16 on Rocky Linux 8 or AlmaLinux 8, the command is: ``` text dnf -y install edb-pgbouncer116 diff --git a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx index a9e56f77be6..288549ce487 100644 --- a/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx +++ b/product_docs/docs/pgbouncer/1.16/01_installation/index.mdx @@ -24,7 +24,7 @@ This table lists the latest PgBouncer versions and their supported corresponding The documented and supported functionality of each version of PgBouncer is the same. The information in this documentation applies to all supported versions of PgBouncer. See the following topics to install EDB PgBouncer on specific hosts: -- [CentOS/Rocky Linux x86-64](01_installing_pgbouncer_on_a_linux_or_centos_host) +- [CentOS/Rocky Linux/AlmaLinux x86-64](01_installing_pgbouncer_on_a_linux_or_centos_host) - [Debian or Ubuntu x86-64](/02_installing_pgbouncer_on_a_debian_or_ubuntu_host) - [SLES 12 x86-64](03_installing_pgbouncer_on_an_sles_host) - [RHEL 8 ppcle](03a_installing_pgbouncer_on_a_rhel8_ppcle_host) diff --git a/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx b/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx index 720aed1a9cc..2aea8846665 100644 --- a/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx +++ b/product_docs/docs/pgbouncer/1.16/02_configuration_and_usage.mdx @@ -105,7 +105,7 @@ default_pool_size = 20 For more information about the settings used in the `pgbouncer.ini` file, click [here](https://pgbouncer.github.io/config.html). -After editing the PgBouncer configuration file to reflect your environment, you must restart the PgBouncer service for the changes to take effect. For CentOS, Rocky Linux, RHEL, SUSE, and Windows platforms, the PgBouncer service name is `edb-pgbouncer-1.16`, and for Deb packages, the PgBouncer service name is `edb-pgbouncer116`; use platform-specific commands to stop, start, or restart the service as needed. +After editing the PgBouncer configuration file to reflect your environment, you must restart the PgBouncer service for the changes to take effect. For CentOS, Rocky Linux, AlmaLinux, RHEL, SUSE, and Windows platforms, the PgBouncer service name is `edb-pgbouncer-1.16`, and for Deb packages, the PgBouncer service name is `edb-pgbouncer116`; use platform-specific commands to stop, start, or restart the service as needed. ## Using the PgBouncer Admin Console diff --git a/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx b/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx index 37ff21405e1..b1896f4bedb 100644 --- a/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx +++ b/product_docs/docs/pgbouncer/1.16/03_uninstallation.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: This section walks you through uninstalling PgBouncer. -## Uninstalling PgBouncer on a RHEL//Rocky Linux Host +## Uninstalling PgBouncer on a RHEL/Rocky Linux/AlmaLinux Host To uninstall PgBouncer on a CentOS host, assume the identity of the root user and invoke the following command: @@ -20,7 +20,7 @@ On RHEL/CentOS 7: yum -y erase edb-pgbouncer ``` -On RHEL/Rocky Linux 8: +On RHEL/Rocky Linux/AlmaLinux 8: ``` text dnf -y erase edb-pgbouncer From 8a9eec8350b93df0da5ae9411ddd0ad4d1596faa Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 05:27:18 -0500 Subject: [PATCH 74/97] added AlmaLinux --- product_docs/docs/efm/3/efm_quick_start/index.mdx | 2 +- .../docs/efm/3/efm_user/03_installing_efm.mdx | 8 ++++---- .../01_encrypting_database_password.mdx | 2 +- product_docs/docs/efm/3/efm_user/05_using_efm.mdx | 14 +++++++------- .../efm/3/efm_user/08_controlling_efm_service.mdx | 6 +++--- .../3/efm_user/12_upgrading_existing_cluster.mdx | 2 +- product_docs/docs/efm/4/03_installing_efm.mdx | 8 ++++---- .../02_encrypting_database_password.mdx | 2 +- product_docs/docs/efm/4/05_using_efm.mdx | 14 +++++++------- .../docs/efm/4/08_controlling_efm_service.mdx | 6 +++--- .../docs/efm/4/12_upgrading_existing_cluster.mdx | 2 +- product_docs/docs/efm/4/efm_quick_start/index.mdx | 2 +- 12 files changed, 34 insertions(+), 34 deletions(-) diff --git a/product_docs/docs/efm/3/efm_quick_start/index.mdx b/product_docs/docs/efm/3/efm_quick_start/index.mdx index 6e799209816..f2346efa378 100644 --- a/product_docs/docs/efm/3/efm_quick_start/index.mdx +++ b/product_docs/docs/efm/3/efm_quick_start/index.mdx @@ -107,7 +107,7 @@ Copy the `efm.properties` and `efm.nodes` files to the `/etc/edb/efm-3.10` direc **Step 6: Start the EFM Cluster** -On any node, start the Failover Manager agent. The agent is named `edb-efm-3.10`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/RHEL 8.x host use the command: +On any node, start the Failover Manager agent. The agent is named `edb-efm-3.10`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host use the command: ```text systemctl start edb-efm-3.10 diff --git a/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx b/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx index 80bf6f783cf..6b25fe242f5 100644 --- a/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx +++ b/product_docs/docs/efm/3/efm_user/03_installing_efm.mdx @@ -18,7 +18,7 @@ To request credentials that allow you to access an EnterpriseDB repository, visi -## RedHat/CentOS/Rocky Linux Host +## RedHat/CentOS/Rocky Linux/AlmaLinux Host When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter y, and press Return to continue. @@ -111,7 +111,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co yum -y install edb-efm310 ``` -### RHEL or Rocky Linux 8 Host +### RHEL or Rocky Linux or AlmaLinux 8 Host 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: ```text @@ -126,7 +126,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 3. Install the EPEL repository: -- On Rocky Linux 8 +- On Rocky Linux 8 or AlmaLinux 8 ```text dnf -y install epel-release ``` @@ -137,7 +137,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 4. Enable the additional repositories to resolve dependencies: -- On Rocky Linux 8 +- On Rocky Linux 8 or AlmaLinux 8 ```text dnf config-manager --set-enabled PowerTools ``` diff --git a/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx b/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx index 0214183045a..cbc9f5d07b2 100644 --- a/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx +++ b/product_docs/docs/efm/3/efm_user/04_configuring_efm/01_cluster_properties/01_encrypting_database_password.mdx @@ -57,7 +57,7 @@ Job for edb-efm-3.10.service failed because the control process exited with erro If you receive this message when starting the Failover Manager service, please see the startup log (located in `/var/log/efm-3.10/startup-efm.log`) for more information. -If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, startup information is also available with the following command: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, startup information is also available with the following command: ```text systemctl status edb-efm-3.10 diff --git a/product_docs/docs/efm/3/efm_user/05_using_efm.mdx b/product_docs/docs/efm/3/efm_user/05_using_efm.mdx index 76ab7be92da..caf0d0c4450 100644 --- a/product_docs/docs/efm/3/efm_user/05_using_efm.mdx +++ b/product_docs/docs/efm/3/efm_user/05_using_efm.mdx @@ -36,7 +36,7 @@ By default, [some of the efm commands](07_using_efm_utility/#using_efm_utility) You can start the nodes of a Failover Manager cluster in any order. -To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: +To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges, and invoke the command: ```text systemctl start edb-efm-3.10 @@ -71,7 +71,7 @@ You can add a node to a Failover Manager cluster at any time. When you add a nod 2. Configure the cluster members file on the new node, adding an entry for the Membership Coordinator. For more information about modifying the cluster members file, see [The Cluster Members File](04_configuring_efm/03_cluster_members/#cluster_members). -3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, invoke the command: +3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, invoke the command: ```text systemctl start edb-efm-3.10 @@ -174,7 +174,7 @@ For more information about the efm utility, see [Using the EFM Utility](07_using When you stop an agent, Failover Manager will remove the node's address from the cluster members list on all of the running nodes of the cluster, but will not remove the address from the Failover Manager Allowed node host list. -To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: +To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges, and invoke the command: ```text systemctl stop edb-efm-3.10 @@ -218,7 +218,7 @@ You can monitor multiple database clusters that reside on the same host by runni 1. Create a cluster properties file for each member of each cluster that defines a unique set of properties and the role of the node within the cluster. 2. Create a cluster members file for each member of each cluster that lists the members of the cluster. -3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. +3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. 4. Start the services for each cluster. The examples that follow uses two database clusters (acctg and sales) running on the same node: @@ -274,14 +274,14 @@ The following parameters are used when assigning the virtual IP address to a nod This parameter value is determined by the virtual IP addresses being used and may or may not be the same for both `acctg.properties` and `sales.properties`. -After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files; this step is platform specific. If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x](#rhelcentos-7x-or-rhelcentos-8x). +After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files; this step is platform specific. If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x](#rhelcentos-7x-or-rhelcentos-8x). !!! Note If you are using a unit file, you must manually update the file to reflect the new service name when you upgrade Failover Manager. -### RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x +### RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, you should copy the `edb-efm-3.10` unit file to new file with a name that is unique for each cluster. For example, if you have two clusters (named acctg and sales), the unit file names might be: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you should copy the `edb-efm-3.10` unit file to new file with a name that is unique for each cluster. For example, if you have two clusters (named acctg and sales), the unit file names might be: ```text /usr/lib/systemd/system/efm-acctg.service diff --git a/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx b/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx index 70c5a18f0a4..d2286f26c56 100644 --- a/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx +++ b/product_docs/docs/efm/3/efm_user/08_controlling_efm_service.mdx @@ -23,11 +23,11 @@ The commands that control the Failover Manager service are platform-specific. -## Using the systemctl Utility on RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x +## Using the systemctl Utility on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x -On RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-3.10.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager will run a copy of the service on each node of the replication cluster. +On RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-3.10.service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager will run a copy of the service on each node of the replication cluster. -Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x host: +Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x host: ```text systemctl start edb-efm-3.10 diff --git a/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx b/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx index 4eecccff627..7bce8d90687 100644 --- a/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx +++ b/product_docs/docs/efm/3/efm_user/12_upgrading_existing_cluster.mdx @@ -63,7 +63,7 @@ After upgrading to Failover Manager 3.10, you can use your native package manage yum remove edb-efm39 ``` -- On RHEL or Rocky Linux 8.x: +- On RHEL or Rocky Linux or AlmaLinux 8.x: ```text dnf remove edb-efm39 diff --git a/product_docs/docs/efm/4/03_installing_efm.mdx b/product_docs/docs/efm/4/03_installing_efm.mdx index 3a11a226170..92e21f19a34 100644 --- a/product_docs/docs/efm/4/03_installing_efm.mdx +++ b/product_docs/docs/efm/4/03_installing_efm.mdx @@ -20,7 +20,7 @@ For information about the platforms and versions supported by Failover Manager, To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://info.enterprisedb.com/rs/069-ALB-339/images/Repository%20Access%2004-09-2019.pdf). -## RedHat/CentOS/Rocky Linux host +## RedHat/CentOS/Rocky Linux/AlmaLinux host When you install an RPM package that is signed by a source that isn't recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press **Return** to continue. @@ -30,7 +30,7 @@ Failover Manager must be installed by root. During the installation process, the After receiving your credentials, you must create the EnterpriseDB repository configuration file on each node of the cluster and then modify the file to enable access. -### RHEL Rocky Linux 8 x86-64 host +### RHEL/Rocky Linux/AlmaLinux 8 x86-64 host 1. To create the repository configuration file, assume superuser privileges and invoke the following command: ```text @@ -45,7 +45,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 3. Install the EPEL repository: -- On Rocky Linux 8 +- On Rocky Linux 8 or AlmaLinux 8 ```text dnf -y install epel-release ``` @@ -56,7 +56,7 @@ After receiving your credentials, you must create the EnterpriseDB repository co 4. Enable the additional repositories to resolve dependencies: -- On Rocky Linux 8 +- On Rocky Linux 8 or AlmaLinux 8 ```text dnf config-manager --set-enabled PowerTools ``` diff --git a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx index ac5757538c7..63a18c3501f 100644 --- a/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx +++ b/product_docs/docs/efm/4/04_configuring_efm/02_encrypting_database_password.mdx @@ -55,7 +55,7 @@ Job for edb-efm-4.4.service failed because the control process exited with error If you receive this message when starting the Failover Manager service, see the startup log `/var/log/efm-4.4/startup-efm.log` for more information. -If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, startup information is also available with the following command: +If you are using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, startup information is also available with the following command: ```text systemctl status edb-efm-4.4 diff --git a/product_docs/docs/efm/4/05_using_efm.mdx b/product_docs/docs/efm/4/05_using_efm.mdx index af7a7334502..fac3a88a11f 100644 --- a/product_docs/docs/efm/4/05_using_efm.mdx +++ b/product_docs/docs/efm/4/05_using_efm.mdx @@ -34,7 +34,7 @@ By default, [some of the efm commands](07_using_efm_utility/#using_efm_utility) You can start the nodes of a Failover Manager cluster in any order. -To start the Failover Manager cluster on RHEL/Rocky Linux 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges, and invoke the command: +To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges, and invoke the command: `systemctl start edb-efm-4.` @@ -66,7 +66,7 @@ You can add a node to a Failover Manager cluster at any time. When you add a nod 2. Configure the cluster members file on the new node, adding an entry for the membership coordinator. For more information about modifying the cluster members file, see [The cluster members file](04_configuring_efm/03_cluster_members/#cluster_members). -3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, invoke the command: +3. Assume superuser privileges on the new node, and start the Failover Manager agent. To start the Failover Manager cluster on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, invoke the command: `systemctl start edb-efm-4.` @@ -162,7 +162,7 @@ For more information about the efm utility, see [Using the efm utility](07_using When you stop an agent, Failover Manager removes the node's address from the cluster members list on all of the running nodes of the cluster but doesn't remove the address from the Failover Manager Allowed node host list. -To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, assume superuser privileges and invoke the command: +To stop the Failover Manager agent on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, assume superuser privileges and invoke the command: `systemctl stop edb-efm-4.` @@ -200,7 +200,7 @@ You can monitor multiple database clusters that reside on the same host by runni 1. Create a cluster properties file for each member of each cluster that defines a unique set of properties and the role of the node within the cluster. 2. Create a cluster members file for each member of each cluster that lists the members of the cluster. -3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. +3. Customize the unit file (on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system) for each cluster to specify the names of the cluster properties and the cluster members files. 4. Start the services for each cluster. These examples use two database clusters (acctg and sales) running on the same node: @@ -256,14 +256,14 @@ Use the following parameters when assigning the virtual IP address to a node. If This parameter value is determined by the virtual IP addresses being used and can be the same for both `acctg.properties` and `sales.properties`. -After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x](#rhelcentos-7x-or-rhelcentos-8x). +After creating the `acctg.properties` and `sales.properties` files, create a service script or unit file for each cluster that points to the respective property files. This step is platform specific. If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, see [RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x](#rhelcentos-7x-or-rhelcentos-8x). !!! Note If you're using a unit file, manually update the file to reflect the new service name when you upgrade Failover Manager. -### RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x +### RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux 8.x, copy the `edb-efm-4.` unit file to a new file with a name that is unique for each cluster. For example, if you have two clusters named acctg and sales, the unit file names might be: +If you're using RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, copy the `edb-efm-4.` unit file to a new file with a name that is unique for each cluster. For example, if you have two clusters named acctg and sales, the unit file names might be: ```text /usr/lib/systemd/system/efm-acctg.service diff --git a/product_docs/docs/efm/4/08_controlling_efm_service.mdx b/product_docs/docs/efm/4/08_controlling_efm_service.mdx index e87afff3dcf..8edc34eac79 100644 --- a/product_docs/docs/efm/4/08_controlling_efm_service.mdx +++ b/product_docs/docs/efm/4/08_controlling_efm_service.mdx @@ -21,11 +21,11 @@ The commands that control the Failover Manager service are platform specific. -## Using the systemctl utility on RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x +## Using the systemctl utility on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x -On RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-4..service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster. +On RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x, Failover Manager runs as a Linux service named (by default) `edb-efm-4..service` that is located in `/usr/lib/systemd/system`. Each database cluster monitored by Failover Manager runs a copy of the service on each node of the replication cluster. -Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux 8.x host: +Use the following systemctl commands to control a Failover Manager agent that resides on a RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x host: `systemctl start edb-efm-4.` diff --git a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx index e557344fd6f..35512b33ede 100644 --- a/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx +++ b/product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx @@ -70,7 +70,7 @@ After upgrading to Failover Manager 4.4, you can use your native package manager yum remove edb-efm41 ``` -- On RHEL or Rocky Linux 8.x: +- On RHEL or Rocky Linux or AlmaLinux 8.x: ```text dnf remove edb-efm41 diff --git a/product_docs/docs/efm/4/efm_quick_start/index.mdx b/product_docs/docs/efm/4/efm_quick_start/index.mdx index 6b93ae0219a..5d2c200d9a4 100644 --- a/product_docs/docs/efm/4/efm_quick_start/index.mdx +++ b/product_docs/docs/efm/4/efm_quick_start/index.mdx @@ -88,7 +88,7 @@ Start the configuration process on a primary or standby node. Then, copy the con - Modify the `bind.address` property to use the node’s local address. - Set `is.witness` to `true` if the node is a witness node. If the node is a witness node, the properties relating to a local database installation are ignored. -1. Start the Failover Manager cluster. On any node, start the Failover Manager agent. The agent is named `edb-efm-4.4`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/RHEL 8.x host, use the command: +1. Start the Failover Manager cluster. On any node, start the Failover Manager agent. The agent is named `edb-efm-4.4`; you can use your platform-specific service command to control the service. For example, on a CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host, use the command: ```text systemctl start edb-efm-4.4 From 9a8e6caed1f913cfa1f2e83ac9aa51953ddf62e9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 06:09:49 -0500 Subject: [PATCH 75/97] Added AlmaLinux --- .../eprs/6.2/01_introduction/04_supported_jdk_versions.mdx | 2 +- .../eprs/6.2/03_installation/03_installing_rpm_package.mdx | 2 +- .../03_installation/05_post_installation_host_environment.mdx | 4 ++-- .../01_prerequisites/06_verifying_host_accessibility.mdx | 2 +- .../01_registering_subscription_server.mdx | 2 +- .../index.mdx | 2 +- .../eprs/7.0/01_introduction/04_supported_jdk_versions.mdx | 2 +- .../eprs/7.0/03_installation/03_installing_rpm_package.mdx | 2 +- .../03_installation/05_post_installation_host_environment.mdx | 4 ++-- .../01_prerequisites/06_verifying_host_accessibility.mdx | 2 +- .../01_registering_subscription_server.mdx | 2 +- .../index.mdx | 2 +- 12 files changed, 14 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx index ee9cb3987f4..eb6e9c93394 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/04_supported_jdk_versions.mdx @@ -8,7 +8,7 @@ The xDB Replication Server is certified to work with the following Java platform | **Operating Systems** | **JDK Versions** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -| `CentOS 7 and Rocky Linux 8`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| +| `CentOS 7 and Rocky Linux/AlmaLinux 8`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
| | `PPCLE RHEL 8` | Red Hat OpenJDK 8 | | `PPCLE RHEL7` | Red Hat OpenJDK 8 | | `RHEL 7`
| - Red Hat OpenJDK 7
- Red Hat OpenJDK 8
- Oracle JDK 7
- Oracle JDK 8
| diff --git a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx index 691f99b6d53..b1085015661 100644 --- a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx @@ -82,7 +82,7 @@ As the `root` account, run the following command to install this repository conf > `yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` -**On RHEL or Rocky Linux 8:** +**On RHEL or Rocky Linux or AlmaLinux 8:** > `dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` diff --git a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx index 34b66c37485..6860f2b84d1 100644 --- a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx @@ -24,9 +24,9 @@ The following files are created that you may need during the configuration proce | `edb-repl.conf` (Linux) | `/etc` | xDB Replication Configuration file | | `edb-repl.conf` (Windows) | `XDB_HOME\etc` | xDB Replication Configuration file | | `edb-xdbpubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the publication server | -| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | +| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) | | `edb-xdbsubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the subscription server | -| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | +| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux, RHEL 8) | | `xdb_pubserver.conf` | `XDB_HOME/etc` | Publication server configuration file | | `xdb_subserver.conf` | `XDB_HOME/etc` | Subscription server configuration file | | `xdbReplicationServer-xx.config` | `XDB_HOME/etc/sysconfig` | xDB Startup Configuration file | diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index 3250512fe30..f421bc5b056 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -107,7 +107,7 @@ Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] ``` -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: `systemctl restart network` diff --git a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index e9c2a853eb0..a8543c57625 100644 --- a/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/6.2/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -13,7 +13,7 @@ It is important that you record the login information for the subscription serve !!! Note If you are using Oracle publication or subscription databases, and the subscription server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your xDB Replication Server installation, you must restart the subscription server. -**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. +**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. Use the Start or Restart link for the service named Subscription Service for xDB Replication Server. diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index e5e28584cf2..c0d721f8e74 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -41,7 +41,7 @@ nullReplacementChar = ? **Step 2:** Restart the publication or subscription server. -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlamLinux or RHEL 8: `systemctl restart edb-xdbpubserver` diff --git a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx index fa674b69218..5fb42904609 100644 --- a/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7.0/01_introduction/04_supported_jdk_versions.mdx @@ -8,7 +8,7 @@ The Replication Server is certified to work with the following Java platforms: | **Operating Systems** | **JDK Versions** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | -| `CentOS 7 and Rocky Linux 8`
| Red Hat OpenJDK 8
| +| `CentOS 7 and Rocky Linux/AlmaLinux 8`
| Red Hat OpenJDK 8
| | `SLES 12`
| Red Hat OpenJDK 8
| | `PPCLE RHEL 8` | Red Hat OpenJDK 8 | | `PPCLE RHEL 7` | Red Hat OpenJDK 8
| diff --git a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx index 2caaa478c72..824da85d987 100644 --- a/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/03_installing_rpm_package.mdx @@ -76,7 +76,7 @@ As the `root` account, run the following command to install this repository conf > `yum -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` -**On RHEL or Rocky Linux 8:** +**On RHEL or Rocky Linux or AlmaLinux 8:** > `dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/edb-repo-latest.noarch.rpm` diff --git a/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx index 11978aebb22..8eab285bc62 100644 --- a/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/7.0/03_installation/05_post_installation_host_environment.mdx @@ -24,9 +24,9 @@ The following files are created that you may need during the configuration proce | `edb-repl.conf` (Linux) | `/etc` | EPRS Replication Configuration file | | `edb-repl.conf` (Windows) | `XDB_HOME\etc` | EPRS Replication Configuration file | | `edb-xdbpubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the publication server | -| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | +| `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) | | `edb-xdbsubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the subscription server | -| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, RHEL 8) | +| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) | | `xdb_pubserver.conf` | `XDB_HOME/etc` | Publication server configuration file | | `xdb_subserver.conf` | `XDB_HOME/etc` | Subscription server configuration file | | `xdbReplicationServer-xx.config` | `XDB_HOME/etc/sysconfig` | Replication Server Startup Configuration file | diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index 85e87737f49..0e7cd6465cc 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -107,7 +107,7 @@ Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] ``` -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: `systemctl restart network` diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index 40918538925..b594d4fbbca 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -13,7 +13,7 @@ It is important that you record the login information for the subscription serve !!! Note If you are using Oracle publication or subscription databases, and the subscription server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, you must restart the subscription server. -**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. +**For Linux only:** Use the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8, and the service command for previous Linux versions to start, stop, or restart `edb-xdbsubserver` for the subscription server. See [Registering a Publication Server](../02_creating_publication/01_registering_publication_server/#registering_publication_server) for information on how these commands are used. **For Windows only:** Open Control Panel, System and Security, Administrative Tools, and then Services. Use the Start or Restart link for the service named Subscription Service for Replication Server. diff --git a/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index 61fb5d1cb0a..61b7945f44b 100644 --- a/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/7.0/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -41,7 +41,7 @@ nullReplacementChar = ? **Step 2:** Restart the publication or subscription server. -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: `systemctl restart edb-xdbpubserver` From 74305c7795a43f684ce6ccb25461ecb20a199b36 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 25 Jan 2022 06:33:57 -0500 Subject: [PATCH 76/97] Apply suggestions from code review Additional updates --- .../05_post_installation_host_environment.mdx | 2 +- .../index.mdx | 2 +- .../01_registering_publication_server.mdx | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx index 6860f2b84d1..d8df792109d 100644 --- a/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/05_post_installation_host_environment.mdx @@ -26,7 +26,7 @@ The following files are created that you may need during the configuration proce | `edb-xdbpubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the publication server | | `edb-xdbpubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the publication server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) | | `edb-xdbsubserver` (Linux) | `/etc/init.d` | Start, stop, or restart the subscription server | -| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux, RHEL 8) | +| `edb-xdbsubserver.service` (Linux) | `/usr/lib/systemd/system` | Start, stop, or restart the subscription server (CentOS 7, RHEL 7, Rocky Linux 8, AlmaLinux 8, RHEL 8) | | `xdb_pubserver.conf` | `XDB_HOME/etc` | Publication server configuration file | | `xdb_subserver.conf` | `XDB_HOME/etc` | Subscription server configuration file | | `xdbReplicationServer-xx.config` | `XDB_HOME/etc/sysconfig` | xDB Startup Configuration file | diff --git a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index c0d721f8e74..1db33af723f 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -41,7 +41,7 @@ nullReplacementChar = ? **Step 2:** Restart the publication or subscription server. -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlamLinux or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: `systemctl restart edb-xdbpubserver` diff --git a/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx b/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx index c48a8a6d06b..2bc5a2e6135 100644 --- a/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx +++ b/product_docs/docs/eprs/7.0/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx @@ -13,9 +13,9 @@ It is important that you record the login information for the publication server !!! Note If you are using Oracle publication or subscription databases, and the publication server has not been restarted since copying the Oracle JDBC driver to the `lib/jdbc` subdirectory of your Replication Server installation, you must restart the publication server. -**For Linux only:** You can verify the publication server is running by using the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux or RHEL 8, and the service command for previous Linux versions. +**For Linux only:** You can verify the publication server is running by using the `systemctl` command for CentOS 7 or RHEL 7 and Rocky Linux, AlmaLinux, or RHEL 8, and the service command for previous Linux versions. -Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +Use the following command for CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: ```text systemctl status edb-xdbpubserver @@ -29,7 +29,7 @@ service edb-xdbpubserver status If the publication server is running and you wish to restart it, use the restart option. -For CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: ```text systemctl restart edb-xdbpubserver @@ -43,7 +43,7 @@ service edb-xdbpubserver restart If the publication server is not running, use the start option. -For CentOS 7 or RHEL 7 and Rocky Linux 8 or RHEL 8: +For CentOS 7 or RHEL 7 and Rocky Linux 8 or AlmaLinux 8 or RHEL 8: ```text systemctl start edb-xdbpubserver From b48cc8f7edf593aaf54da7875e2a4df1b7292dad Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 06:51:55 -0500 Subject: [PATCH 77/97] added AlmaLinux --- .../migration_toolkit/54/05_installing_mtk.mdx | 16 ++++++++-------- .../migration_toolkit/55/05_installing_mtk.mdx | 14 +++++++------- .../2.7.0/02_requirements_overview.mdx | 2 +- .../04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.7.0/05_updating_the_mysql_data_adapter.mdx | 2 +- .../12_uninstalling_the_mysql_data_adapter.mdx | 2 +- 6 files changed, 20 insertions(+), 20 deletions(-) diff --git a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx index 039b5f38bda..db46fc08e35 100644 --- a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx @@ -23,7 +23,7 @@ To install Migration Toolkit, you must have credentials that allow access to the The following are the various installation methods: -- [Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL Host](#rpm_installation) +- [Installing Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL Host](#rpm_installation) - [Installing Migration Toolkit on a CentOS, or RHEL 7 ppc64le Host](#rhel_centos_ppcle_installation) - [Installing Migration Toolkit on a Debian or Ubuntu Host](#debian_or_ubuntu_installation) - [Installing Migration Toolkit on a SLES Host](#sles_installation) @@ -32,22 +32,22 @@ The following are the various installation methods: -## Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL 7 and 8 Host +## Installing Migration Toolkit on a CentOS/RHEL 7 and RHEL/Rocky Linux/AlmaLinux 8 Host -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. **Creating a Repository Configuration File** 1. To create the repository configuration file, assume superuser privileges and invoke the following command: -- On RHEL or CentOs 7: +- On RHEL or CentOS 7: ```text yum -y install https://yum.enterprisedb.com/edb-repo-rpms/ edb-repo-latest.noarch.rpm ``` -- On RHEL or CentOs 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edb-repo-rpms/ @@ -78,16 +78,16 @@ You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/ epel-release-latest-7.noarch.rpm ``` -- On RHEL or Centos 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install https://dl.fedoraproject.org/pub/epel/ epel-release-latest-8.noarch.rpm ``` -4. If you are using RHEL or Rocky Linux 8.x, you must enable an additional repository to resolve dependencies: +4. If you are using RHEL or Rocky Linux or AlmaLinux 8.x, you must enable an additional repository to resolve dependencies: -- On Rocky Linux 8 (Powertools repo): +- On Rocky Linux or AlmaLinux 8 (Powertools repo): ```text dnf config-manager --set-enabled PowerTools diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx index a43fc6f6cbc..a737cd8c46a 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx @@ -20,7 +20,7 @@ To install Migration Toolkit, you must have credentials that allow access to the The following are the various installation methods: -- [Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL Host](#rpm_installation) +- [Installing Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL Host](#rpm_installation) - [Installing Migration Toolkit on a RHEL 7 or 8 ppc64le Host](#installing-migration-toolkit-on-a-rhel-7-or-8-ppc64le-host) - [Installing Migration Toolkit on a Debian or Ubuntu Host](#debian_or_ubuntu_installation) - [Installing Migration Toolkit on a SLES Host](#sles_installation) @@ -29,9 +29,9 @@ The following are the various installation methods: -## Installing Migration Toolkit on a CentOS/Rocky Linux/RHEL 7 and 8 Host +## Installing Migration Toolkit on a CentOS/RHEL 7 and Rocky Linux/AlmaLinux/RHEL 8 Host -You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. +You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/AlmaLinux/RHEL host. The following steps provide detailed information about accessing the EnterpriseDB repository and installing Migration Toolkit. **Creating a Repository Configuration File** @@ -82,9 +82,9 @@ You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/ epel-release-latest-8.noarch.rpm ``` -4. If you are using RHEL or Rocky Linux 8.x, you must enable an additional repository to resolve dependencies: +4. If you are using RHEL or Rocky Linux or AlmaLinux 8.x, you must enable an additional repository to resolve dependencies: -- On Rocky Linux 8 (Powertools repo): +- On Rocky Linux 8 or AlmaLinux 8 (Powertools repo): ```text dnf config-manager --set-enabled PowerTools @@ -100,13 +100,13 @@ You can use an RPM package to install Migration Toolkit on a CentOS/Rocky Linux/ **Installing Migration Toolkit** -- On RHEL or CentOs 7: +- On RHEL or CentOS 7: ```text yum -y install edb-migrationtoolkit ``` -- On RHEL or CentOs 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install edb-migrationtoolkit diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx index b4d76583c8b..fa8a130f318 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx @@ -14,7 +14,7 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. - RHEL 8.x/7.x - CentOS 7.x -- Rocky Linux 8.x +- Rocky Linux/AlmaLinux 8.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx index 01dc6088998..e04bbbe2d01 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -311,7 +311,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx index cf79c1a23ba..c55733f3c5e 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx @@ -14,7 +14,7 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can ```text sudo yum -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` - - On RHEL or Rocky Linux 8: + - On RHEL or Rocky Linux or AlmaLinux 8: ```text sudo dnf -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx index cd52d6c158b..a290dbfea07 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ Where `xx` is the server version number, and `x` is the supported release versio `yum remove edb-as-mysql5_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mysql8_fdw` From 443733c7e5df6725d5403c6d106a63f40caa58aa Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 7 Jan 2022 14:59:54 -0500 Subject: [PATCH 78/97] first draft of MySQL FDW updates for RHEL 8 Power --- .../2.7.0/02_requirements_overview.mdx | 5 +- .../04_installing_the_mysql_data_adapter.mdx | 323 ++++++++++++++---- 2 files changed, 261 insertions(+), 67 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx index fa8a130f318..420288c0268 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx @@ -29,6 +29,7 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. - Ubuntu 18.04 LTS - Debian 10.x/9.x -**Linux on IBM Power8/9 (LE)** +**Linux on IBM Power (ppc64le)** -- RHEL 7.x +- RHEL 8 +- RHEL 7 diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx index e04bbbe2d01..1969a35cd43 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx @@ -4,41 +4,44 @@ title: "Installing the MySQL Foreign Data Wrapper" -The MySQL Foreign Data Wrapper can be installed with an RPM package. During the installation process, the installer will satisfy software prerequisites. + -## Installing the MySQL Foreign Data Wrapper using an RPM Package +## Installing on Linux x86-64 (amd64) -You can install the MySQL Foreign Data Wrapper using an RPM package on the following platforms: +You can install the MySQL Foreign Data Wrapper on the following operating systems: -- [RHEL 7](#rhel7) -- [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) +- [RHEL 7](#rhel7) +- [Rocky Linux/AlmaLinux](#centos8) - [CentOS 7](#centos7) -- [Rocky Linux/AlmaLinux 8](#centos8) +- [Ubuntu/Debian](#on-debian-or-ubuntu) - -### On RHEL 7 + + + +### On RHEL 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: Install the `epel-release` package: ```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm +dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -Enable the optional, extras, and HA repositories: +Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: ```text -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" +ARCH=$( /bin/arch ) +subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" ``` You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - + After receiving your repository credentials you can: @@ -51,7 +54,7 @@ After receiving your repository credentials you can: To create the repository configuration file, assume superuser privileges, and invoke the following command: ```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. @@ -69,64 +72,40 @@ gpgcheck=1 repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` - **Installing MySQL Foreign Data Wrapper** -1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: - - ```text - yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm - ``` +After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: -2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: - - For MySQL 8: - ```text - yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw - ``` - - For MySQL 5: - ```text - yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw - ``` +```text +dnf install edb-as-mysql8_fdw +``` Where `xx` is the server version number i.e. 13. When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - + -### On RHEL 7 PPCLE +### On RHEL 7 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: -1. Use the following commands to install Advance Toolchain: -```text -rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b -cat > /etc/yum.repos.d/advance-toolchain.repo < + After receiving your repository credentials you can: @@ -160,22 +139,34 @@ gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY **Installing MySQL Foreign Data Wrapper** -Use the following command to install the MySQL Foreign Data Wrapper: - ```text - yum install edb-as-mysql5_fdw +1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: + + ```text + yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm ``` -where `xx` is the server version number i.e. 13. - !!! Note - MySQL 8.0 RPMs are not available for CentOS 7 PPCLE platform. +2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: + - For MySQL 8: + ```text + yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw + ``` + - For MySQL 5: + ```text + yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw + ``` +Where `xx` is the server version number i.e. 13. When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - -### On RHEL 8 + + + + + +### On CentOS 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: @@ -185,16 +176,15 @@ Install the `epel-release` package: dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: +Enable the `PowerTools` repository: ```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" +dnf config-manager --set-enabled PowerTools ``` You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - + After receiving your repository credentials you can: @@ -207,7 +197,7 @@ After receiving your repository credentials you can: To create the repository configuration file, assume superuser privileges, and invoke the following command: ```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. @@ -225,9 +215,10 @@ gpgcheck=1 repo_gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY ``` + **Installing MySQL Foreign Data Wrapper** -After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: +After saving your changes to the configuration file, use the following command to install the MySQL Foreign Data Wrapper: ```text dnf install edb-as-mysql8_fdw @@ -238,7 +229,6 @@ When you install an RPM package that is signed by a source that is not recognize During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - ### On CentOS 7 @@ -473,8 +463,211 @@ The following steps will walk you through on using the EDB apt repository to ins ``` Where `xx` is the server version number i.e. 13 and `y` is the MySQL version i.e. 5 or 8. +## Installing on IBM Power (ppc64le) + +You can install the Hadoop Foreign Data Wrapper on the following operating systems on IBM Power (ppc64le): + + - [RHEL 8](#on-rhel-8-1) + - [RHEL 7](#centos7_PPCLE) + +### On RHEL 8 +There are two steps to completing an installation: + +- Setting up the repository +- Installing the package + +For each step, you must be logged in as superuser. + +To log in as a superuser: + +```sh +sudo su - +``` + +#### Setting up the Repository + +1. To register with EDB to receive credentials for the EDB repository, visit: [Repository Access Request](https://www.enterprisedb.com/repository-access-request). + +1. Set up the EDB repository: + + ```sh + dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm + ``` + + This creates the /etc/yum.repos.d/edb.repo configuration file. + +1. Add your EDB credentials to the edb.repo file: + + ```sh + sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + + Where `USERNAME:PASSWORD` is the username and password available from your + [EDB account](https://www.enterprisedb.com/user). + +1. Install the EPEL repository and refresh the cache: + + ```sh + dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm + dnf makecache + ``` + +1. Enable the codeready-builder-for-rhel-8-\*-rpms repository since EPEL packages may depend on packages from it: + + ```sh + ARCH=$( /bin/arch ) + subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" + ``` + +1. Disable the built-in PostgreSQL module: + ```sh + dnf -qy module disable postgresql + ``` + +#### Installing the Package + +```sh +dnf -y install edb-as-mysql8_fdw +``` + +where `xx` is the server version number. + + + +### On RHEL 7 + +1. Use the following command to create a configuration file and install Advance Toolchain: + + ```text + rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + cat > /etc/yum.repos.d/advance-toolchain.repo <:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo + ``` + +4. Install the EPEL repository: + + ```text + yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm + ``` + +5. On RHEL 7 PPCLE, enable the additional repositories to resolve EPEL dependencies: + + ```text + subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" + ``` + +6. Install the selected package: + + ```text + dnf install edb-as-mongo_fdw + ``` + + where `xx` is the server version number. + + + +### On RHEL 7 PPCLE + +Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: +1. Use the following commands to install Advance Toolchain: +```text +rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b + +cat > /etc/yum.repos.d/advance-toolchain.repo < + +After receiving your repository credentials you can: + +1. Create the repository configuration file. +2. Modify the file, providing your user name and password. +3. Install the MySQL Foreign Data Wrapper. + +**Creating a Repository Configuration File** + +To create the repository configuration file, assume superuser privileges, and invoke the following command: + +```text +yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm +``` + +The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. + +**Modifying the file, providing your user name and password** + +After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. + +```text +[edb] +name=EnterpriseDB RPMs $releasever - $basearch +baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch +enabled=1 +gpgcheck=1 +repo_gpgcheck=1 +gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY +``` + +**Installing MySQL Foreign Data Wrapper** + +Use the following command to install the MySQL Foreign Data Wrapper: + ```text + yum install edb-as-mysql5_fdw + ``` +where `xx` is the server version number i.e. 13. + +!!! Note + MySQL 8.0 RPMs are not available for CentOS 7 PPCLE platform. + +When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. + +During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. + + From a5b880c0a6ab940b68b318820d2dbc4350b53a3f Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 8 Jan 2022 06:47:43 -0500 Subject: [PATCH 79/97] Fixed platform support --- .../mysql_data_adapter/2.7.0/02_requirements_overview.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx index 420288c0268..6d1fb25011d 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx @@ -19,6 +19,11 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x +**Linux on IBM Power (ppc64le)** + +- RHEL 8 + + ### The MySQL Foreign Data Wrapper is supported for MySQL 5 on the following platforms: **Linux x86-64** @@ -31,5 +36,4 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. **Linux on IBM Power (ppc64le)** -- RHEL 8 - RHEL 7 From 964644b1bee58dbd4c6445ead1cc64946da71b84 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sun, 23 Jan 2022 10:47:43 -0500 Subject: [PATCH 80/97] CentOS 8 > Rocky Linux for older versions --- .../2.5.5/02_requirements_overview.mdx | 11 ++++++----- .../2.5.5/04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.5.5/05_updating_the_mysql_data_adapter.mdx | 14 +++++++------- .../11_uninstalling_the_mysql_data_adapter.mdx | 2 +- .../2.6.0/02_requirements_overview.mdx | 3 ++- .../2.6.0/04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.6.0/05_updating_the_mysql_data_adapter.mdx | 2 +- .../12_uninstalling_the_mysql_data_adapter.mdx | 2 +- 8 files changed, 22 insertions(+), 20 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx index 4617fdab475..8afc0a77f5e 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx @@ -15,11 +15,12 @@ The MySQL Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** -> - RHEL 8.x/7.x -> - CentOS 8.x/7.x -> - OL 8.x/7.x -> - Ubuntu 20.04/18.04 LTS -> - Debian 10.x/9.x + - RHEL 8.x/7.x + - Rocky Linux 8.x + - CentOS 7.x + - OL 8.x/7.x + - Ubuntu 20.04/18.04 LTS + - Debian 10.x/9.x **Linux on IBM Power8/9 (LE)** diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx index 8f9cd230f18..7b1c888d5b7 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -226,7 +226,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx index 962cbf3d2c6..35c5a6c0620 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx @@ -10,25 +10,25 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can - On RHEL or CentOS 7: - > `yum upgrade edb-repo` + `yum upgrade edb-repo` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: - > `dnf upgrade edb-repo` + `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 any installed packages: - On RHEL or CentOS 7: - > `yum upgrade edb-as-mysql_fdw` + `yum upgrade edb-as-mysql_fdw` where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to upgrade MySQL 5.0 on RHEL 7: - > `yum upgrade edb-as-mysql5_fdw` + `yum upgrade edb-as-mysql5_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: - > `dnf upgrade edb-as-mysql8_fdw` + `dnf upgrade edb-as-mysql8_fdw` **Updating MongoDB Foreign Data Wrapper on a Debian or Ubuntu Host** diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx index 188ecceb2b0..64c4b0b9530 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > > > `yum remove edb-as-mysql5_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mysql8_fdw` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx index 76e502543e2..658cc2d4e22 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx @@ -13,7 +13,8 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. **Linux x86-64** - RHEL 8.x/7.x -- CentOS 8.x/7.x +- Rocky Linux 8.x +- CentOS 7.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx index ad0d3572656..01dc6088998 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [CentOS 8](#centos8) +- [Rocky Linux 8](#centos8) @@ -311,7 +311,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx index e0730522270..cf79c1a23ba 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx @@ -14,7 +14,7 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can ```text sudo yum -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` - - On RHEL or CentOS 8: + - On RHEL or Rocky Linux 8: ```text sudo dnf -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx index 1757e93c803..cd52d6c158b 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ Where `xx` is the server version number, and `x` is the supported release versio `yum remove edb-as-mysql5_fdw` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux 8: `dnf remove edb-as-mysql8_fdw` From 419443c398fdf627c9324597a4eddbcf82654209 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 07:29:45 -0500 Subject: [PATCH 81/97] Added AlmaLinux --- .../mysql_data_adapter/2.5.5/02_requirements_overview.mdx | 2 +- .../2.5.5/04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.5.5/05_updating_the_mysql_data_adapter.mdx | 4 ++-- .../2.5.5/11_uninstalling_the_mysql_data_adapter.mdx | 2 +- .../mysql_data_adapter/2.6.0/02_requirements_overview.mdx | 2 +- .../2.6.0/04_installing_the_mysql_data_adapter.mdx | 4 ++-- .../2.6.0/05_updating_the_mysql_data_adapter.mdx | 2 +- .../2.6.0/12_uninstalling_the_mysql_data_adapter.mdx | 2 +- 8 files changed, 11 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx index 8afc0a77f5e..76e3b9176e4 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx @@ -16,7 +16,7 @@ The MySQL Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x/7.x - - Rocky Linux 8.x + - Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx index 7b1c888d5b7..3f04e15e189 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -226,7 +226,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx index 35c5a6c0620..5952e4af7cc 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -26,7 +26,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-as-mysql5_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-as-mysql8_fdw` diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx index 64c4b0b9530..c9db724cc6a 100644 --- a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > > > `yum remove edb-as-mysql5_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mysql8_fdw` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx index 658cc2d4e22..2d8d28d2217 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx @@ -13,7 +13,7 @@ The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 9. **Linux x86-64** - RHEL 8.x/7.x -- Rocky Linux 8.x +- Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx index 01dc6088998..e04bbbe2d01 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the MySQL Foreign Data Wrapper using an RPM package on the follo - [RHEL 7 PPCLE](#centos7_PPCLE) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -311,7 +311,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx index cf79c1a23ba..c55733f3c5e 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx @@ -14,7 +14,7 @@ If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can ```text sudo yum -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` - - On RHEL or Rocky Linux 8: + - On RHEL or Rocky Linux or AlmaLinux 8: ```text sudo dnf -y upgrade edb-as-mysql8_fdw* mysql-community-devel ``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx index cd52d6c158b..a290dbfea07 100644 --- a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx @@ -16,7 +16,7 @@ Where `xx` is the server version number, and `x` is the supported release versio `yum remove edb-as-mysql5_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mysql8_fdw` From 5040c6cc1f7d78127c4a9c74f032762111d749dd Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 08:39:51 -0500 Subject: [PATCH 82/97] adjustments after rebase --- .../2.7.0/04_installing_the_mysql_data_adapter.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx index 1969a35cd43..07734f532da 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx +++ b/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter.mdx @@ -14,7 +14,7 @@ You can install the MySQL Foreign Data Wrapper on the following operating system - [RHEL 8](#rhel8) - [RHEL 7](#rhel7) -- [Rocky Linux/AlmaLinux](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) - [CentOS 7](#centos7) - [Ubuntu/Debian](#on-debian-or-ubuntu) @@ -166,7 +166,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On CentOS 8 +### On Rocky Linux/AlmaLinux 8 Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: From ce2b8771ec7942a4b8019ade014911bca431acac Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 08:57:02 -0500 Subject: [PATCH 83/97] added AlmaLinux --- .../mongo_data_adapter/5.2.8/02_requirements_overview.mdx | 2 +- .../5.2.8/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.8/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.8/11_uninstalling_the_mongo_data_adapter.mdx | 2 +- .../mongo_data_adapter/5.2.9/02_requirements_overview.mdx | 2 +- .../5.2.9/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.9/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../5.2.9/11_uninstalling_the_mongo_data_adapter.mdx | 2 +- .../mongo_data_adapter/5.3.0/02_requirements_overview.mdx | 2 +- .../5.3.0/04_installing_the_mongo_data_adapter.mdx | 4 ++-- .../5.3.0/05_updating_the_mongo_data_adapter.mdx | 4 ++-- .../5.3.0/11_uninstalling_the_mongo_data_adapter.mdx | 2 +- 12 files changed, 18 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx index 72393e6ea2a..35fff09fabe 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/02_requirements_overview.mdx @@ -16,7 +16,7 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x/7.x - - Rocky Linux 8.x + - Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx index 0868ce70219..8f4a3b68c4d 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/04_installing_the_mongo_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 Before installing the MongoDB Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx index b39260285ae..9245f7f3e7f 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/05_updating_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca > `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: > `dnf upgrade edb-repo` @@ -22,7 +22,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r > `yum upgrade edb-as-mongo_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: > `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx index c18c4d250c5..3d6dc8ce772 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.8/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx index ff10ce55df4..af558e99654 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/02_requirements_overview.mdx @@ -13,7 +13,7 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x/7.x - - Rocky Linux 8.x + - Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x/7.x - Ubuntu 20.04/18.04 LTS diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx index 372140873f0..8f2ce92d8c5 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/04_installing_the_mongo_data_adapter.mdx @@ -17,7 +17,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -189,7 +189,7 @@ You can install the MongoDB Foreign Data Wrapper using an RPM package on the fol -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx index 6f1898befab..d5924581f4f 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/05_updating_the_mongo_data_adapter.mdx @@ -16,7 +16,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -30,7 +30,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r `yum upgrade edb-as-mongo_fdw edb-libmongoc-libs` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx index e5fa5c65ef4..5312c8fb933 100644 --- a/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.2.9/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx index 22b7f9c354d..2a62b8aa28d 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/02_requirements_overview.mdx @@ -12,7 +12,7 @@ The MongoDB Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - - RHEL 8/Rocky Linux 8/OL 8 + - RHEL 8/Rocky Linux 8/AlmaLinux 8/OL 8 - RHEL 7/CentOS 7/OL 7 - Ubuntu 20.04/18.04 LTS - Debian 10.x/9.x diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx index 6b1e631b5df..4f3ff4bf64e 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/04_installing_the_mongo_data_adapter.mdx @@ -14,7 +14,7 @@ You can install the MongoDB Foreign Data Wrapper on the following operating syst - [RHEL 8](#rhel8) - [RHEL 7](#rhel7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) - [CentOS 7](#centos7) - [Ubuntu/Debian](#on-debian-or-ubuntu) @@ -106,7 +106,7 @@ You can install the MongoDB Foreign Data Wrapper on the following operating syst -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx index 0b5808d3a66..bbe9f385d73 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/05_updating_the_mongo_data_adapter.mdx @@ -16,7 +16,7 @@ If you have an existing RPM installation of MongoDB Foreign Data Wrapper, you ca `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -34,7 +34,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number and `yy` is Advance Toolchain major version number. For EDB Postgres Advanced Server versions 9.6 to 11, `yy` must be 10 and for EDB Postgres Advanced Server version 12 and later, `yy` must be 11. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-as-mongo_fdw` diff --git a/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx b/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx index e5fa5c65ef4..5312c8fb933 100644 --- a/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx +++ b/product_docs/docs/mongo_data_adapter/5.3.0/11_uninstalling_the_mongo_data_adapter.mdx @@ -12,7 +12,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install `yum remove edb-as-mongo_fdw` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-mongo_fdw` From 033c91ffd613d057d3ba5145f4e8e557f976bbf4 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 09:09:52 -0500 Subject: [PATCH 84/97] added AlmaLinux --- .../hadoop_data_adapter/2.0.7/02_requirements_overview.mdx | 2 +- .../2.0.7/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.7/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- .../hadoop_data_adapter/2.0.8/02_requirements_overview.mdx | 2 +- .../2.0.8/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.8/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- .../hadoop_data_adapter/2.1.0/02_requirements_overview.mdx | 2 +- .../2.1.0/05_installing_the_hadoop_data_adapter.mdx | 4 ++-- .../2.1.0/06_updating_the_hadoop_data_adapter.mdx | 4 ++-- .../2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx | 2 +- 12 files changed, 18 insertions(+), 18 deletions(-) diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx index 179e5089bab..abbac1739b2 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/02_requirements_overview.mdx @@ -16,7 +16,7 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x and 7.x - - Rocky Linux 8.x + - Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x and 7.x - Ubuntu 20.04 and 18.04 LTS diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx index c9391508451..7db147644b0 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/05_installing_the_hadoop_data_adapter.mdx @@ -18,7 +18,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -216,7 +216,7 @@ During the installation, yum may encounter a dependency that it cannot resolve. -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 Before installing the Hadoop Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx index 94ec393e182..1366440ad50 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can > `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: > `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: > `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx index 090fd306dc4..d30391031a0 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.7/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx index 820634fc433..3c68e256820 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/02_requirements_overview.mdx @@ -13,7 +13,7 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - RHEL 8.x and 7.x - - Rocky Linux 8.x + - Rocky Linux/AlmaLinux 8.x - CentOS 7.x - OL 8.x and 7.x - Ubuntu 20.04 and 18.04 LTS diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx index a1785889167..51b34673964 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/05_installing_the_hadoop_data_adapter.mdx @@ -16,7 +16,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll - [RHEL 7](#rhel7) - [RHEL 8](#rhel8) - [CentOS 7](#centos7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) @@ -190,7 +190,7 @@ You can install the Hadoop Foreign Data Wrapper using an RPM package on the foll -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx index 836367cb076..0c309f095c3 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx index 8644c6dac94..026a761c828 100644 --- a/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.0.8/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx index ee9ad75891d..dc3bc077efe 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/02_requirements_overview.mdx @@ -12,7 +12,7 @@ The Hadoop Foreign Data Wrapper is supported on the following platforms: **Linux x86-64** - - RHEL 8/Rocky Linux 8/OL 8 + - RHEL 8/Rocky Linux 8/AlmaLinux 8/OL 8 - RHEL 7/CentOS 7/OL 7 - Ubuntu 20.04 and 18.04 LTS - Debian 10.x and 9.x diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx index 790a6fcb817..f91ffbbccad 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/05_installing_the_hadoop_data_adapter.mdx @@ -13,7 +13,7 @@ You can install the Hadoop Foreign Data Wrapper on the following operating syste - [RHEL 8](#rhel8) - [RHEL 7](#rhel7) -- [Rocky Linux 8](#centos8) +- [Rocky Linux/AlmaLinux 8](#centos8) - [CentOS 7](#centos7) - [Ubuntu/Debian](#on-debian-or-ubuntu) @@ -98,7 +98,7 @@ You can install the Hadoop Foreign Data Wrapper on the following operating syste -### On Rocky Linux 8 +### On Rocky Linux/AlmaLinux 8 1. To create the repository configuration file, assume superuser privileges, and invoke the following command: diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx index 836367cb076..0c309f095c3 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/06_updating_the_hadoop_data_adapter.mdx @@ -12,7 +12,7 @@ If you have an existing RPM installation of Hadoop Foreign Data Wrapper, you can `yum upgrade edb-repo` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-repo` @@ -24,7 +24,7 @@ yum or dnf will update the `edb.repo` file to enable access to the current EDB r where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf upgrade edb-as-hdfs_fdw` diff --git a/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx b/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx index 8644c6dac94..026a761c828 100644 --- a/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx +++ b/product_docs/docs/hadoop_data_adapter/2.1.0/11_uninstalling_the_hadoop_data_adapter.mdx @@ -14,7 +14,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install > where `xx` is the server version number. -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: `dnf remove edb-as-hdfs_fdw` From 4cc67838a45241fd22a462bd125f83bc048cee0e Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 25 Jan 2022 11:25:41 -0500 Subject: [PATCH 85/97] Added AlmaLinux --- ...rerequisites_for_installing_pem_server.mdx | 2 +- .../03_installing_pem_server_on_linux.mdx | 10 +++---- .../06_installing_pem_agent_on_linux.mdx | 10 +++---- .../07_registering_a_pem_agent.mdx | 2 +- ...2_upgrading_pem_installation_linux_rpm.mdx | 16 +++++------ ...ading_pem_installation_linux_graphical.mdx | 28 +++++++++---------- .../02_upgrading_backend_database.mdx | 4 +-- ...rerequisites_for_installing_pem_server.mdx | 2 +- .../03_installing_pem_server_on_linux.mdx | 8 +++--- .../08_installing_pem_agent_on_linux.mdx | 10 +++---- .../09_registering_a_pem_agent.mdx | 2 +- .../06_uninstalling_pem_components.mdx | 6 ++-- ...2_upgrading_pem_installation_linux_rpm.mdx | 12 ++++---- 13 files changed, 56 insertions(+), 56 deletions(-) diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx index ee241d61eb9..48958059c7c 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx @@ -64,7 +64,7 @@ legacyRedirectsGenerated: yum upgrade ``` - To upgrade packages on a Rocky Linux or RHEL 8.x host + To upgrade packages on a Rocky Linux or AlmaLinux or RHEL 8.x host ```text dnf upgrade diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index 94d96411caa..13e0fa74a71 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -9,9 +9,9 @@ legacyRedirectsGenerated: Before following the detailed instructions that install the PEM server on your specific platform, you must perform the prerequisite steps detailed in [Prerequisites for installing PEM Server](01_prerequisites_for_installing_pem_server/#prerequisites_for_installing_pem_server). -## Installing the PEM Server on a CentOS or RHEL or Rocky Linux Host +## Installing the PEM Server on a CentOS or RHEL or Rocky Linux or AlmaLinux Host -On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux or AlmaLinux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. **Install Version-Specific Software** @@ -23,7 +23,7 @@ Follow the version-specific instructions listed below to prepare your host syste yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a Rocky Linux or RHEL 8.x host: +- On a Rocky Linux or AlmaLinux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -56,13 +56,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo After meeting the platform-specific prerequisites listed above, you can use `yum` or `dnf` to install the PEM Server: -- On CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x, you can use `yum` to install the PEM server : +- On CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x, you can use `yum` to install the PEM server : ```text yum install edb-pem ``` -- On Rocky Linux or RHEL 8.x, you can use `dnf` to install the PEM Server: +- On Rocky Linux/AlmaLinux/RHEL 8.x, you can use `dnf` to install the PEM Server: ```text dnf install edb-pem diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx index 8b62006f59b..7662a9f0c8b 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_installing_pem_agent_on_linux.mdx @@ -9,9 +9,9 @@ legacyRedirectsGenerated: A PEM Agent may monitor one or more servers on one or more hosts. For comprehensive information about managing a PEM Agent, see the [PEM Agent User Guide](https://www.enterprisedb.com/docs/pem/latest/pem_agent/). -## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux Host +## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux or AlmaLinux Host -On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux or AlmaLinux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. **Install Platform-Specific Software** @@ -21,7 +21,7 @@ On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a Rocky Linux or RHEL 8.x host: +- On a Rocky Linux or AlmaLinux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -52,13 +52,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo **Installing the PEM Agent** -- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x: +- Use the `yum install` command to install the PEM Agent on CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x: ```text yum install edb-pem-agent ``` -- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux or RHEL 8.x: +- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux/AlmaLinux/RHEL 8.x: ```text dnf install edb-pem-agent diff --git a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx index 18dae45f24e..22bf1e4a678 100644 --- a/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx +++ b/product_docs/docs/pem/7/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_registering_a_pem_agent.mdx @@ -60,7 +60,7 @@ By default, `heartbeat_connection` value is `false` but you can override the val Then, use a platform-specific command to start the PEM Agent service; -On a CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x host, use `systemctl` to start the service: +On a CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host, use `systemctl` to start the service: ```text systemctl start pemagent diff --git a/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx b/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx index 976ab5fc790..c90be9c8128 100644 --- a/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx +++ b/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx @@ -28,7 +28,7 @@ The following sections will walk you through the upgrade process on a Linux host PEM is dependent on third-party components from the vendor repository, including the python3, libboost, openssl, snmp++, libcurl, etc. To ensure these components are up to date, you should update your operating system using following platform-specific commands. Minimum version require for openssl is 1.0.2k. If you are using a version of PostgreSQL or Advanced Server older than version 10, before the upgrade you must install the `libs` package for version 10 or above on the system where the PEM server is installed. Use the following platform-specific commands to install the `libs` version 10 or above on your host: -### Prerequisites to Upgrade a PEM Installation on a CentOS or RHEL Host +### Prerequisites to Upgrade a PEM Installation on a CentOS or Rocky Linux or AlmaLinux or RHEL Host To upgrade packages on a CentOS or RHEL 7.x host @@ -36,7 +36,7 @@ To upgrade packages on a CentOS or RHEL 7.x host yum upgrade ``` -To upgrade packages on a CentOS or RHEL 8.x host +To upgrade packages on a Rocky Linux or AlmaLinux or RHEL 8.x host ```text dnf upgrade @@ -104,9 +104,9 @@ Where `` is the PostgreSQL or Advanced Server version whose `libs` package yo You can use native packages to upgrade existing PEM Agents that were initially installed using native packages. The upgrade process does not update the PEM agent configuration file. After installing the new agent, you must manually copy the configuration file of the existing agent to the new installation location. -### Upgrading the PEM Agent on a CentOS or RHEL Host +### Upgrading the PEM Agent on a CentOS or Rocky Linux or AlmaLinux or RHEL Host -For CentOS or RHEL 7.x or 8.x: +For CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x: To upgrade a PEM agent, use the following command: @@ -114,7 +114,7 @@ To upgrade a PEM agent, use the following command: yum upgrade edb-pem-agent ``` -For CentOS or RHEL 8.x, you can also use the following command: +For Rocky Linux or AlmaLinux or RHEL 8.x, you can also use the following command: ```text dnf upgrade edb-pem-agent @@ -142,17 +142,17 @@ If you initially used native packages to install your PEM server, you can use na If you wish to upgrade a PEM server that is installed on a machine in an isolated network, you need to create a PEM repository on that machine before you upgrade the PEM server. For more information about creating a PEM repository on an isolated network, see [Creating a PEM Repository on an Isolated Network](03_creating_pem_repository_in_isolated_network/#creating_pem_repository_in_isolated_network). -### Upgrading a PEM Server on a CentOS or RHEL Host +### Upgrading a PEM Server on a CentOS or Rocky Linux or AlmaLinux or RHEL Host To use an RPM package to upgrade an existing RPM installation you must: -You can use the `yum` package manager to upgrade the installed version of the PEM server on CentOS or RHEL 7.x or 8.x: +You can use the `yum` package manager to upgrade the installed version of the PEM server on CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x: ```text yum upgrade edb-pem ``` -You can also use the `dnf` command on CentOS or RHEL 8.x: +You can also use the `dnf` command on Rocky Linux/AlmaLinux/RHEL 8.x: ```text dnf upgrade edb-pem diff --git a/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/04_upgrading_pem_installation_linux_graphical.mdx b/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/04_upgrading_pem_installation_linux_graphical.mdx index f34635dea5c..1a7a2f6a7f7 100644 --- a/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/04_upgrading_pem_installation_linux_graphical.mdx +++ b/product_docs/docs/pem/7/pem_upgrade/01_upgrading_pem_installation/04_upgrading_pem_installation_linux_graphical.mdx @@ -48,7 +48,7 @@ The default installation location for the PEM Agent when installed by the graphi 1. Use the version specific command to stop the `pemagent` service. - On a CentOS or RHEL 7.x 0r 8.x host: + On a CentOS or RHEL 7.x or Rocky Linux or AlmaLinux or RHEL 8.x host: ```text systemctl stop pemagent @@ -98,7 +98,7 @@ The default installation location for the PEM Agent when installed by the graphi 4. The `yum makecache` command downloads the metadata for the currently enabled repositories; when the command completes, check the available packages to confirm that the list includes the latest PEM Agent: - On a CentOS or RHEL 7.x or 8.x: + On CentOS/RHEL 7.x: ```text yum makecache @@ -106,7 +106,7 @@ The default installation location for the PEM Agent when installed by the graphi yum list edb-pem-agent ``` - On a CentOS or RHEL 8.x: + On Rocky Linux or AlmaLinux or RHEL 8.x: ```text dnf makecache @@ -116,7 +116,7 @@ The default installation location for the PEM Agent when installed by the graphi 5. Install the PEM Agent RPM; when the installation completes, you can use the `yum info` command to confirm installation information for the PEM Agent: - On a CentOS or RHEL 7.x or 8.x: + On CentOS or RHEL 7.x: ```text yum install edb-pem-agent @@ -124,7 +124,7 @@ The default installation location for the PEM Agent when installed by the graphi yum info edb-pem-agent ``` - On a CentOS or RHEL 8.x: + On Rocky Linux or AlmaLinux or RHEL 8.x: ```text dnf install edb-pem-agent @@ -153,7 +153,7 @@ The default installation location for the PEM Agent when installed by the graphi b. Take a backup of the service file and agent certificates: - On CentOS or RHEL 7.x or 8.x, use the following command to back up the service file: + On CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x, use the following command to back up the service file: ```text cp /usr/lib/systemd/system/pemagent.service /usr/lib/systemd/system/pemagent.service_bkp @@ -175,7 +175,7 @@ The default installation location for the PEM Agent when installed by the graphi d. Use version specific commands to restore the service file backup and agent certificates to original location. For example: - On a RHEL or CentOS 7.x or 8.x host: + On a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host: ```text cp /usr/lib/systemd/system/pemagent.service_bkp /usr/lib/systemd/system/pemagent.service @@ -191,7 +191,7 @@ The default installation location for the PEM Agent when installed by the graphi 7. Enable the `pemagent` service, and start `pemagent` and `httpd`. - On a RHEL or CentOS 7.x or 8.x host, use the commands: + On a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host, use the commands: ```text systemctl enable pemagent @@ -214,7 +214,7 @@ The default installation location for the PEM server when installed by the graph 2. Stop the PEMHTTPD service on PEM server. In case PEM server and web server are on two different systems, run the command on the web server: - On a CentOS or RHEL 7.x 0r 8.x host: + On a CentOS or RHEL 7.x or RHEL 8.x host: ```text systemctl stop PEMHTTPD @@ -264,7 +264,7 @@ The default installation location for the PEM server when installed by the graph 5. The `yum makecache` command downloads the metadata for the currently enabled repositories; when the command completes, check the available packages to confirm that the list includes the latest PEM Server: - On a CentOS or RHEL 7.x or 8.x: + On CentOS or RHEL 7.x: ```text yum makecache @@ -272,7 +272,7 @@ The default installation location for the PEM server when installed by the graph yum list edb-pem ``` - On a CentOS or RHEL 8.x: + On RHEL 8.x: ```text dnf makecache @@ -282,7 +282,7 @@ The default installation location for the PEM server when installed by the graph 6. Install the PEM Server RPM; when the installation completes, you can use the `yum info` command to confirm installation information for the PEM Server: - On a CentOS or RHEL 7.x or 8.x: + On CentOS or RHEL 7.x: ```text yum install edb-pem @@ -290,7 +290,7 @@ The default installation location for the PEM server when installed by the graph yum info edb-pem ``` - On a CentOS or RHEL 8.x: + On RHEL 8.x: ```text dnf install edb-pem @@ -376,7 +376,7 @@ The default installation location for the PEM server when installed by the graph 16. Enable the `pemagent` service on PEM server and web server. Start the `pemagent` and `httpd` services on the web server. - On a CentOS or RHEL 7.x 0r 8.x host: + On a CentOS or RHEL 7.x host: ```text systemctl enable pemagent diff --git a/product_docs/docs/pem/7/pem_upgrade/02_upgrading_backend_database.mdx b/product_docs/docs/pem/7/pem_upgrade/02_upgrading_backend_database.mdx index 6bd6f06581e..f70e76d9c02 100644 --- a/product_docs/docs/pem/7/pem_upgrade/02_upgrading_backend_database.mdx +++ b/product_docs/docs/pem/7/pem_upgrade/02_upgrading_backend_database.mdx @@ -225,7 +225,7 @@ You can find more information about using pg_upgrade at: 3. Stop the services of both the old backend database and the new backend database. - On RHEL or CentOS 7.x or 8.x, open a command line and assume the identity of a superuser. Enter the command: + On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, open a command line and assume the identity of a superuser. Enter the command: ```text systemctl stop @@ -412,7 +412,7 @@ You can find more information about using pg_upgrade at: 8. Restart the service of the new backend database. - On RHEL or CentOS 7.x or 8.x, open a command line and assume the identity of a superuser. Enter the command: + On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, open a command line and assume the identity of a superuser. Enter the command: ```text systemctl stop diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx index 80f173c06c0..dbd8e5335b6 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/01_prerequisites_for_installing_pem_server.mdx @@ -66,7 +66,7 @@ legacyRedirectsGenerated: yum upgrade ``` - To upgrade packages on a Rocky Linux or RHEL 8.x host + To upgrade packages on a Rocky Linux or AlmaLinux or RHEL 8.x host ```text dnf upgrade diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx index 6c2f6423c89..463c5cbfcfb 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/03_installing_pem_server_on_linux.mdx @@ -7,9 +7,9 @@ legacyRedirectsGenerated: Before following the detailed instructions that install the PEM server on your specific platform, you must perform the prerequisite steps detailed in [Prerequisites for installing PEM Server](01_prerequisites_for_installing_pem_server/#prerequisites_for_installing_pem_server). -## Installing the PEM Server on a CentOS or RHEL or Rocky Linux Host +## Installing the PEM Server on a CentOS or RHEL or Rocky Linux or AlmaLinux Host -On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux or AlmaLinux system, you can use the `yum` package manager or `dnf` command to install a PEM Server; the installation tool you use will be dependent on the version of the host operating system. Before installing the server, you must ensure that your system contains the required prerequisite software listed below. **Install Version-Specific Software** @@ -21,7 +21,7 @@ Follow the version-specific instructions listed below to prepare your host syste yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a Rocky Linux or RHEL 8.x host: +- On a Rocky Linux or AlmaLinux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -60,7 +60,7 @@ After meeting the platform-specific prerequisites listed above, you can use yum yum install edb-pem ``` -- On Rocky Linux or RHEL 8.x, you can use `dnf` to install the PEM Server: +- On Rocky Linux or AlmaLinux or RHEL 8.x, you can use `dnf` to install the PEM Server: ```text dnf install edb-pem diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx index 2b57870847a..0e58a8dbeb0 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/08_installing_pem_agent_on_linux.mdx @@ -7,9 +7,9 @@ legacyRedirectsGenerated: A PEM Agent may monitor one or more servers on one or more hosts. For comprehensive information about managing a PEM Agent, see the [PEM Agent User Guide](https://www.enterprisedb.com/docs/pem/latest/pem_agent/). -## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux Host +## Installing a PEM Agent on a CentOS or RHEL or Rocky Linux or AlmaLinux Host -On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. +On a CentOS or RHEL or Rocky Linux or AlmaLinux system, you can use the `yum` package manager or `dnf` command to install a PEM Agent; the installation tool you use will be dependent on the version of the host operating system. Before installing the agent, you must ensure that your system contains the required prerequisite software listed below. **Install Platform-Specific Software** @@ -19,7 +19,7 @@ On a CentOS or RHEL or Rocky Linux system, you can use the `yum` package manager yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` -- On a Rocky Linux or RHEL 8.x host: +- On a Rocky Linux or AlmaLinux or RHEL 8.x host: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm @@ -50,13 +50,13 @@ sed -i "s@:@USERNAME:PASSWORD@" /etc/yum.repos.d/edb.repo **Installing the PEM Agent** -- Use the `yum install` command to install the PEM Agent on CentOS or RHEL 7.x | RHEL or Rocky Linux 8.x: +- Use the `yum install` command to install the PEM Agent on CentOS/RHEL 7.x or RHEL/Rocky Linux/AlmaLinux 8.x: ```text yum install edb-pem-agent ``` -- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux or RHEL 8.x: +- Also, you can use `dnf` command to install the PEM Agent on Rocky Linux or AlmaLinux or RHEL 8.x: ```text dnf install edb-pem-agent diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx index c44d3a5c6f8..3ff66c67e4a 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/09_registering_a_pem_agent.mdx @@ -59,7 +59,7 @@ By default, `heartbeat_connection` value is `false` but you can override the val Then, use a platform-specific command to start the PEM Agent service; -On a CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x host, use `systemctl` to start the service: +On a CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x host, use `systemctl` to start the service: ```text systemctl start pemagent diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx index e7b660b70e0..6f0f0644543 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/06_uninstalling_pem_components.mdx @@ -12,9 +12,9 @@ If you uninstall the PEM server package from a host, the PEM Agent package insta !!! Note Before uninstalling the PEM Agent, you need to de-register the agent first. You can de-register the agent using the `pemworker` command-line utility. After that, you can proceed with the uninstallation steps. -## Uninstalling PEM components from CentOS or RHEL or Rocky Linux Hosts +## Uninstalling PEM components from CentOS or RHEL or Rocky Linux or AlmaLinux Hosts -You can use variations of the `rpm`, `yum remove`, or `yum erase`, commands to remove the installed packages from CentOS or RHEL 7.x | Rocky Linux or RHEL 8.x hosts. Also you use `dnf remove` command to remove the installed package from Rocky Linux or RHEL 8.x host. Note that removing a package does not damage the PEM data directory. +You can use variations of the `rpm`, `yum remove`, or `yum erase` commands to remove the installed packages from CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x hosts. Also, you can use the `dnf remove` command to remove the installed package from Rocky Linux/AlmaLinux/RHEL 8.x hosts. Note that removing a package does not damage the PEM data directory. - Include the `-e` option when invoking the rpm command to remove an installed package; the command syntax is: @@ -36,7 +36,7 @@ You can use variations of the `rpm`, `yum remove`, or `yum erase`, commands to r Where `package_name` is the name of the package that you would like to remove. -- You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on Rocky Linux or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command: +- You can use `dnf remove` command to remove the pem server or Agent along with the `edb-pem` and `edb-pem-docs` dependencies on Rocky Linux or AlmaLinux or RHEL 8.x hosts. To remove a package, open a terminal window, assume superuser privileges, and enter the command: ```text dnf remove package_name diff --git a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx index 86ef501ae52..899d2d84c53 100644 --- a/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx +++ b/product_docs/docs/pem/8/pem_upgrade/01_upgrading_pem_installation/02_upgrading_pem_installation_linux_rpm.mdx @@ -30,7 +30,7 @@ yum update yum upgrade ``` -To upgrade packages on a CentOS or RHEL 8.x host +To upgrade packages on a Rocky Linux or AlmaLinux or RHEL 8.x host ```text dnf update @@ -103,7 +103,7 @@ You can use native packages to upgrade existing PEM Agents initially installed u ### Upgrading the PEM Agent on a CentOS or RHEL Host -For CentOS or RHEL 7.x or 8.x: +For CentOS or RHEL 7.x or RHEL 8.x: To upgrade a PEM agent, use the following command: @@ -111,7 +111,7 @@ To upgrade a PEM agent, use the following command: yum upgrade edb-pem-agent ``` -For CentOS or RHEL 8.x, you can also use the following command: +For Rocky Linux or AlmaLinux or RHEL 8.x, you can also use the following command: ```text dnf upgrade edb-pem-agent @@ -139,17 +139,17 @@ If you initially used native packages to install your PEM server, you can use na If you wish to upgrade a PEM server that is installed on a machine in an isolated network, you need to create a PEM repository on that machine before you upgrade the PEM server. For more information about creating a PEM repository on an isolated network, see [Creating a PEM Repository on an Isolated Network](../../pem_inst_guide_linux/04_installing_postgres_enterprise_manager/04_creating_pem_repository_in_isolated_network/). -### Upgrading a PEM Server on a CentOS or RHEL Host +### Upgrading a PEM Server on a CentOS, Rocky Linux, AlmaLinux, or RHEL Host To use an RPM package to upgrade an existing RPM installation you must: -You can use the `yum` package manager to upgrade the installed version of the PEM server on CentOS or RHEL 7.x or 8.x: +You can use the `yum` package manager to upgrade the installed version of the PEM server on CentOS/RHEL 7.x or Rocky Linux/AlmaLinux/RHEL 8.x: ```text yum upgrade edb-pem ``` -You can also use the `dnf` command on CentOS or RHEL 8.x: +You can also use the `dnf` command on Rocky Linux/AlmaLinux/RHEL 8.x: ```text dnf upgrade edb-pem From b4306d551b19891d74484b6637bd72da09baada1 Mon Sep 17 00:00:00 2001 From: Guang Yi Xu Date: Wed, 26 Jan 2022 11:40:07 +0800 Subject: [PATCH 86/97] Update BigAnimal getting_started doc to reflect latest output of preflight check script --- .../01_preparing_azure/index.mdx | 48 +++++++++---------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx index 563d5350cfe..03e2d506082 100644 --- a/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/01_preparing_azure/index.mdx @@ -4,10 +4,10 @@ redirects: - ../01_check_resource_limits --- -BigAnimal requires you to configure your Azure subscription before you deploy your clusters. The configurations that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: +BigAnimal requires you to configure your Azure subscription before you deploy your clusters. The configurations that you perform ensure that your Azure subscription is prepared to meet your clusters' requirements and resource limits, such as: - Are the necessary Azure resource providers registered for your subscription? -- Is there a restriction on SKUs for the Standard Esv3 and Standard Dv4 VM size families? +- Is there a restriction on SKUs for the Standard Esv3 family and Standard D2_v4 VM size? - Is there a sufficient limit on the number of vCPU or Public IP addresses in your region? !!! Note @@ -25,7 +25,7 @@ EDB recommends using the `biganimal-preflight-azure` script to check whether all EDB provides a shell script called [`biganimal-preflight-azure`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/biganimal-preflight-azure), which automatically checks whether requirements and resource limits are met in your Azure subscription based on the clusters you plan to deploy. 1. Open the [Azure Cloud Shell](https://shell.azure.com/) in your browser. -2. From the Azure Cloud Shell, use the following command to run the `biganimal-preflight-azure` script. +2. From the Azure Cloud Shell, use the following command to run the `biganimal-preflight-azure` script. ```sh curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/biganimal-preflight-azure | bash -s \ @@ -41,7 +41,7 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. - ``: Enter the Azure subscription ID of your BigAnimal deployment. - ``: Enter the Azure region where your clusters are being deployed. - - ``: Enter **e2s_v3**, which indicates the type of virtual machine instance (Esv3 with 2 cores) used in BigAnimal. + - ``: Enter **e2s_v3**, which indicates the type of virtual machine instance (Esv3 with 2 cores) used in BigAnimal. - `--high-availability` or `-a`: Indicates that high availability is enabled in your clusters. - ``: Indicates either **public** or **private** endpoints. - `--activate-region` or `-r`: Indicates that no clusters are currently deployed in the region. @@ -58,7 +58,7 @@ EDB provides a shell script called [`biganimal-preflight-azure`](https://github. --activate-region ``` -The script displays the following output: +The script displays the following output: - A list of required Azure resource providers and their registration status. Ensure that you register the resource providers that are displayed as `NotRegistered` in the `RegistrationState` column. See [Register Azure resource providers](#register-azure-service-providers). @@ -100,16 +100,16 @@ The script displays the following output: - Whether your Azure subscription has sufficient limits on vCPUs and IP addresses for your region. Open a support request to raise limits for the vCPUs and IP addresses if they exceed the available VM families with `NotAvailableForSubscription` displayed in the `Restrictions` column. See [Increase Public IP addresses](#increase-public-ip-addresses-limits) and [Increase vCPU limits](#increase-vcpu-limits). ``` - ####################### - # Quota Limitation # - ####################### - - Resource Limit Used Available Gap Suggestion - Total Regional vCPUs 130 27 103 89 OK - Standard D2v4 Family vCPUs 20 14 6 0 Need Increase - Standard E2sv3 Family vCPUs 20 4 16 8 OK - Public IP Addresses — Basic 20 11 9 8 OK - Public IP Addresses — Standard 20 3 17 16 OK + ####################### + # Quota Limitation # + ####################### + + Resource Limit Used Available Gap Suggestion + Total Regional vCPUs 130 27 103 89 OK + Standard Dv4 Family vCPUs 20 14 6 0 Need Increase + Standard ESv3 Family vCPUs 20 4 16 8 OK + Public IP Addresses — Basic 20 11 9 8 OK + Public IP Addresses — Standard 20 3 17 16 OK ``` ### Method 2: Manually check requirements @@ -118,7 +118,7 @@ If you are manually checking the requirements instead of using the `biganimal-pr #### Check Azure resource provider registrations using Azure Cloud Shell -To check if an Azure resource provider is registered, use the following command. +To check if an Azure resource provider is registered, use the following command. ``` az provider show -n Microsoft.ContainerService @@ -129,16 +129,16 @@ Microsoft.ContainerService RegistrationRequired Registered ``` -#### Check for vCPU restrictions for the VM size family +#### Check for SKU restrictions for the specific VM size -You can check vCPU limits for the VM size family using the Azure Cloud Shell. For example, to check the Standard_D2_v4 VM SKU restriction in `eastus2` location for all zones, run the following command: +You can check SKU restrictions for the VM size using the Azure Cloud Shell. For example, to check the Standard_E2s_v3 VM SKU restriction in `eastus2` location for all zones, run the following command: ```sh -az vm list-skus -l eastus2 --zone --size Standard_D2_v4 +az vm list-skus -l eastus2 --zone --size Standard_E2s_v3 -ResourceType Locations Name Zones Restrictions ---------------- ----------- --------------- ------- ------------ -virtualMachines eastus2 Standard_D2_v4 1,2,3 NotAvailableForSubscription, type: Zone, locations: eastus2, zones: 3,2 +ResourceType Locations Name Zones Restrictions +--------------- ----------- --------------- ------- ------------ +virtualMachines eastus2 Standard_E2s_v3 1,2,3 NotAvailableForSubscription, type: Zone, locations: eastus2, zones: 3,2 ``` Alternatively, to check for SKU restrictions using the Azure Portal, see [Solution 3 - Azure portal](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/error-sku-not-available#solution-3---azure-portal). @@ -156,7 +156,7 @@ To check if you have adequate Azure resources to provision new clusters: ## Configure your Azure subscription -After checking whether the requirements and resource limits are met, configure your Azure subscription. +After checking whether the requirements and resource limits are met, configure your Azure subscription. !!! Note Before proceeding, see [Understanding requirements in Azure](../01_preparing_azure/01_understanding_qotas_in_azure) for details on planning for your clusters' requirements and resource limits in Azure. @@ -194,7 +194,7 @@ You can increase the number of public IP addresses for your account either by us ### Increase vCPU limits -You can increase the number of Dv4 or Esv3 family virtual machines per region by using the Azure Portal or by submitting a support request. See: +You can increase the number of Dv4 or Esv3 family virtual machines per region by using the Azure Portal or by submitting a support request. See: - [Request a quota increase at a subscription level using Usages + quotas](https://docs.microsoft.com/en-us/azure/azure-portal/supportability/classic-deployment-model-quota-increase-requests#request-quota-increase-for-the-classic-deployment-model-from-usage--quotas) From 88bc101909677d7b080f88f9ba22854e0d219b1e Mon Sep 17 00:00:00 2001 From: sszhao1020 <89435179+sszhao1020@users.noreply.github.com> Date: Wed, 26 Jan 2022 16:02:28 +0800 Subject: [PATCH 87/97] Update 02_connect_cloud_account.mdx --- .../release/getting_started/02_connect_cloud_account.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index aeeddf96400..27b334e5ba1 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -37,12 +37,14 @@ Set up your BigAnimal account on Azure Marketplace. Your Azure subscription for ### Create Azure Active Directory Application using `create-spn` -To simplify the process of creating an Azure AD Application, EDB provides the [`create-spn`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/create-spn.sh) script for Azure API users. The script automates the creation of the Active Directory Application. You can download the script [here](https://github.com/EnterpriseDB/cloud-utilities/tree/main/azure). +To simplify the process of creating an Azure AD Application, EDB provides the [`create-spn`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/create-spn.sh) script for Azure API users. The script automates the creation of the Active Directory Application. The script is [here](https://github.com/EnterpriseDB/cloud-utilities/tree/main/azure). Before using the script, ensure that these utilities are installed on your machine: - [jq command-line JSON processor](https://stedolan.github.io/jq/) - [azure cli](https://docs.microsoft.com/en-us/cli/azure/) v2.26 or above +The alertnative way is running the script on [Azure Cloud Shell](https://azure.microsoft.com/en-us/features/cloud-shell/?ef_id=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&OCID=AID2200202_SEM_CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&gclid=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE#overview). + The syntax of the command is: ``` From a8b9764f404ef0b4818e0f5d018e8928fcf79db3 Mon Sep 17 00:00:00 2001 From: George Song Date: Wed, 26 Jan 2022 08:54:21 -0800 Subject: [PATCH 88/97] build: update development environment settings This app is still no Node 14 --- .envrc | 1 + .nvmrc | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.envrc b/.envrc index 809c9115599..eac95bf39ba 100644 --- a/.envrc +++ b/.envrc @@ -1,2 +1,3 @@ layout node +source_env_if_exists .envrc.local dotenv_if_exists .env.development diff --git a/.nvmrc b/.nvmrc index b009dfb9d9f..8351c19397f 100644 --- a/.nvmrc +++ b/.nvmrc @@ -1 +1 @@ -lts/* +14 From 1937df0ff771777bdd80701c357270e2065452da Mon Sep 17 00:00:00 2001 From: Jon Ericson Date: Wed, 26 Jan 2022 10:16:51 -0800 Subject: [PATCH 89/97] Add LiveCompare automation and use a dispatch script. --- .github/workflows/sync-and-process-files.yml | 18 +------------ scripts/source/dispatch_product.py | 28 ++++++++++++++++++++ scripts/source/livecompare.js | 2 +- 3 files changed, 30 insertions(+), 18 deletions(-) create mode 100755 scripts/source/dispatch_product.py diff --git a/.github/workflows/sync-and-process-files.yml b/.github/workflows/sync-and-process-files.yml index ee9c55cc48f..4c114d93bb4 100644 --- a/.github/workflows/sync-and-process-files.yml +++ b/.github/workflows/sync-and-process-files.yml @@ -41,23 +41,7 @@ jobs: run: npm install -g npm@7 - name: Process changes - run: | - case ${{ github.event.client_payload.repo }} in - - EnterpriseDB/cloud-native-postgresql) - ${{ github.workspace }}/destination/scripts/source/process-cnp-docs.sh ${{ github.workspace }}/source ${{ github.workspace }}/destination - ;; - - EnterpriseDB/fe) - mkdir -p ${{ github.workspace }}/destination/icons-pkg && \ - cp -fr utils/icons-placeholder/output/* ${{ github.workspace }}/destination/icons-pkg/ - ;; - - *) - echo "The workflow has not been configured for the ${{ github.event.client_payload.repo }} repo" - exit 1 - ;; - esac + run: ${{ github.workspace }}/destination/scripts/source/dispatch_product.py ${{ github.event.client_payload.repo }} ${{ github.workspace }} working-directory: source - name: Create pull request diff --git a/scripts/source/dispatch_product.py b/scripts/source/dispatch_product.py new file mode 100755 index 00000000000..13e185ba598 --- /dev/null +++ b/scripts/source/dispatch_product.py @@ -0,0 +1,28 @@ +#!/usr/bin/env python3 + +import argparse +parser = argparse.ArgumentParser() +parser.add_argument("repo", + help="Product repository", + type=str) +parser.add_argument("workspace", + help="GitHub workplace path", + type=str) + +args = parser.parse_args() + +import os + +commands = {'EnterpriseDB/cloud-native-postgresql': + f'{args.workspace}/destination/scripts/source/process-cnp-docs.sh {args.workspace}/source {args.workspace }/destination', + 'EnterpriseDB/fe': + f'mkdir -p {args.workspace}/destination/icons-pkg && \ + cp -fr utils/icons-placeholder/output/* {args.workspace}/destination/icons-pkg/', + 'EnterpriseDB/LiveCompare': + f'node {args.workspace}/destination/scripts/source/livecompare.js' + } + + +cmd = commands[args.repo] + +ret = os.system(cmd) diff --git a/scripts/source/livecompare.js b/scripts/source/livecompare.js index a28a8d40542..1cf9cf29b89 100644 --- a/scripts/source/livecompare.js +++ b/scripts/source/livecompare.js @@ -19,7 +19,7 @@ const { exec, execSync } = require("child_process"); const isAbsoluteUrl = require("is-absolute-url"); const fileToMetadata = {}; -const basePath = path.resolve("temp_livecompare/docs/"); +const basePath = path.resolve("source/docs/"); (async () => { const processor = unified() From 4dc86c89ac7e337eaa2ac7df0670bdfcb412894a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 26 Jan 2022 13:45:54 -0500 Subject: [PATCH 90/97] added AlmaLinux --- .../02_rpm_installation.mdx | 4 +- ...age_manager_to_install_advanced_server.mdx | 38 ++++++++-------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- .../06_uninstalling_advanced_server.mdx | 6 +-- .../02_rpm_installation.mdx | 6 +-- ...age_manager_to_install_advanced_server.mdx | 40 ++++++++--------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- .../06_uninstalling_advanced_server.mdx | 6 +-- .../13/edb_plus/03_installing_edb_plus.mdx | 12 ++--- ...age_manager_to_install_advanced_server.mdx | 44 +++++++++---------- .../04_installing_troubleshooting.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 4 +- ...06_installing_and_configuring_pgadmin4.mdx | 2 +- .../07_uninstalling_advanced_server.mdx | 6 +-- .../docs/epas/13/epas_qs_linux_7/index.mdx | 4 +- .../docs/epas/13/epas_qs_linux_8/index.mdx | 6 +-- .../14/edb_plus/03_installing_edb_plus.mdx | 12 ++--- ...age_manager_to_install_advanced_server.mdx | 42 +++++++++--------- .../epas_inst_linux/04_enabling_core_dump.mdx | 4 +- .../05_installing_troubleshooting.mdx | 2 +- ...06_installing_and_configuring_pgadmin4.mdx | 2 +- ...naging_an_advanced_server_installation.mdx | 2 +- .../08_uninstalling_advanced_server.mdx | 6 +-- .../docs/epas/14/epas_qs_linux_7/index.mdx | 4 +- .../docs/epas/14/epas_qs_linux_8/index.mdx | 6 +-- 27 files changed, 136 insertions(+), 136 deletions(-) diff --git a/product_docs/docs/epas/11/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx b/product_docs/docs/epas/11/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx index 2350b31ed6f..aa86c08aeea 100644 --- a/product_docs/docs/epas/11/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx +++ b/product_docs/docs/epas/11/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx @@ -18,7 +18,7 @@ To create the repository configuration file, assume superuser privileges, and in yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -32,7 +32,7 @@ The repository configuration file is named `edb.repo`. The file resides in `/etc yum install edb-asxx-edbplus ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ``` dnf install edb-asxx-edbplus diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index ff9b9ea2dd3..ce099567bb1 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -74,7 +74,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text # dnf -y install java @@ -94,9 +94,9 @@ After receiving your repository credentials you can: - Modify the file, providing your user name and password. - Install Advanced Server. -## Installing on CentOS 7 or Rocky Linux 8 +## Installing on CentOS 7 or Rocky Linux/AlmaLinux 8 -You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. +You can use an RPM package to install Advanced Server on a CentOS 7 or Rocky Linux/AlmaLinux 8 host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -106,7 +106,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -126,19 +126,19 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text # dnf -y install epel-release ``` -- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On Rocky Linux 8, disable the built-in PostgreSQL module: + On Rocky Linux/AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -154,7 +154,7 @@ After saving your changes to the configuration file, you can use `yum install` o yum -y install edb-as11-server ``` -- On Rocky Linux 8: +- On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-as11-server @@ -399,7 +399,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or Rocky Linux 8: +On RHEL or Rocky Linux/AlmaLinux 8: ```text dnf search @@ -482,7 +482,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux/AlmaLinux 8: ```text dnf upgrade edb-repo @@ -496,7 +496,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux/AlmaLinux 8: ```text dnf upgrade edb* @@ -917,7 +917,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -925,9 +925,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -1014,9 +1014,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Modifying the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-11.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as11/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -1044,7 +1044,7 @@ By default, data files reside under `/var/lib/edb/as11/data` directory. To use a You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** The `edb-as11-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1096,7 +1096,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or Rocky Linux 8.x: + On RHEL or Rocky Linux/AlmaLinux 8.x: ```bash dnf install epel-release @@ -1139,7 +1139,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as11-server ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-as11-server diff --git a/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx index 2ab5bf46c4b..ee3b688bfb8 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index 7d9987f5a90..777fdddf52b 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -32,9 +32,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx index 3104ca0c0ed..7f07fad252e 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/06_uninstalling_advanced_server.mdx @@ -32,7 +32,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove @@ -43,7 +43,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or Rocky Linux 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 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + 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: @@ -53,7 +53,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as11-server* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove edb-as11-server* diff --git a/product_docs/docs/epas/12/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx b/product_docs/docs/epas/12/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx index b6f5d19cfb2..7819d95053b 100644 --- a/product_docs/docs/epas/12/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx +++ b/product_docs/docs/epas/12/edb_plus/03_installing_edb_plus/02_rpm_installation.mdx @@ -19,7 +19,7 @@ To create the repository configuration file, assume superuser privileges, and in yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -33,7 +33,7 @@ The repository configuration file is named `edb.repo`. The file resides in `/etc yum install edb-asxx-edbplus ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ``` dnf install edb-asxx-edbplus @@ -66,7 +66,7 @@ You must confirm that an `identd` server is installed and running. You can use t yum install xinetd authd ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf install xinetd authd diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 0fcf57655c8..37f0ce57d03 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -20,7 +20,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux | AlmaLinux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` - On SLES: `zypper search --requires --verbose ` @@ -73,7 +73,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text # dnf -y install java @@ -94,9 +94,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS 7 or Rocky Linux 8 +## Installing on CentOS 7 or Rocky Linux/AlmaLinux 8 -You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. +You can use an RPM package to install Advanced Server on a CentOS 7 or Rocky Linux/AlmaLinux 8 host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -106,7 +106,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -128,7 +128,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # yum makecache ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text # dnf -y install epel-release @@ -136,13 +136,13 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # dnf makecache ``` -- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On Rocky Linux 8, disable the built-in PostgreSQL module: + On Rocky Linux/AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -170,7 +170,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as12-server ``` -- On Rocky Linux 8: +- On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-as12-server @@ -445,7 +445,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or Rocky Linux 8: +On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf search @@ -540,7 +540,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb-repo @@ -554,7 +554,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb* @@ -1017,7 +1017,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -1025,9 +1025,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -1174,9 +1174,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Modifying the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-12.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as12/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -1204,7 +1204,7 @@ By default, data files reside under `/var/lib/edb/as12/data` directory. To use a You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** The `edb-as12-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1256,7 +1256,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or Rocky Linux 8.x: + On RHEL or Rocky Linux or AlmaLinux 8.x: ```bash dnf install epel-release @@ -1299,7 +1299,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as12-server ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install edb-as12-server diff --git a/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx index d75461ecb14..a0cfb5384ce 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x or RHEL or Rocky Linux 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index 5360d07865b..dcdd0c94562 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -33,9 +33,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx index e08c5ff20f4..701af8c9923 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/12/epas_inst_linux/06_uninstalling_advanced_server.mdx @@ -32,7 +32,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove @@ -43,7 +43,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or Rocky Linux 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 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + 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: @@ -53,7 +53,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as12-server* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove edb-as12-server* diff --git a/product_docs/docs/epas/13/edb_plus/03_installing_edb_plus.mdx b/product_docs/docs/epas/13/edb_plus/03_installing_edb_plus.mdx index a6470da4392..b10dd484fee 100644 --- a/product_docs/docs/epas/13/edb_plus/03_installing_edb_plus.mdx +++ b/product_docs/docs/epas/13/edb_plus/03_installing_edb_plus.mdx @@ -25,7 +25,7 @@ Before installing EDB\*Plus, you must first install Java (version 1.8 or later). # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text # dnf -y install java @@ -61,7 +61,7 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -81,13 +81,13 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools @@ -101,7 +101,7 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install edb-asxx-edbplus ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-asxx-edbplus @@ -338,7 +338,7 @@ You must confirm that an `identd` server is installed and running. You can use t yum -y install xinetd authd ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf -y install xinetd authd diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index b71d367f48a..0e804680133 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -12,7 +12,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux AlmaLinux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` Where, `package_name` is the name of the package that you want to install. @@ -64,7 +64,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text # dnf -y install java @@ -85,9 +85,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS 7 or Rocky Linux 8 +## Installing on CentOS 7 or Rocky Linux/AlmaLinux 8 -You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. +You can use an RPM package to install Advanced Server on a CentOS 7 or Rocky Linux/AlmaLinux 8 host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -97,7 +97,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -119,7 +119,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # yum makecache ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text # dnf -y install epel-release @@ -127,13 +127,13 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # dnf makecache ``` -- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On Rocky Linux 8, disable the built-in PostgreSQL module: + On Rocky Linux/AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -161,7 +161,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as13-server ``` -- On Rocky Linux 8: +- On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-as13-server @@ -432,7 +432,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or Rocky Linux 8: +On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf search @@ -527,7 +527,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb-repo @@ -541,7 +541,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb* @@ -717,7 +717,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -725,9 +725,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL/CentOS 7.x on RHEL/Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -876,7 +876,7 @@ Where `path_to_initdb_installation_directory` specifies the location of the `ini ### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-13.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as13/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -919,7 +919,7 @@ By default, data files reside under `/var/lib/edb/as13/data` directory. To use a systemctl start edb-as-13 ``` -### Configuring SELinux Policy to Change the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Configuring SELinux Policy to Change the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x By default, the data files resides under `/var/lib/edb/as13/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps: @@ -1003,9 +1003,9 @@ By default, the data files resides under `/var/lib/edb/as13/data` directory. To You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination. -**Enabling Core Dumps on a RHEL orCentOS or Rocky Linux Host** +**Enabling Core Dumps on a RHEL/CentOS 7 or RHEL/Rocky Linux/AlmaLinux 8 Host** -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: +On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: - Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled. @@ -1230,7 +1230,7 @@ On Debian 9, 10 or Ubuntu 18, 20, core file creation is disabled by default. To You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** The `edb-as13-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1282,7 +1282,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or Rocky Linux 8.x: + On RHEL or Rocky Linux or AlmaLinux 8.x: ```bash dnf install epel-release @@ -1325,7 +1325,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as13-server ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install edb-as13-server diff --git a/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx b/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx index f3acb6151b2..44c3d972b5c 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/04_installing_troubleshooting.mdx @@ -24,7 +24,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and RHEL or Rocky Linux 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx index b11ef253354..c26e676e8d6 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/05_managing_an_advanced_server_installation.mdx @@ -27,9 +27,9 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -If your installation of Advanced Server resides on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. +If your installation of Advanced Server resides on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, you must use the `systemctl` command to control the Advanced Server service and supporting components. The `systemctl` command must be in your search path and must be invoked with superuser privileges. To use the command, open a command line, and enter: diff --git a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx index 7ecf6b7cee0..19c24aae14b 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx @@ -10,7 +10,7 @@ legacyRedirectsGenerated: pgAdmin 4 is the leading Open Source management tool for Postgres databases. EDB pgAdmin 4 is an enhanced version of open source pgAdmin 4 specifically for Advanced Server databases. It is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance, and use of database objects. -You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or Rocky Linux 8.x platform. +You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL/CentOS 7.x platforms and using `dnf` package manager for RHEL/Rocky Linux/AlmaLinux 8.x platforms. diff --git a/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx index f4abed45c23..470fd056c5e 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/13/epas_inst_linux/07_uninstalling_advanced_server.mdx @@ -30,7 +30,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove @@ -41,7 +41,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or Rocky Linux 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 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + 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: @@ -51,7 +51,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as13-server* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove edb-as13-server* diff --git a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx b/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx index 8a879489623..45e2825098f 100644 --- a/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_linux_7/index.mdx @@ -1,6 +1,6 @@ --- -navTitle: Linux on CentOS or RHEL 7 -title: "Quick Start Guide for Linux on CentOS or RHEL 7" +navTitle: CentOS/RHEL 7 +title: "Quick Start Guide for CentOS/RHEL 7" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx b/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx index 75c0aed6b83..05aa2e5b58b 100644 --- a/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx +++ b/product_docs/docs/epas/13/epas_qs_linux_8/index.mdx @@ -1,6 +1,6 @@ --- -navTitle: Linux on CentOS or RHEL 8 -title: "Quick Start Guide for Linux on CentOS or RHEL 8" +navTitle: RHEL/Rocky Linux/AlmaLinux 8 +title: "Quick Start Guide for RHEL/Rocky Linux/AlmaLinux 8" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -10,7 +10,7 @@ legacyRedirectsGenerated: Advanced Server adds extended functionality to the open-source PostgreSQL database that supports database administration, enhanced SQL capabilities, database and application security, performance monitoring and analysis, and application development utilities. Advanced Server also supports database compatibility features for Oracle users; for detailed information about compatibility features, see the Advanced Server documentation. -This guide will walk you through using `dnf` to install EDB Postgres Advanced Server on a RHEL or CentOS 8 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are likely to be additional security and resource considerations when configuring a production installation that are not covered by this document. +This guide will walk you through using `dnf` to install EDB Postgres Advanced Server on a RHEL/Rocky Linux/AlmaLinux 8 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are likely to be additional security and resource considerations when configuring a production installation that are not covered by this document. This guide assumes that you are familiar with simple operating system and system administration procedures, and have administrative privileges on the host on which Advanced Server will be installed. diff --git a/product_docs/docs/epas/14/edb_plus/03_installing_edb_plus.mdx b/product_docs/docs/epas/14/edb_plus/03_installing_edb_plus.mdx index 92f083877b6..3e25833fe69 100644 --- a/product_docs/docs/epas/14/edb_plus/03_installing_edb_plus.mdx +++ b/product_docs/docs/epas/14/edb_plus/03_installing_edb_plus.mdx @@ -16,7 +16,7 @@ Before installing EDB\*Plus, you must first install Java (version 1.8 or later). # yum -y install java ``` -- On RHEL or CentOS 8: +- On RHEL or Rocky Linux/AlmaLinux 8: ```text # dnf -y install java @@ -52,7 +52,7 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -72,13 +72,13 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` -- For CentOS 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools @@ -92,7 +92,7 @@ You can use an RPM package to install EDB\*Plus on a CentOS host. yum -y install edb-asxx-edbplus ``` - On CentOS 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-asxx-edbplus @@ -329,7 +329,7 @@ You must confirm that an `identd` server is installed and running. You can use t yum -y install xinetd authd ``` -- On RHEL or CentOS 8: +- On RHEL/Rocky Linux/AlmaLinux 8: ```text dnf -y install xinetd authd diff --git a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 96e5a2fe455..87532fbf95a 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -8,7 +8,7 @@ You can use the `dnf` or `yum` package manager to install Advanced Server or Adv You can list the dependencies of a package by running the following command: -- On Fedora | RHEL | CentOS | Rocky Linux: `repoquery --requires --resolve ` +- On Fedora | RHEL | CentOS | Rocky Linux | AlmaLinux: `repoquery --requires --resolve ` - On Debian | Ubuntu: `apt-cache depends ` Where, `package_name` is the name of the package that you want to install. @@ -60,7 +60,7 @@ Before using an RPM to install Migration Toolkit or EDB\*Plus, you must first in # yum -y install java ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text # dnf -y install java @@ -81,9 +81,9 @@ After receiving your repository credentials you can: - Install the repository keys and additional prerequisite software. - Install Advanced Server and supporting components. -## Installing on CentOS 7 or Rocky Linux 8 +## Installing on CentOS 7 or Rocky Linux/AlmaLinux 8 -You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux host. +You can use an RPM package to install Advanced Server on a CentOS 7 or Rocky Linux/AlmaLinux 8 host. - To install the repository configuration file, assume superuser privileges and invoke one of the following platform specific commands: @@ -93,7 +93,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm @@ -115,7 +115,7 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # yum makecache ``` - On Rocky Linux 8: + On Rocky Linux/AlmaLinux 8: ```text # dnf -y install epel-release @@ -123,13 +123,13 @@ You can use an RPM package to install Advanced Server on a CentOS or Rocky Linux # dnf makecache ``` -- For Rocky Linux 8, enable the PowerTools repository to satisfy package dependencies: +- For Rocky Linux/AlmaLinux 8, enable the PowerTools repository to satisfy package dependencies: ```text dnf config-manager --set-enabled PowerTools ``` - On Rocky Linux 8, disable the built-in PostgreSQL module: + On Rocky Linux/AlmaLinux 8, disable the built-in PostgreSQL module: ```text dnf -qy module disable postgresql @@ -157,7 +157,7 @@ Then, you can use `yum install` or `dnf install` command to install Advanced Ser yum -y install edb-as14-server ``` -- On Rocky Linux 8: +- On Rocky Linux/AlmaLinux 8: ```text dnf -y install edb-as14-server @@ -430,7 +430,7 @@ On RHEL or CentOS 7: yum search ``` -On RHEL or Rocky Linux 8: +On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf search @@ -525,7 +525,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb-repo ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb-repo @@ -539,7 +539,7 @@ If you have an existing Advanced Server RPM installation, you can use `yum` or ` yum upgrade edb* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf upgrade edb* @@ -715,7 +715,7 @@ The packages that install the database server component create a unit file (on v The PostgreSQL `initdb` command creates a database cluster; when installing Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can: - Specify environment options on the command line. -- Include the `systemd` service manager on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x and use a service configuration file to configure the environment. +- Include the `systemd` service manager on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment. To review the `initdb` documentation, visit: @@ -723,9 +723,9 @@ To review the `initdb` documentation, visit: After specifying any options in the service configuration file, you can create the database cluster and start the service; these steps are platform specific. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** -To invoke `initdb` on a RHEL or CentOS 7.x | Rocky Linux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: +To invoke `initdb` on a RHEL/CentOS 7.x or Rocky Linux/AlmaLinux 8.x system, with the options specified in the service configuration file, assume the identity of the operating system superuser: ```text su - root @@ -872,9 +872,9 @@ You can also view online help for `initdb` by assuming superuser privileges and Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file. -### Modifying the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Modifying the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. +On a RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x host, the unit file is named `edb-as-14.service` and resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the Advanced Server `data` directory. You should avoid making any modifications directly to the unit file because it may be overwritten during package upgrades. By default, data files reside under `/var/lib/edb/as14/data` directory. To use a data directory that resides in a non-default location, perform the following steps: @@ -917,7 +917,7 @@ By default, data files reside under `/var/lib/edb/as14/data` directory. To use a systemctl start edb-as-14 ``` -### Configuring SELinux Policy to Change the Data Directory Location on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Configuring SELinux Policy to Change the Data Directory Location on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x By default, the data files resides under `/var/lib/edb/as14/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy and perform the following steps: @@ -1001,7 +1001,7 @@ By default, the data files resides under `/var/lib/edb/as14/data` directory. To You can configure Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are version specific to the Linux host. -**On RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x** +**On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x** The `edb-as14-server-core` RPM for version 7.x | 8.x contains a unit file that starts the Advanced Server instance. The file allows you to start multiple services, with unique `data` directories and that monitor different ports. You must have `root` access to invoke or modify the script. @@ -1053,7 +1053,7 @@ To create and use a local repository, you must: yum install createrepo ``` - On RHEL or Rocky Linux 8.x: + On RHEL or Rocky Linux or AlmaLinux 8.x: ```bash dnf install epel-release @@ -1096,7 +1096,7 @@ After specifying the location and connection information for your local reposito yum -y install edb-as14-server ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf -y install edb-as14-server diff --git a/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx b/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx index 37bc053b744..44b4df637f6 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/04_enabling_core_dump.mdx @@ -6,9 +6,9 @@ title: "Enabling Core Dumps" You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps may be produced on-demand (such as by a debugger) or automatically upon termination. -## Enabling Core Dumps on a RHEL or CentOS or Rocky Linux Host +## Enabling Core Dumps on a RHEL or CentOS or Rocky Linux or AlmaLinux Host -On a RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: +On RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x, core file creation is disabled by default. To enable the core file generation, follow the following commands: - Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled. diff --git a/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx b/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx index 49fd42390f5..b4d56632ce7 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/05_installing_troubleshooting.mdx @@ -20,7 +20,7 @@ If you encounter a similar message, you should confirm that the data directory i **Difficulty Installing the EPEL Release Package** -If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL or CentOS 7.x and RHEL or Rocky Linux 8.x: +If you encounter difficulty when installing the `EPEL` release package, you can use the following command to install the `epel-release` package on RHEL/CentOS 7.x and RHEL/Rocky Linux/AlmaLinux 8.x: ```text yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm diff --git a/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx b/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx index 58d291f1404..894a7d45d59 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/06_installing_and_configuring_pgadmin4.mdx @@ -6,7 +6,7 @@ title: "Installing and Configuring pgAdmin4" pgAdmin 4 is the leading Open Source management tool for Postgres databases. EDB pgAdmin 4 is an enhanced version of open source pgAdmin 4 specifically for Advanced Server databases. It is designed to meet the needs of both novice and experienced Postgres users alike, providing a powerful graphical interface that simplifies the creation, maintenance, and use of database objects. -You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL or CentOS 7.x platform and using `dnf` package manager for RHEL or Rocky Linux 8.x platform. +You can install EDB pgAdmin 4 for your Advanced Server database using the `yum` package manager for RHEL/CentOS 7.x platforms and using `dnf` package manager for RHEL/Rocky Linux/AlmaLinux 8.x platforms. diff --git a/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx index f1e6afa38a5..ea2fdc47b2b 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/07_managing_an_advanced_server_installation.mdx @@ -23,7 +23,7 @@ The following table lists the names of the services that control Advanced Server You can use the Linux command line to control Advanced Server's database server and the services of Advanced Server's supporting components. The commands that control the Advanced Server service on a Linux platform are host specific. -### Controlling a Service on RHEL or CentOS 7.x | RHEL or Rocky Linux 8.x +### Controlling a Service on RHEL/CentOS 7.x or RHEL/Rocky Linux/AlmaLinux 8.x If your installation of Advanced Server resides on version 7.x | 8.x of RHEL and CentOS, you must use the `systemctl` command to control the Advanced Server service and supporting components. diff --git a/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx b/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx index 421dad16b2a..62b8364c355 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx +++ b/product_docs/docs/epas/14/epas_inst_linux/08_uninstalling_advanced_server.mdx @@ -28,7 +28,7 @@ You can use the `yum remove` or `dnf remove` command to remove a package install yum remove ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove @@ -39,7 +39,7 @@ Where `package_name` is the name of the package that you would like to remove. `yum` and RPM will not remove a package that is required by another package. If you attempt to remove a package that satisfies a package dependency, `yum` or RPM will provide a warning. !!! Note - In RHEL or Rocky Linux 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 8, you must disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file. + 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: @@ -49,7 +49,7 @@ To uninstall Advanced Server and its dependent packages; use the following comma yum remove edb-as14-server* ``` -- On RHEL or Rocky Linux 8: +- On RHEL or Rocky Linux or AlmaLinux 8: ```text dnf remove edb-as14-server* diff --git a/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx b/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx index 35672832170..4c363361b24 100644 --- a/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx +++ b/product_docs/docs/epas/14/epas_qs_linux_7/index.mdx @@ -1,6 +1,6 @@ --- -navTitle: Linux on CentOS or RHEL 7 -title: "Quick Start Guide for Linux on CentOS or RHEL 7" +navTitle: CentOS/RHEL 7 +title: "Quick Start Guide for CentOS or RHEL 7" --- Advanced Server adds extended functionality to the open-source PostgreSQL database that supports database administration, enhanced SQL capabilities, database and application security, performance monitoring and analysis, and application development utilities. Advanced Server also supports database compatibility features for Oracle users; for detailed information about compatibility features, [see the Advanced Server documentation](/epas/latest/). diff --git a/product_docs/docs/epas/14/epas_qs_linux_8/index.mdx b/product_docs/docs/epas/14/epas_qs_linux_8/index.mdx index e204d893349..e6470f109bc 100644 --- a/product_docs/docs/epas/14/epas_qs_linux_8/index.mdx +++ b/product_docs/docs/epas/14/epas_qs_linux_8/index.mdx @@ -1,11 +1,11 @@ --- -navTitle: Linux on CentOS or RHEL 8 -title: "Quick Start Guide for Linux on CentOS or RHEL 8" +navTitle: RHEL/Rocky Linux/AlmaLinux 8 +title: "Quick Start Guide for RHEL/Rocky Linux/AlmaLinux 8" --- Advanced Server adds extended functionality to the open-source PostgreSQL database that supports database administration, enhanced SQL capabilities, database and application security, performance monitoring and analysis, and application development utilities. Advanced Server also supports database compatibility features for Oracle users; for detailed information about compatibility features, see the Advanced Server documentation. -This guide will walk you through using `dnf` to install EDB Postgres Advanced Server on a RHEL or CentOS 8 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are likely to be additional security and resource considerations when configuring a production installation that are not covered by this document. +This guide will walk you through using `dnf` to install EDB Postgres Advanced Server on a RHEL/Rocky Linux/AlmaLinux 8 system and deploying a database cluster. The database created by this tutorial is well-suited for experimentation and testing. There are likely to be additional security and resource considerations when configuring a production installation that are not covered by this document. This guide assumes that you are familiar with simple operating system and system administration procedures, and have administrative privileges on the host on which Advanced Server will be installed. From 0fb69563b3bb56f28f67f318de3f31970177aebf Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Wed, 26 Jan 2022 13:55:17 -0500 Subject: [PATCH 91/97] Dee's edits --- .../release/getting_started/02_connect_cloud_account.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index 27b334e5ba1..714f2d1999b 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -43,7 +43,7 @@ Before using the script, ensure that these utilities are installed on your machi - [jq command-line JSON processor](https://stedolan.github.io/jq/) - [azure cli](https://docs.microsoft.com/en-us/cli/azure/) v2.26 or above -The alertnative way is running the script on [Azure Cloud Shell](https://azure.microsoft.com/en-us/features/cloud-shell/?ef_id=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&OCID=AID2200202_SEM_CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&gclid=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE#overview). +Alternatively, you can run the script in [Azure Cloud Shell](https://azure.microsoft.com/en-us/features/cloud-shell/?ef_id=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&OCID=AID2200202_SEM_CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE%3AG%3As&gclid=CjwKCAiA3L6PBhBvEiwAINlJ9Pj1wF0QH8KpGtC5Z4qIy21h5fcsP7tDYtBPxNLP-UMFaIiQY-EEuhoCppEQAvD_BwE#overview). The syntax of the command is: From 856b150f9b9beab6cc82cee4fddd77ba71fdd8d6 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Wed, 26 Jan 2022 13:56:03 -0500 Subject: [PATCH 92/97] Another edit --- .../release/getting_started/02_connect_cloud_account.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index 714f2d1999b..fd9c7a8cf47 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -37,7 +37,7 @@ Set up your BigAnimal account on Azure Marketplace. Your Azure subscription for ### Create Azure Active Directory Application using `create-spn` -To simplify the process of creating an Azure AD Application, EDB provides the [`create-spn`](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/create-spn.sh) script for Azure API users. The script automates the creation of the Active Directory Application. The script is [here](https://github.com/EnterpriseDB/cloud-utilities/tree/main/azure). +To simplify the process of creating an Azure AD Application, EDB provides the `create-spn` script for Azure API users (available [here](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/create-spn.sh)). The script automates the creation of the Active Directory Application. Before using the script, ensure that these utilities are installed on your machine: - [jq command-line JSON processor](https://stedolan.github.io/jq/) From 2f26a256e55dcd924d18437fbe15fdf6447e1fde Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 26 Jan 2022 14:20:11 -0500 Subject: [PATCH 93/97] Fixed syntax of the years option --- .../release/getting_started/02_connect_cloud_account.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index 27b334e5ba1..9f76d372bed 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -51,7 +51,7 @@ The syntax of the command is: curl -sL https://raw.githubusercontent.com/EnterpriseDB/cloud-utilities/main/azure/create-spn.sh | bash -s \ -- --display-name \ ----subscription \ - --years + -- -years ``` Flag and option details: From ce73adb2b77c664652a5a96a6926a14b9e6ff13c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 26 Jan 2022 14:23:35 -0500 Subject: [PATCH 94/97] Changed link to parent folder --- .../release/getting_started/02_connect_cloud_account.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index 831a100b03b..237a5ac32cb 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -37,7 +37,7 @@ Set up your BigAnimal account on Azure Marketplace. Your Azure subscription for ### Create Azure Active Directory Application using `create-spn` -To simplify the process of creating an Azure AD Application, EDB provides the `create-spn` script for Azure API users (available [here](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure/create-spn.sh)). The script automates the creation of the Active Directory Application. +To simplify the process of creating an Azure AD Application, EDB provides the `create-spn` script for Azure API users (available [here](https://github.com/EnterpriseDB/cloud-utilities/blob/main/azure)). The script automates the creation of the Active Directory Application. Before using the script, ensure that these utilities are installed on your machine: - [jq command-line JSON processor](https://stedolan.github.io/jq/) From 098f5033ca16619624c377e38eccf2e80024081d Mon Sep 17 00:00:00 2001 From: Jon Ericson Date: Wed, 26 Jan 2022 11:39:02 -0800 Subject: [PATCH 95/97] Improved error handling --- scripts/source/dispatch_product.py | 13 +++++++++---- scripts/source/livecompare.js | 8 +++++--- 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/scripts/source/dispatch_product.py b/scripts/source/dispatch_product.py index 13e185ba598..90192556c30 100755 --- a/scripts/source/dispatch_product.py +++ b/scripts/source/dispatch_product.py @@ -12,6 +12,7 @@ args = parser.parse_args() import os +import sys commands = {'EnterpriseDB/cloud-native-postgresql': f'{args.workspace}/destination/scripts/source/process-cnp-docs.sh {args.workspace}/source {args.workspace }/destination', @@ -19,10 +20,14 @@ f'mkdir -p {args.workspace}/destination/icons-pkg && \ cp -fr utils/icons-placeholder/output/* {args.workspace}/destination/icons-pkg/', 'EnterpriseDB/LiveCompare': - f'node {args.workspace}/destination/scripts/source/livecompare.js' + f'node {args.workspace}/destination/scripts/source/livecompare.js {args.workspace}/source {args.workspace }/destination' } +if args.repo in commands: + cmd = commands[args.repo] + ret = os.system(cmd) +else: + print(f'The workflow has not been configured for the {args.repo} repo', file=sys.stderr) + ret = 1 -cmd = commands[args.repo] - -ret = os.system(cmd) +sys.exit(ret) diff --git a/scripts/source/livecompare.js b/scripts/source/livecompare.js index 1cf9cf29b89..d18bde2689f 100644 --- a/scripts/source/livecompare.js +++ b/scripts/source/livecompare.js @@ -1,4 +1,4 @@ -// run: node scripts/source/livecompare.js" +// run: node scripts/source/livecompare.js source_path destination_path" // purpose: // Import and convert the LiveCompare docs, rendering them in /product_docs/livecompare/ // @@ -19,7 +19,9 @@ const { exec, execSync } = require("child_process"); const isAbsoluteUrl = require("is-absolute-url"); const fileToMetadata = {}; -const basePath = path.resolve("source/docs/"); +const args = process.argv.slice(2); +const basePath = path.resolve(args[1], 'docs'); +const destination = path.resolve(argv[2]); (async () => { const processor = unified() @@ -47,7 +49,7 @@ const basePath = path.resolve("source/docs/"); const markdownToProcess = mdIndex.nav; const version = mdIndex.site_name.match(/LiveCompare (\d+\.\d+)/)[1]; - const destPath = path.resolve("product_docs", "docs", "livecompare", version); + const destPath = path.resolve(destination, "product_docs", "docs", "livecompare", version); const indexFilename = "index.md"; fileToMetadata[indexFilename] = {}; From dad43570ccb9f047685d720870127f7f0dc7e1fa Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 26 Jan 2022 14:48:20 -0500 Subject: [PATCH 96/97] more cleanup --- .../release/getting_started/02_connect_cloud_account.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx index 237a5ac32cb..e640483cf21 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connect_cloud_account.mdx @@ -58,9 +58,9 @@ Flag and option details: | Flag/option shortcut | Flag/option long name | Description | | -------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------- | -| -d *NAME* | --display-name *NAME* | Name of Azure AD Application. | -| -s *SUBSCRIPTION_ID* | --subscription *SUBSCRIPTION_ID* | Azure Subscription ID used by BigAnimal. | -| -y *YEARS* | --years *YEARS* | Integer value specifying the number of years for which the credentials are valid. The default is one year. | +| -d <display-name> | --display-name <display-name> | Name of Azure AD Application. | +| -s <subscription> | --subscription <subscription> | Azure Subscription ID used by BigAnimal. | +| -y <years> | --years <years> | Integer value specifying the number of years for which the credentials are valid. The default is one year. | | -h | --help | Displays information on the syntax and usage of the script. | The script creates the Azure AD Service Principal and configures its access to Azure resources in the specified subscription. From e31c00caff155c255a4d99cd6b5451d6ead453cf Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Wed, 26 Jan 2022 20:22:06 +0000 Subject: [PATCH 97/97] Fix typos --- scripts/source/livecompare.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/source/livecompare.js b/scripts/source/livecompare.js index d18bde2689f..16a1ee9f592 100644 --- a/scripts/source/livecompare.js +++ b/scripts/source/livecompare.js @@ -20,8 +20,8 @@ const isAbsoluteUrl = require("is-absolute-url"); const fileToMetadata = {}; const args = process.argv.slice(2); -const basePath = path.resolve(args[1], 'docs'); -const destination = path.resolve(argv[2]); +const basePath = path.resolve(args[0], 'docs'); +const destination = path.resolve(args[1]); (async () => { const processor = unified()