From 3e2ff28d4381f6d58a20cd59e4550c1243192db6 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 25 Apr 2022 12:10:36 -0400 Subject: [PATCH 01/18] Setting up architecture hierarchy for JDBC --- .../09_jdbc42_rhel8_ppcle.mdx | 3 +- .../11_jdbc42_sles15_ppcle.mdx | 3 +- .../12_jdbc42_sles12_ppcle.mdx | 3 +- .../ibm_power_ppc64le/index.mdx | 11 ++++++++ .../index.mdx | 28 +++++++++++-------- .../{ => x86_amd64}/01_jdbc42_rhel8_x86.mdx | 3 +- .../02_jdbc42_other_linux8_x86.mdx | 3 +- .../{ => x86_amd64}/03_jdbc42_rhel7_x86.mdx | 3 +- .../{ => x86_amd64}/04_jdbc42_centos7_x86.mdx | 3 +- .../{ => x86_amd64}/05_jdbc42_sles15_x86.mdx | 3 +- .../{ => x86_amd64}/06_jdbc42_sles12_x86.mdx | 3 +- .../07_jdbc42_ubuntu20_deb10_x86.mdx | 3 +- .../08_jdbc42_ubuntu18_deb9_x86.mdx | 3 +- .../x86_amd64/index.mdx | 16 +++++++++++ .../13_upgrading_rpm_install.mdx | 2 +- .../index.mdx | 6 ---- .../11_mtk55_sles15_ppcle.mdx | 2 +- .../12_mtk55_sles12_ppcle.mdx | 2 +- 18 files changed, 68 insertions(+), 32 deletions(-) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => ibm_power_ppc64le}/09_jdbc42_rhel8_ppcle.mdx (94%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => ibm_power_ppc64le}/11_jdbc42_sles15_ppcle.mdx (93%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => ibm_power_ppc64le}/12_jdbc42_sles12_ppcle.mdx (93%) create mode 100644 product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/01_jdbc42_rhel8_x86.mdx (96%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/02_jdbc42_other_linux8_x86.mdx (95%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/03_jdbc42_rhel7_x86.mdx (96%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/04_jdbc42_centos7_x86.mdx (96%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/05_jdbc42_sles15_x86.mdx (94%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/06_jdbc42_sles12_x86.mdx (96%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/07_jdbc42_ubuntu20_deb10_x86.mdx (93%) rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/{ => x86_amd64}/08_jdbc42_ubuntu18_deb9_x86.mdx (93%) create mode 100644 product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx rename product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/{01_installing_the_connector_with_an_rpm_package => }/13_upgrading_rpm_install.mdx (95%) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/09_jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx similarity index 94% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/09_jdbc42_rhel8_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx index cdcee25b546..a76144b0ea4 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/09_jdbc42_rhel8_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 8 on IBM Power (ppc64le)" +title: "Installing the JDBC Connector on RHEL 8 IBM Power (ppc64le)" +navTitle: "RHEL 8" --- There are two steps to completing an installation: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/11_jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx similarity index 93% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/11_jdbc42_sles15_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx index e781b18afe5..ad0b00093f5 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/11_jdbc42_sles15_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on IBM Power (ppc64le)" +title: "Installing the JDBC Connector on SLES 15 IBM Power (ppc64le)" +navTitle: "SLES 15" --- There are two steps to completing an installation: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/12_jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx similarity index 93% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/12_jdbc42_sles12_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx index ac5e5e5a48a..e468439241b 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/12_jdbc42_sles12_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on IBM Power (ppc64le)" +title: "Installing the JDBC Connector on SLES 12 IBM Power (ppc64le)" +navTitle: "SLES 12" --- There are two steps to completing an installation: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx new file mode 100644 index 00000000000..f535916a71c --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx @@ -0,0 +1,11 @@ +--- +title: "Installing the JDBC Connector on IBM Power (ppc64le)" +navTitle: "IBM Power (ppc64le)" +--- + +For operating system-specific install instructions, see: + + - [RHEL 8](09_jdbc42_rhel8_ppcle) + + - [SLES 15](11_jdbc42_sles15_ppcle) + - [SLES 12](12_jdbc42_sles12_ppcle) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx index c57bd84d4ad..302ee2c9ab2 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx @@ -1,5 +1,9 @@ --- -title: "Installing the Connector with an RPM Package" +title: "Installing the Connector on Linux" +navTitle: "Installing the Connector on Linux" +navigation: +- x86_amd64 +- ibm_power_ppc64le --- To install EDB Postgres Advanced Server JDBC Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). @@ -7,18 +11,18 @@ To install EDB Postgres Advanced Server JDBC Connector, you must have credential For platform-specific install instructions, see: - Linux x86-64 (amd64): - - [RHEL 8/OL 8](01_jdbc42_rhel8_x86) + - [RHEL 8/OL 8](x86_amd64/01_jdbc42_rhel8_x86) - - [Rocky Linux 8/AlmaLinux 8](02_jdbc42_other_linux8_x86) - - [RHEL 7/OL 7](03_jdbc42_rhel7_x86) - - [CentOS 7](04_jdbc42_centos7_x86) - - [SLES 15](05_jdbc42_sles15_x86) - - [SLES 12](06_jdbc42_sles12_x86) - - [Ubuntu 20.04/Debian 10](07_jdbc42_ubuntu20_deb10_x86) - - [Ubuntu 18.04/Debian 9](08_jdbc42_ubuntu18_deb9_x86) + - [Rocky Linux 8/AlmaLinux 8](x86_amd64/02_jdbc42_other_linux8_x86) + - [RHEL 7/OL 7](x86_amd64/03_jdbc42_rhel7_x86) + - [CentOS 7](x86_amd64/04_jdbc42_centos7_x86) + - [SLES 15](x86_amd64/05_jdbc42_sles15_x86) + - [SLES 12](x86_amd64/06_jdbc42_sles12_x86) + - [Ubuntu 20.04/Debian 10](x86_amd64/07_jdbc42_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](x86_amd64/08_jdbc42_ubuntu18_deb9_x86) - Linux on IBM Power (ppc64le): - - [RHEL 8](09_jdbc42_rhel8_ppcle) + - [RHEL 8](ibm_power_ppc64le/09_jdbc42_rhel8_ppcle) - - [SLES 15](11_jdbc42_sles15_ppcle) - - [SLES 12](12_jdbc42_sles12_ppcle) + - [SLES 15](ibm_power_ppc64le/11_jdbc42_sles15_ppcle) + - [SLES 12](ibm_power_ppc64le/12_jdbc42_sles12_ppcle) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/01_jdbc42_rhel8_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx similarity index 96% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/01_jdbc42_rhel8_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx index 0137f58bf7d..9f3cb4f9d96 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/01_jdbc42_rhel8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 8/OL 8 on x86_64" +title: "Installing the JDBC Connector on RHEL 8/OL 8 x86" +navTitle: "RHEL 8/OL 8" --- Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/02_jdbc42_other_linux8_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx similarity index 95% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/02_jdbc42_other_linux8_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx index d15e6bde4db..3e1e76f6e3f 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/02_jdbc42_other_linux8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Rocky Linux 8/AlmaLinux 8 on x86_64" +title: "Installing the JDBC Connector on Rocky Linux 8/AlmaLinux 8 x86" +navTitle: "Rocky Linux 8/AlmaLinux 8" --- Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/03_jdbc42_rhel7_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx similarity index 96% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/03_jdbc42_rhel7_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx index a36eb97e289..2c940fdd316 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/03_jdbc42_rhel7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx @@ -1,5 +1,6 @@ --- -title: "RHEL 7/OL 7 on x86_64" +title: "Installing the JDBC Connector on RHEL 7/OL 7 x86" +navTitle: "RHEL 7/OL 7 " --- Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/04_jdbc42_centos7_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx similarity index 96% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/04_jdbc42_centos7_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx index 02a2a3a7676..8b1edfc5e85 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/04_jdbc42_centos7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx @@ -1,5 +1,6 @@ --- -title: "CentOS 7 on x86_64" +title: "Installing the JDBC Connector on CentOS 7 x86" +navTitle: "CentOS 7" --- Before installing the JDBC Connector, you must install the following prerequisite packages, and request credentials from EDB: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/05_jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx similarity index 94% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/05_jdbc42_sles15_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx index 6c3589816ca..e6eafe654bf 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/05_jdbc42_sles15_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 15 on x86_64" +title: "Installing the JDBC Connector on SLES 15 x86" +navTitle: "SLES 15" --- There are two steps to completing an installation: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/06_jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx similarity index 96% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/06_jdbc42_sles12_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx index 53d4680cd65..e5197d8f89c 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/06_jdbc42_sles12_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx @@ -1,5 +1,6 @@ --- -title: "SLES 12 on x86_64" +title: "Installing the JDBC Connector on SLES 12 x86" +navTitle: "SLES 12" --- To install the connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials for the repository, visit the EnterpriseDB website at: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/07_jdbc42_ubuntu20_deb10_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx similarity index 93% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/07_jdbc42_ubuntu20_deb10_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx index ccf69e51a19..3e11446ddce 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/07_jdbc42_ubuntu20_deb10_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 20.04/Debian 10 on x86_64" +title: "Installing the JDBC Connector on Ubuntu 20.04/Debian 10 x86" +navTitle: "Ubuntu 20.04/Debian 10" --- To install a DEB package 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). diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/08_jdbc42_ubuntu18_deb9_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx similarity index 93% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/08_jdbc42_ubuntu18_deb9_x86.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx index 1cf36640307..1e51408cdb3 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/08_jdbc42_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx @@ -1,5 +1,6 @@ --- -title: "Ubuntu 18.04/Debian 9 on x86_64" +title: "Installing the JDBC Connector on Ubuntu 18.04/Debian 9 x86" +navTitle: "Ubuntu 18.04/Debian 9" --- To install a DEB package 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). diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx new file mode 100644 index 00000000000..ca309bda6cd --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx @@ -0,0 +1,16 @@ +--- +title: "Installing the JDBC Connector on Linux x86 (amd64)" +navTitle: "Intel x86 (amd64)" +--- + +For operating system-specific install instructions, see: + + - [RHEL 8/OL 8](01_jdbc42_rhel8_x86) + + - [Rocky Linux 8/AlmaLinux 8](02_jdbc42_other_linux8_x86) + - [RHEL 7/OL 7](03_jdbc42_rhel7_x86) + - [CentOS 7](04_jdbc42_centos7_x86) + - [SLES 15](05_jdbc42_sles15_x86) + - [SLES 12](06_jdbc42_sles12_x86) + - [Ubuntu 20.04/Debian 10](07_jdbc42_ubuntu20_deb10_x86) + - [Ubuntu 18.04/Debian 9](08_jdbc42_ubuntu18_deb9_x86) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/13_upgrading_rpm_install.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx similarity index 95% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/13_upgrading_rpm_install.mdx rename to product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx index 8a46265d9cf..1a9e00ba1ac 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/13_upgrading_rpm_install.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx @@ -1,5 +1,5 @@ --- -title: Upgrading an RPM Installation +title: Upgrading a Linux 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.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx index 70e19ad4e62..89c866c3c9d 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx @@ -1,12 +1,6 @@ --- title: "Installing and configuring the JDBC Connector" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/installing_and_configuring_the_jdbc_connector.html" - - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.9.1/installing_and_configuring_the_jdbc_connector.html" - - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.8.1/installing_and_configuring_the_jdbc_connector.html" - - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.1/installing_and_configuring_the_jdbc_connector.html" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx index 40012bec8b1..996a2a08215 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/11_mtk55_sles15_ppcle.mdx @@ -1,6 +1,6 @@ --- title: "Installing Migration Toolkit on SLES 15 IBM Power (ppc64le)" -navTitle: "SLES 15 " +navTitle: "SLES 15" --- diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx index 18c008ea2be..28db7141963 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk/install_on_linux/ibm_power_ppc64le/12_mtk55_sles12_ppcle.mdx @@ -1,6 +1,6 @@ --- title: "Installing Migration Toolkit on SLES 12 IBM Power (ppc64le)" -navTitle: "SLES 12 " +navTitle: "SLES 12" --- From 10c8937e7aeda97e53e27ce5d30197da325e5d41 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 26 Apr 2022 08:32:08 -0400 Subject: [PATCH 02/18] updated comment for MP in redirect file --- static/_redirects | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/static/_redirects b/static/_redirects index 55e4821c8bd..af895ab18b1 100644 --- a/static/_redirects +++ b/static/_redirects @@ -114,7 +114,7 @@ /docs/migration_toolkit/55.0.0/* /docs/migration_toolkit/55/:splat 301 # Migration Portal -# Consolidated to latest version +# Add redirect for the n-1 version whenever version is bumped /docs/migration_portal/3.0.1/* /docs/migration_portal/latest/:splat 301 /docs/migration_portal/3.1.0/* /docs/migration_portal/latest/:splat 301 /docs/migration_portal/3.2.0/* /docs/migration_portal/latest/:splat 301 From ad6cd88c5e594348d7e3ec4e8462671e24a4f6aa Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Tue, 26 Apr 2022 09:13:24 -0400 Subject: [PATCH 03/18] Updated product names --- .../ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx | 2 +- .../ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx | 2 +- .../ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx | 2 +- .../ibm_power_ppc64le/index.mdx | 2 +- .../index.mdx | 6 +++--- .../x86_amd64/01_jdbc42_rhel8_x86.mdx | 2 +- .../x86_amd64/02_jdbc42_other_linux8_x86.mdx | 2 +- .../x86_amd64/03_jdbc42_rhel7_x86.mdx | 2 +- .../x86_amd64/04_jdbc42_centos7_x86.mdx | 2 +- .../x86_amd64/05_jdbc42_sles15_x86.mdx | 2 +- .../x86_amd64/06_jdbc42_sles12_x86.mdx | 2 +- .../x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx | 2 +- .../x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx | 2 +- .../x86_amd64/index.mdx | 2 +- .../index.mdx | 2 +- 15 files changed, 17 insertions(+), 17 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx index a76144b0ea4..d559b2b468e 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on RHEL 8 IBM Power (ppc64le)" +title: "Installing EDB JDBC Connector on RHEL 8 IBM Power (ppc64le)" navTitle: "RHEL 8" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx index ad0b00093f5..c39d53eafbb 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/11_jdbc42_sles15_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on SLES 15 IBM Power (ppc64le)" +title: "Installing EDB JDBC Connector on SLES 15 IBM Power (ppc64le)" navTitle: "SLES 15" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx index e468439241b..b2f8ec0488f 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/12_jdbc42_sles12_ppcle.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on SLES 12 IBM Power (ppc64le)" +title: "Installing EDB JDBC Connector on SLES 12 IBM Power (ppc64le)" navTitle: "SLES 12" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx index f535916a71c..86d80a5b95a 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on IBM Power (ppc64le)" +title: "Installing EDB JDBC Connector on IBM Power (ppc64le)" navTitle: "IBM Power (ppc64le)" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx index 302ee2c9ab2..e6b0f8e76cd 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx @@ -1,12 +1,12 @@ --- -title: "Installing the Connector on Linux" -navTitle: "Installing the Connector on Linux" +title: "Installing EDB JDBC Connector on Linux" +navTitle: "Installing EDB JDBC Connector on Linux" navigation: - x86_amd64 - ibm_power_ppc64le --- -To install EDB Postgres Advanced Server JDBC Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). +To install EDB JDBC Connector, you must have credentials that allow access to the EnterpriseDB repository. To request credentials that allow you to access an EnterpriseDB repository, see the [EDB Repository Access instructions](https://www.enterprisedb.com/repository-access-request). For platform-specific install instructions, see: diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx index 9f3cb4f9d96..11f5d4fe54e 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/01_jdbc42_rhel8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on RHEL 8/OL 8 x86" +title: "Installing EDB JDBC Connector on RHEL 8/OL 8 x86" navTitle: "RHEL 8/OL 8" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx index 3e1e76f6e3f..8dada8e9444 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/02_jdbc42_other_linux8_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on Rocky Linux 8/AlmaLinux 8 x86" +title: "Installing EDB JDBC Connector on Rocky Linux 8/AlmaLinux 8 x86" navTitle: "Rocky Linux 8/AlmaLinux 8" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx index 2c940fdd316..1c9a9f89531 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/03_jdbc42_rhel7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on RHEL 7/OL 7 x86" +title: "Installing EDB JDBC Connector on RHEL 7/OL 7 x86" navTitle: "RHEL 7/OL 7 " --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx index 8b1edfc5e85..c15fb02655d 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/04_jdbc42_centos7_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on CentOS 7 x86" +title: "Installing EDB JDBC Connector on CentOS 7 x86" navTitle: "CentOS 7" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx index e6eafe654bf..0ed4265da50 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/05_jdbc42_sles15_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on SLES 15 x86" +title: "Installing EDB JDBC Connector on SLES 15 x86" navTitle: "SLES 15" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx index e5197d8f89c..c6fde3929a0 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/06_jdbc42_sles12_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on SLES 12 x86" +title: "Installing EDB JDBC Connector on SLES 12 x86" navTitle: "SLES 12" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx index 3e11446ddce..38157423804 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/07_jdbc42_ubuntu20_deb10_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on Ubuntu 20.04/Debian 10 x86" +title: "Installing EDB JDBC Connector on Ubuntu 20.04/Debian 10 x86" navTitle: "Ubuntu 20.04/Debian 10" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx index 1e51408cdb3..fca2148dc27 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/08_jdbc42_ubuntu18_deb9_x86.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on Ubuntu 18.04/Debian 9 x86" +title: "Installing EDB JDBC Connector on Ubuntu 18.04/Debian 9 x86" navTitle: "Ubuntu 18.04/Debian 9" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx index ca309bda6cd..118861e9f69 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing the JDBC Connector on Linux x86 (amd64)" +title: "Installing EDB JDBC Connector on Linux x86 (amd64)" navTitle: "Intel x86 (amd64)" --- diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx index 89c866c3c9d..85894a81d6c 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx @@ -1,5 +1,5 @@ --- -title: "Installing and configuring the JDBC Connector" +title: "Installing and configuring EDB JDBC Connector" --- From e6c410910f48077e3a76e0cc7404e9957dc954a2 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 26 Apr 2022 11:32:00 -0400 Subject: [PATCH 04/18] Edited the recent changes to Migration Portal --- .../10_mp_4.0_rel_notes.mdx | 30 ++++---- .../4.0/01_mp_release_notes/index.mdx | 2 +- .../03_mp_using_portal/03_mp_quick_start.mdx | 12 +-- .../01_data_pump_utility.mdx | 67 ++++++++-------- .../01_mp_schema_extraction/index.mdx | 76 +++++++++---------- .../02_mp_schema_assessment.mdx | 33 ++++---- 6 files changed, 103 insertions(+), 117 deletions(-) diff --git a/product_docs/docs/migration_portal/4.0/01_mp_release_notes/10_mp_4.0_rel_notes.mdx b/product_docs/docs/migration_portal/4.0/01_mp_release_notes/10_mp_4.0_rel_notes.mdx index 5725711da38..da7b858247b 100644 --- a/product_docs/docs/migration_portal/4.0/01_mp_release_notes/10_mp_4.0_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4.0/01_mp_release_notes/10_mp_4.0_rel_notes.mdx @@ -10,18 +10,18 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.0 | Enhancement | The Migration Portal now supports the use of the EDB DDL Extractor again. Issues related to the DDL Extractor are resolved and the temporary restriction introduced on the use of DDL Extractor file format has been removed. The Migration Portal continues to support the use of the Oracle Data Pump utilities following the instructions in the [documentation](https://www.enterprisedb.com/docs/migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/); however, the use of the EDB DDL Extractor is recommended.| | Enhancement | The schema assessment algorithms are optimized to address a few performance related issues and to reduce overall schema assessment time.| | Enhancement | Added a repair handler to remove CACHE/NOCACHE keyword from TABLE definition as EDB Postgres Advanced Server does not support it.| -| Security Fix | The jackson-databind and h2 libraries are upgraded to the latest versions to address security issues (CVE-2020-36518, CVE-2022-23221, CVE-2021-42392 and CVE-2021-23463).| -| Bug Fix | Fixed the grammar rule to resolve a parsing error that skipped execution of a repair handler to remove EDITIONABLE keywords.| -| Bug Fix | Fixed the repair handler to perform proper conversion of Oracle PIPELINED and PIPE ROW function calls.| -| Bug Fix | Fixed an issue where the case sensitivity was lost when an object name was based on Unicode characters.| -| Bug Fix | Fixed the issue that displays the Getting Started wizard when Migration Portal landing page is opened for the first time for a new user.| -| Bug Fix | Fixed the issue where a VIEW definition was truncated during transformation in the target EPAS DDL script.| -| Bug Fix | Previously, uploaded DDL files having characters that were not compatible with UTF-8 were failing at the start of the Assessment phase. Migration Portal now reads the SQL files as UTF-8. In case a non UTF-8 file is uploaded, all the characters that are not compatible with UTF-8 will be converted to the replacement character ‘�’ and assessment will continue without failing.| -| Bug Fix | Fixed constraint name assignment for the unnamed constraint in the source Oracle DDL.| -| Bug Fix | Updated the repair handler to remove the OIDINDEX storage clause for Oracle Data Pump generated source DDL files.| -| Bug Fix | Allowed the COLLATE and COMPUTATION keywords to be used as identifiers.| -| Bug Fix | Fixed the handling of multi-line comments that appear as part of single line comments.| -| Bug Fix | Fixed the grammar to properly identify and skip wrapped objects.| -| Bug Fix | Fixed ConcurrentModificationException occurred while running multiple projects simultaneously.| -| Bug Fix | Fixed unique object names handling across multiple schemas. The object names are not required to be unique across different schemas.| -| Bug Fix | Made some fixes in the create table grammar to ignore the order of some clauses as no specific order is required.| +| Security fix | The jackson-databind and h2 libraries are upgraded to the latest versions to address security issues (CVE-2020-36518, CVE-2022-23221, CVE-2021-42392 and CVE-2021-23463).| +| Bug fix | Fixed the grammar rule to resolve a parsing error that skipped execution of a repair handler to remove EDITIONABLE keywords.| +| Bug fix | Fixed the repair handler to perform proper conversion of Oracle PIPELINED and PIPE ROW function calls.| +| Bug fix | Fixed an issue where the case sensitivity was lost when an object name was based on Unicode characters.| +| Bug fix | Fixed the issue that displays the Getting Started wizard when Migration Portal landing page is opened for the first time for a new user.| +| Bug fix | Fixed the issue where a VIEW definition was truncated during transformation in the target EPAS DDL script.| +| Bug fix | Previously, uploaded DDL files having characters that were not compatible with UTF-8 were failing at the start of the Assessment phase. Migration Portal now reads the SQL files as UTF-8. In case a non UTF-8 file is uploaded, all the characters that are not compatible with UTF-8 will be converted to the replacement character ‘�’ and assessment will continue without failing.| +| Bug fix | Fixed constraint name assignment for the unnamed constraint in the source Oracle DDL.| +| Bug fix | Updated the repair handler to remove the OIDINDEX storage clause for Oracle Data Pump generated source DDL files.| +| Bug fix | Allowed the COLLATE and COMPUTATION keywords to be used as identifiers.| +| Bug fix | Fixed the handling of multi-line comments that appear as part of single line comments.| +| Bug fix | Fixed the grammar to properly identify and skip wrapped objects.| +| Bug fix | Fixed ConcurrentModificationException occurred while running multiple projects simultaneously.| +| Bug fix | Fixed unique object names handling across multiple schemas. The object names are not required to be unique across different schemas.| +| Bug fix | Made some fixes in the create table grammar to ignore the order of some clauses as no specific order is required.| diff --git a/product_docs/docs/migration_portal/4.0/01_mp_release_notes/index.mdx b/product_docs/docs/migration_portal/4.0/01_mp_release_notes/index.mdx index 8e8fb7e0724..5ec9a9c3efe 100644 --- a/product_docs/docs/migration_portal/4.0/01_mp_release_notes/index.mdx +++ b/product_docs/docs/migration_portal/4.0/01_mp_release_notes/index.mdx @@ -6,6 +6,6 @@ redirects: The Migration Portal documentation describes the latest version of Migration Portal 4.0. -| Version | Release Date | +| Version | Release date | | ------- | ------------ | | [4.0](10_mp_4.0_rel_notes) | 22 Apr 2022 | \ No newline at end of file diff --git a/product_docs/docs/migration_portal/4.0/03_mp_using_portal/03_mp_quick_start.mdx b/product_docs/docs/migration_portal/4.0/03_mp_using_portal/03_mp_quick_start.mdx index 093c55290a2..445bbdcf0b4 100644 --- a/product_docs/docs/migration_portal/4.0/03_mp_using_portal/03_mp_quick_start.mdx +++ b/product_docs/docs/migration_portal/4.0/03_mp_using_portal/03_mp_quick_start.mdx @@ -3,25 +3,25 @@ title: Migration Portal quick start --- To migrate Oracle schemas using Migration Portal: -1. Generate a .sql file with metadata information of your schemas. For more information, see [Performing a schema extraction](../04_mp_migrating_database/01_mp_schema_extraction). +1. Generate a `.sql` file with metadata information of your schemas. For more information, see [Performing a schema extraction](../04_mp_migrating_database/01_mp_schema_extraction). 1. Log in to [Migration Portal](https://migration.enterprisedb.com/) with your EDB credentials. 1. Create a new project. -1. Upload the .sql file with your schema metadata. +1. Upload the `.sql` file with your schema metadata. !!! Note - Uploading large DDL files might freeze or crash the browser (depending on the browser and the system resources in use). In this scenario, try running Migration Portal in a different browser or extracting fewer schemas and uploading that file into the Migration Portal. + Uploading large DDL files might freeze or crash the browser (depending on the browser and the system resources in use). In this scenario, try running Migration Portal in a different browser or extracting fewer schemas and uploading that file into Migration Portal. 1. Select **Create & assess**. Migration Portal reviews every construct, executes repair actions to improve compatibility with EDB Postgres Advanced Server, and flags any remaining errors that require manual intervention. -1. Verify the DDL objects; for example, TABLES that do not show a 100% success ratio. +1. Verify the DDL objects, for example, TABLES that don't show a 100% success ratio. -1. Select the objects that are not compatible with EDB Postgres Advanced Server. +1. Select the objects that aren't compatible with EDB Postgres Advanced Server. -1. Refer to the Knowledge Base for checking the possible workarounds for the objects that are not compatible in EDB Postgres Advanced Server. +1. Refer to the Knowledge Base for checking the possible workarounds for the objects that aren't compatible in EDB Postgres Advanced Server. 1. Make the required changes and select **Reassess** to rerun the analysis. diff --git a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index dea06db2ee8..035cc3a4d48 100644 --- a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -1,18 +1,17 @@ --- -title: "Extracting schemas using data pump utility -" +title: "Extracting schemas using data pump utility" --- -Migration Portal only requires the metadata in the SQL dump file to assess the extracted schemas. +Migration Portal requires only the metadata in the SQL dump file to assess the extracted schemas. -#### Prerequisites +## Prerequisites -* If you plan on exporting schemas that are not your own, ensure that you are assigned the `DATAPUMP_IMP_FULL_DATABASE` role. Otherwise, you can only export your own schema. +- If you plan on exporting schemas that aren't your own, make sure that you're assigned the `DATAPUMP_IMP_FULL_DATABASE` role. Otherwise, you can export only your own schema. -* Ensure that you have sufficient tablespace quota to create objects in the tablespace. +- Make sure that you have enough tablespace quota to create objects in the tablespace. -* In SQL*Plus, create a directory object that points to a directory on your server file system. For example: +- In SQL\*Plus, create a directory object that points to a directory on your server file system. For example: **On Linux**: @@ -22,32 +21,32 @@ Migration Portal only requires the metadata in the SQL dump file to assess the e `SQL> create directory DMPDIR as 'c:\sample\file\path\';` -* In SQL*Plus, grant read, write permissions to the user running the Data Pump utility. +- In SQL\*Plus, grant read-write permissions to the user running the Data Pump utility. `SQL> grant read,write on directory DMPDIR to ;` Perform either of the following procedures: -* [To extract one or more schemas in a database](#to-extract-one-or-more-schemas-in-a-database) +- [Extract one or more schemas in a database](#extract-one-or-more-schemas-in-a-database) -* [To extract all schemas in a database](#to-extract-all-schemas-in-a-database) +- [Extract all schemas in a database](#extract-all-schemas-in-a-database) -### To extract one or more schemas in a database +### Extract one or more schemas in a database -1. Before running the `expdp` command, create a file with a `.par` extension (for example, export.par) on your server. Add attributes and values to the file, as follows: +1. Before running the `expdp` command, create a file with a `.par` extension (for example, `export.par`) on your server. Add attributes and values to the file: - ``` + ```text CONTENT=metadata_only INCLUDE=SYNONYM,SEQUENCE,TYPE,TABLE,CONSTRAINT,PROCEDURE,FUNCTION,PACKAGE,INDEX,MATERIALIZED_VIEW,VIEW,TRIGGER,DB_LINK ``` - The attributes and values in the above command specify the following options: - + `CONTENT=metadata_only` extracts only the metadata of the schemas. - + `INCLUDE=` specifies which database object types to include in the extraction. Append a comma-separated list of the [Supported object types](../01_mp_schema_extraction/#supported-object-types) to only extract database object types that are supported by Migration Portal. + The attributes and values in this command specify the following options: + - `CONTENT=metadata_only` extracts only the metadata of the schemas. + - `INCLUDE=` specifies the database object types to include in the extraction. Append a comma-separated list of the [Supported object types](../01_mp_schema_extraction/#supported-object-types) to extract only database object types that are supported by Migration Portal. -2. From the command line, run the export command to generate a **schemas_metadata.dump** file. For example, to extract metadata information for ``, ``, ``, and so on, run: +2. From the command line, run the export command to generate a `schemas_metadata.dump` file. For example, to extract metadata information for ``, ``, ``, and so on, run: ```shell expdp @ DIRECTORY=DMPDIR SCHEMAS=,, DUMPFILE=schemas_metadata.dump parfile=export.par @@ -55,43 +54,43 @@ Perform either of the following procedures: 3. To generate a SQL file from the dump file, run the import command. - For example, to generate **YourSchemas.SQL** file from the schemas_metadata.dump file, enter: + For example, to generate a `YourSchemas.SQL` file from the `schemas_metadata.dump` file, enter: ```shell impdp @ DIRECTORY=DMPDIR TRANSFORM=OID:n SQLFILE=YourSchemas.sql DUMPFILE=schemas_metadata.dump ``` -See an important [note](../01_mp_schema_extraction/#a-note-about-file-encoding) about the file encoding format expected by the Migration Portal. +See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. -### To extract all schemas in a database +### Extract all schemas in a database !!! Note - Do not perform the following procedure from a user account that belongs to the excluded schemas list, see [Unsupported schemas](../01_mp_schema_extraction/#unsupported-schemas). The impdp command fails if the user account running the command is in the excluded list of schemas. + Don't perform this procedure from a user account that belongs to the excluded schemas list (see [Unsupported schemas](../01_mp_schema_extraction/#unsupported-schemas)). The `impdp` command fails if the user account running the command is in the excluded list of schemas. -1. Before running the expdp command, create a file with a `.par` extension (for example, export.par) on your server. Add attributes and values to the file, as follows: +1. Before running the `expdp` command, create a file with a `.par` extension (for example, `export.par`) on your server. Add attributes and values to the file: - ``` + ```text CONTENT=metadata_only FULL=Y INCLUDE=SYNONYM,SEQUENCE,TYPE,TABLE,CONSTRAINT,PROCEDURE,FUNCTION,PACKAGE,INDEX,MATERIALIZED_VIEW,VIEW,TRIGGER,DB_LINK ``` - The attributes and values in the above command specify the following options: - + `CONTENT=metadata_only` extracts only the metadata of the schemas. - + `INCLUDE=` specifies which database object types to include in the extraction. Append a comma-separated list of the [Supported object types](../01_mp_schema_extraction/#supported-object-types) to only extract database object types that are supported by Migration Portal. - + `FULL=Y` extracts all schemas in the database. + The attributes and values in this command specify the following options: + - `CONTENT=metadata_only` extracts only the metadata of the schemas. + - `INCLUDE=` specifies the database object types to include in the extraction. Append a comma-separated list of the [Supported object types](../01_mp_schema_extraction/#supported-object-types) to extract only database object types that are supported by Migration Portal. + - `FULL=Y` extracts all schemas in the database. -2. From the command line, run the export command to generate a **schemas_metadata.dump** file, as follows: +2. From the command line, run the export command to generate a `schemas_metadata.dump` file: ```shell expdp @ DIRECTORY=DMPDIR DUMPFILE=schemas_metadata.dump parfile=export.par ``` -3. Before running the impdp command, create a parameter file with a `.par` extension (for example, import.par) on your server. Add attributes and values to the file, as follows: +3. Before running the `impdp` command, create a parameter file with a `.par` extension (for example, `import.par`) on your server. Add attributes and values to the file: - ``` + ```text EXCLUDE=SCHEMA:"IN(select username as schema_name from sys.dba_users where LOWER(username) LIKE 'pg_%' OR username IN ('ANONYMOUS','APEX_PUBLIC_USER','APEX_030200','APEX_040000','APEX_040200','APPQOSSYS','AUDSYS','CTXSYS','DMSYS','DBSNMP', 'DBSFWUSER','DEMO','DIP','DMSYS', 'DVF','DVSYS','EXFSYS','FLOWS_FILES','FLOWS_020100', 'FRANCK','GGSYS','GSMADMIN_INTERNAL', @@ -100,14 +99,14 @@ See an important [note](../01_mp_schema_extraction/#a-note-about-file-encoding) 'SPATIAL_CSW_ADMIN_USR','SPATIAL_WFS_ADMIN_USR','SQLTXADMIN','SQLTXPLAIN','SYS$UMF','SYS','SYSBACKUP','SYSDG','SYSKM', 'SYSRAC','SYSTEM','SYSMAN','TSMSYS','WKPROXY','WKSYS','WK_TEST','WMSYS','XDB','XS$NULL'))" ``` - The attributes and values in the above command specify the following options: - + `EXCLUDE` specifies which schemas to exclude. Append a list of the [Unsupported schemas](../01_mp_schema_extraction/#unsupported-schemas) to ensure that the Data Pump utility *does not* extract any system schemas (including schemas beginning with **pg_**). + The attributes and values in this command specify the following options: + - `EXCLUDE` specifies the schemas to exclude. Append a list of the [Unsupported schemas](../01_mp_schema_extraction/#unsupported-schemas) to ensure that the Data Pump utility doesn't extract any system schemas (including schemas beginning with `pg_`). 4. To generate a SQL file from the dump file, run the import command. - For example, to generate **YourSchemas.SQL** file from the schemas_metadata.dump file, enter: + For example, to generate `YourSchemas.SQL` file from the `schemas_metadata.dump` file, enter: ```shell impdp @ DIRECTORY=DMPDIR TRANSFORM=OID:n SQLFILE=YourSchemas.sql DUMPFILE=schemas_metadata.dump parfile=import.par ``` -See an important [note](../01_mp_schema_extraction/#a-note-about-file-encoding) about the file encoding format expected by the Migration Portal. +See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. diff --git a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index 2e877106c82..a75f02e933a 100644 --- a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -12,44 +12,42 @@ redirects: - You can perform a schema extraction using either of the following methods. EDB recommends using the EDB DDL extractor to extract your schemas. - [EDB DDL extractor](#extracting-schemas-using-the-edb-ddl-extractor) (recommended method) - [Oracle’s Data Pump utility](01_data_pump_utility/) ## Extracting schemas using the EDB DDL Extractor -Download the latest EDB DDL Extractor script from the Migration Portal `Projects` page. +Download the latest EDB DDL Extractor script from the Migration Portal Projects page. !!! Note - Migration Portal might become unresponsive for very large SQL files, depending on your system’s and browser’s resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size. + Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size. -#### Prerequisites +### Prerequisites - The EDB DDL Extractor script can be run in SQL Developer or SQL\*Plus. It uses Oracle’s `DBMS_METADATA` built-in package to extract DDLs for different objects under schemas (specified while running the script). The EDB DDL extractor creates the DDL file uploaded to the portal and analyzed for EDB Postgres compatibility. +You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses Oracle’s `DBMS_METADATA` built-in package to extract DDLs for different objects under schemas (specified while running the script). The EDB DDL extractor creates the DDL file uploaded to the portal and analyzed for EDB Postgres Advanced Server compatibility. - !!! Note You must have `CONNECT` and `SELECT_CATALOG_ROLE` roles and `CREATE TABLE` privilege. -**For SQL\*Plus** +#### For SQL\*Plus -1. Connect to SQL\*Plus and run the command: +1. Connect to SQL\*Plus and run this command: `SQL>@edb_ddl_extractor.sql` -2. When prompted, if the Oracle user that is running the script has the required privileges, select the `Enter` key to continue running the script. +2. When prompted, if the Oracle user that is running the script has the required privileges, press **Enter** to continue running the script. 3. When prompted, provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter. !!! Note - If you want to extract all the user schemas from the current database, do not mention any schema names while extracting. However, it is recommended to mention the schema names that you would like to extract. + If you want to extract all the user schemas from the current database, don't mention any schema names while extracting. However, we recommend mentioning the schema names that you want to extract. -4. When prompted, enter the path or directory in which the extractor will store the extracted DDL. If no path is specified, the extracted DDL will be output to the directory from which the SQL\*Plus command was run. +4. When prompted, enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command. 5. When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas. -**For example, on Linux:** +For example, on Linux: ```text Enter a comma separated list of schemas to be extracted (Default all schemas): HR, SCOTT, FINANCE @@ -62,7 +60,7 @@ Given schema(s) list may contain objects which are dependent on objects from oth Extract dependent object from other schemas?(yes/no) (Default no / Ignored for all schemas option): yes ``` -**On Windows:** +On Windows: ```text Enter comma separated list of schemas to be extracted (Default all schemas): HR, SCOTT, FINANCE @@ -76,48 +74,43 @@ Given schema(s) list may contain objects which are dependent on objects from oth Extract dependent object from other schemas?(yes/no) (Default no / Ignored for all schemas option): yes ``` -**For SQL Developer** +#### For SQL Developer -After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecting to the source Oracle database, run the script. As the script executes, respond to the prompts as they are displayed. +After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecting to the source Oracle database, run the script. As the script executes, respond to the prompts. -1. If the the user for the database connection has the required privileges as listed in the Script Output tab, select the **Yes** button to continue running the script. +1. If the the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script. -2. Enter a comma-separated list of schemas and select the **OK** button to proceed. +2. Enter a comma-separated list of schemas and select **OK**. -3. Enter the path for the output file and select the **OK** button to proceed. - - *Note that if no value is entered, the output file will be generated in the same location as the DDL Extractor script.* +3. Enter the path for the output file and select **OK**. The default is the location of the DDL Extractor script. -4. Enter **yes** or **no** to extract dependant objects and select the **OK** button to proceed. - - *If no value is provided, the script defaults to not extracting dependent objects.* +4. Enter `yes` or `no` to extract dependent objects and select **OK**. The default is to not extract dependent objects. -Output of the DDL Extractor run will be shown in the Script Output tab. The name of the output file will be shown after the Extraction Completed message in the script output. +Output of the DDL Extractor run appears in the Script Output tab. The name of the output file appears after the `Extraction Completed` message in the script output. !!! Note You can also enter single schema name in both SQL\*Plus and SQL Developer. -The script then iterates through the object types in the source database and once the task is completed, the .SQL output is stored at the entered location (e.g., `c:\Users\Example\Desktop\`. +The script then iterates through the object types in the source database. Once the task is completed, the `.SQL` output is stored at the location you entered (e.g., `c:\Users\Example\Desktop\`). -See an important [note](#a-note-about-file-encoding) about the file encoding format expected by the Migration Portal. +See an important [note](#about-file-encoding) about the file encoding format expected by Migration Portal. -**Additional Notes** +### Additional notes -- The EDB DDL Extractor script does not extract objects restored using `Flashback` and still have names like `BIN$b54+4XlEYwPgUAB/AQBWwA==$0`. If you want to extract these objects, you must change the name of the objects and re-run the extraction process. -- The EDB DDL Extractor extracts `nologging` tables as normal tables. Once these tables are migrated to EDB Postgres Advanced Server, WAL log files will be created. -- The EDB DDL Extractor only extracts objects with a VALID status. Any objects that have an INVALID status that are desired to be assessed by the Migration Portal, first need to be updated to be VALID for them to be extracted by the EDB DDL extractor. -- The EDB DDL Extractor does not extract objects that have been obfuscated using the Oracle wrap feature. As such, these objects will not be included in the set of DDL assessed by the Migration Portal. If it is desired that these objects be assessed and migrated to EDB Postgres Advanced Server, the wrapped versions of the objects will need to be replaced with non-wrapped versions. See the [Wrappped Objects](#wrapped-objects) note below for more information. +- The EDB DDL Extractor script doesn't extract objects restored using `Flashback` that still have names like `BIN$b54+4XlEYwPgUAB/AQBWwA==$0`. If you want to extract these objects, you must change the names of the objects and rerun the extraction process. +- The EDB DDL Extractor extracts `nologging` tables as normal tables. Once these tables are migrated to EDB Postgres Advanced Server, WAL log files are created. +- The EDB DDL Extractor extracts objects only with VALID status. For any objects that have INVALID status that you want Migration Portal to assess, first update them to VALID. +- The EDB DDL Extractor doesn't extract objects that were obfuscated using the Oracle wrap feature. As such, these objects aren't included in the set of DDL assessed by the Migration Portal. If you want to assess these objects and migrate them to EDB Postgres Advanced Server, replace the wrapped versions of the objects with nonwrapped versions. See [Wrapped objects](#wrapped-objects) for more information. - The EDB DDL Extractor creates Global Temporary tables to store the schema names and their dependency information. These tables are dropped at the end of successful extraction. -- The EDB DDL Extractor script does not extract schemas whose name starts with `PG_` because PostgreSQL does not support it. If you want to extract these schemas, you must change name of schema before extraction. - +- The EDB DDL Extractor script doesn't extract schemas whose name starts with `PG_` because PostgreSQL doesn't support it. If you want to extract these schemas, you must change the name of the schema before extraction. ## Schemas and objects support -See the following sections for supported and unsupported schemas and objects. +The lists and tables that follow show supported and unsupported schemas and objects. ### Unsupported schemas -See the following table for a list of Oracle systems schemas you must exclude while generating the SQL dump file. +Exclude these Oracle systems schemas while generating the SQL dump file. | | | | | | | :-------------------- | :------------------ | :---------------- | :----------------- | :---------------------- | @@ -136,12 +129,12 @@ See the following table for a list of Oracle systems schemas you must exclude wh | XS$NULL | | !!! Note - EDB Postgres Advanced Server does not support schema names starting with **pg_**. + EDB Postgres Advanced Server doesn't support schema names starting with `pg_`. ### Supported object types - Synonyms -- DB Links +- DB links - Types and type body - Sequences - Tables @@ -174,14 +167,13 @@ See the following table for a list of Oracle systems schemas you must exclude wh ## Wrapped objects -The Migration Portal is not able to assess wrapped objects. As such, if they are included in the extracted DDL, they will not be loaded into the Migration Portal and not included in the count of objects that are assessed. If wrapped objects are to be assessed and migrated to EDB Postgres Advanced server, the DDL file that is uploaded into the Migration Portal will need to include unwrapped versions of the objects. The recommended way of doing this is to replace the wrapped versions in the Oracle database with clear text versions prior to performing the schema extraction. After performing the schema extraction, the objects can be replaced with the wrapped versions. +Migration Portal can't assess wrapped objects. If you include them in the extracted DDL, they aren't loaded into Migration Portal and aren't included in the count of objects that are assessed. If you want to assess wrapped objects and migrate them to EDB Postgres Advanced Server, include unwrapped versions of the objects in the DDL file that you upload to Migration Portal. The recommended way of doing this is to replace the wrapped versions in the Oracle database with clear-text versions before performing the schema extraction. After performing the schema extraction, you can replace the objects with the wrapped versions. -## A note about file encoding +## About file encoding -Migration Portal recommends the .SQL output file be in the UTF-8 encoding format. If a .SQL file with a non UTF-8 encoding is uploaded, all the characters that are not compatible with UTF-8 are converted to the replacement character ‘�’ in the ouput DDL. +Migration Portal recommends the `.SQL` output file be in the UTF-8 encoding format. If you upload a `.SQL` file with non-UTF-8 encoding, all the characters that aren't compatible with UTF-8 are converted to the replacement character ‘�’ in the output DDL. !!! Tip - You can manually convert the extracted file to the UTF-8 format by using the *iconv* utility on Linux or the *LibIconv* utility on Windows. For example, if your database character set is in Latin-1 (ISO-8859-1), you can convert the extracted file to the UTF-8 format, as follows: + You can manually convert the extracted file to the UTF-8 format by using the iconv utility on Linux or the LibIconv utility on Windows. For example, if your database character set is in Latin-1 (ISO-8859-1), you can convert the extracted file to the UTF-8 format, as follows: `iconv -f iso-8859-1 -t UTF-8 sample.sql > sample_utf8.sql` - diff --git a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/02_mp_schema_assessment.mdx b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/02_mp_schema_assessment.mdx index 1b268d05578..0814ea77ac7 100644 --- a/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/02_mp_schema_assessment.mdx +++ b/product_docs/docs/migration_portal/4.0/04_mp_migrating_database/02_mp_schema_assessment.mdx @@ -13,13 +13,13 @@ You can assess an Oracle database schema for compatibility with EDB Postgres Adv ## Perform a schema assessment -1. Navigate to the [Migration Portal](https://migration.enterprisedb.com). +1. Navigate to [Migration Portal](https://migration.enterprisedb.com). 2. Enter your EDB credentials. -3. Select `New` to create a project. +3. Select **New** to create a project. - ![The Migration Portal New project dialog.](../images/mp_schema_assessment_new_project_edited.png) + ![The Migration Portal New project dialog](../images/mp_schema_assessment_new_project_edited.png) 4. In the dialog box, enter the project name in the **Project name** field. @@ -29,29 +29,27 @@ You can assess an Oracle database schema for compatibility with EDB Postgres Adv - Select a source DB and version for the source. - Select the target DB and Version for the target. -6. To upload the .SQL file generated with your schema metadata, select **Choose file**. +6. To upload the `.SQL` file generated with your schema metadata, select **Choose file**. !!! Note - - Don't modify the `.SQL` file. + Don't modify the `.SQL` file. -7. To specify adding a suffix to indexes (_IDX) and constraints (_CON) when creating a project, select the **Add suffix to make object names unique** checkbox. This selection ensures better assessment results, as EDB Postgres Advanced Server doesn't support the same name for tables and indexes, whereas, Oracle does. +7. To specify adding a suffix to indexes (_IDX) and constraints (_CON) when creating a project, select the **Add suffix to make object names unique** check box. This selection ensures better assessment results, as EDB Postgres Advanced Server doesn't support the same name for tables and indexes whereas Oracle does. 8. Select **Create & assess** to create a new project and to assess the schemas. The analysis tool reviews every construct and executes repair actions to improve compatibility with EDB Postgres Advanced Server. It flags any remaining errors that require manual intervention. - 9. Verify the DDL objects (e.g., TABLES) that don't show a 100% success ratio. - 10. Select the objects that aren't compatible with EDB Postgres Advanced Server and view the details. At the bottom of the middle panel, you can view repair action details. -![Incompatible objects are identified.](../images/mp_schema_assessment_incompatible.png) +![Incompatible objects are identified](../images/mp_schema_assessment_incompatible.png) 11. Refer to the Knowledge Base information in the right panel to locate the possible workarounds for the objects that aren't immediately compatible with EDB Postgres Advanced Server. You can also view the Knowledge Base information on the Portal wiki page. -![Incompatible objects are identified.](../images/mp_schema_assessment_errors.png) +![Incompatible objects are identified](../images/mp_schema_assessment_errors.png) 12. On the **Knowledge Base** tab, you can enter the error message for the incompatible objects with EDB Postgres Advanced Server and select **Search**. @@ -62,18 +60,18 @@ You can assess an Oracle database schema for compatibility with EDB Postgres Adv Similarly, you can make all incompatible objects compatible. -![Workaround or resolution for incompatible objects.](../images/mp_schema_assessment_workaround.png) +![Workaround or resolution for incompatible objects](../images/mp_schema_assessment_workaround.png) !!! Note - If the information or workaround for incompatible objects isn't available in the Knowledge Base, contact the support team for help. + If the information or workaround for incompatible objects isn't available in the Knowledge Base, contact the Support team for help. -When you have finished working with the DDL, you can either download the modified EDB compatible DDL as a `.sql` file or migrate the schemas. See [Schema migration](03_mp_schema_migration/#mp_schema_migration). +When you have finished working with the DDL, you can either download the modified EDB-compatible DDL as a `.sql` file or migrate the schemas. See [Schema migration](03_mp_schema_migration/#mp_schema_migration). ## Generate an assessment report -Migration Portal reports provides a high-level assessment summary of the schemas assessed for your project. In addition, the report provides details about the failed objects and the cause of failure. +Migration Portal reports provide a high-level assessment summary of the schemas assessed for your project. In addition, the report provides details about the failed objects and the cause of failure. 1. Select **Report**. @@ -84,9 +82,6 @@ Migration Portal reports provides a high-level assessment summary of the schemas You can optionally select **Generate PDF** to save the report in PDF format. You can also view the count of distinct repair handlers applied to the DDLs under the selected schemas. !!! Note - - Migration Portal does not assess sensitive PL/SQL source code that is hidden in Oracle wrapped objects. These wrapped objects are not included in the assessed objects count, and therefore the true value of compatibility percentage might be different than the value calculated in the assessment report. + Migration Portal doesn't assess sensitive PL/SQL source code hidden in Oracle wrapped objects. These wrapped objects aren't included in the assessed objects count, and therefore the true value of compatibility percentage might be different from the value calculated in the assessment report. -See the note in the [Performing a schema extraction](01_mp_schema_extraction#wrapped-objects) section for more information about wrapped objects. - - +See the note in [Performing a schema extraction](01_mp_schema_extraction#wrapped-objects) for more information about wrapped objects. From 9bfa2034d4de50980d7f7df879fbf62bdef5f376 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 14 Apr 2022 15:58:17 -0400 Subject: [PATCH 05/18] BigAnimal: handling BigAnimal updates --- product_docs/docs/biganimal/release/index.mdx | 1 + .../release/overview/04_responsibility_model.mdx | 1 + product_docs/docs/biganimal/release/updates.mdx | 9 +++++++++ 3 files changed, 11 insertions(+) create mode 100644 product_docs/docs/biganimal/release/updates.mdx diff --git a/product_docs/docs/biganimal/release/index.mdx b/product_docs/docs/biganimal/release/index.mdx index 36403438dd4..df412c53f90 100644 --- a/product_docs/docs/biganimal/release/index.mdx +++ b/product_docs/docs/biganimal/release/index.mdx @@ -12,6 +12,7 @@ navigation: - overview - getting_started - using_cluster + - updates - administering_cluster - pricing_and_billing - migration diff --git a/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx b/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx index 16427e2e887..5c5006086de 100644 --- a/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx +++ b/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx @@ -10,6 +10,7 @@ The following responsibility model describes the distribution of specific respon - EDB is responsible for deploying clusters with one primary and two replicas. In cloud regions with availability zones, clusters are deployed across multiple availability zones. - You are responsible for choosing whether to enable high availability. +- You are responsible for ensuring your application handles transient outages. ## Database performance diff --git a/product_docs/docs/biganimal/release/updates.mdx b/product_docs/docs/biganimal/release/updates.mdx new file mode 100644 index 00000000000..947c5249d3f --- /dev/null +++ b/product_docs/docs/biganimal/release/updates.mdx @@ -0,0 +1,9 @@ +--- +title: Handling BigAnimal updates +--- +EDB regularly pushes updates including bug fixes as well as releases of additional functionality. +EDB notifies you about updates in a banner on the BigAnimal portal. Details are available on the [BigAnimal status page](https://status.biganimal.com/). You can subscribe to get these updates in a feed by selecting **Subscribe to Updates** on the status page. + +These updates may cause transient outages that in some cases may cause clusters to go down. If that happens, the outage should be for a minute or less but it is your responsibility to restart the clusters. These outages are not counted toward the minimum connectivity commitments in the service level agreements. + +To minimize the time your applications are affected by outages, your application needs to be aware of temporary outages and reconnect after those transient outages are over. From 54bf6124d55a7ddf7c026eb6132588d88d675da0 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 14 Apr 2022 16:14:02 -0400 Subject: [PATCH 06/18] moved topic to overview --- product_docs/docs/biganimal/release/index.mdx | 1 - product_docs/docs/biganimal/release/overview/index.mdx | 8 ++++++++ .../docs/biganimal/release/{ => overview}/updates.mdx | 0 3 files changed, 8 insertions(+), 1 deletion(-) rename product_docs/docs/biganimal/release/{ => overview}/updates.mdx (100%) diff --git a/product_docs/docs/biganimal/release/index.mdx b/product_docs/docs/biganimal/release/index.mdx index df412c53f90..36403438dd4 100644 --- a/product_docs/docs/biganimal/release/index.mdx +++ b/product_docs/docs/biganimal/release/index.mdx @@ -12,7 +12,6 @@ navigation: - overview - getting_started - using_cluster - - updates - administering_cluster - pricing_and_billing - migration diff --git a/product_docs/docs/biganimal/release/overview/index.mdx b/product_docs/docs/biganimal/release/overview/index.mdx index 84de73b868d..4bf9a992bdd 100644 --- a/product_docs/docs/biganimal/release/overview/index.mdx +++ b/product_docs/docs/biganimal/release/overview/index.mdx @@ -1,6 +1,14 @@ --- title: "Overview of service" indexCards: simple +navigation: +- 02_high_availability +- 03_security +- 03a_region_support +- 04_responsibility_model +- 05_database_version_policy +- updates +- support --- diff --git a/product_docs/docs/biganimal/release/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx similarity index 100% rename from product_docs/docs/biganimal/release/updates.mdx rename to product_docs/docs/biganimal/release/overview/updates.mdx From 015b240b1b736c3f277e4a56d133aebe785eb627 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Sat, 16 Apr 2022 06:35:27 -0400 Subject: [PATCH 07/18] Option 2: consolidate minor version section --- .../overview/05_database_version_policy.mdx | 17 ++++++----------- .../docs/biganimal/release/overview/updates.mdx | 12 ++++++++---- 2 files changed, 14 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx b/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx index 1337c6b57ec..1cb5d3fd1ce 100644 --- a/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx +++ b/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx @@ -2,19 +2,14 @@ title: "Database version policy" --- -## Supported Postgres types and versions - -| **Postgres type** | **Major versions** | -| ---------------------------- | ------------------ | -| PostgreSQL | 11–14 | -| EDB Postgres Advanced Server | 11–14 | +PostgreSQL and EDB Postgres Advanced Server major versions are supported from the date they are made available until the version is retired by EDB (generally five years). See [Platform Compatibility ](https://www.enterprisedb.com/platform-compatibility#epas) for more details. -## Major version support +## Supported Postgres types and versions -PostgreSQL and EDB Postgres Advanced Server major versions are supported from the date they are made available until the version is retired by EDB (generally five years). See [Platform Compatibility ](https://www.enterprisedb.com/platform-compatibility#epas) for more details. +| **Postgres type** | **Versions** | +| ---------------------------- | ------------ | +| PostgreSQL | 11–14 | +| EDB Postgres Advanced Server | 11–14 | -## Minor version support -EDB performs periodic maintenance to ensure stability and security. EDB performs minor version upgrades and patch updates as part of periodic maintenance. Customers are notified in the BigAnimal portal prior to maintenance occurring. You cannot configure minor versions. -EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance. diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 947c5249d3f..2191eea5ab1 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -1,9 +1,13 @@ --- -title: Handling BigAnimal updates +title: Periodic maintenance --- -EDB regularly pushes updates including bug fixes as well as releases of additional functionality. -EDB notifies you about updates in a banner on the BigAnimal portal. Details are available on the [BigAnimal status page](https://status.biganimal.com/). You can subscribe to get these updates in a feed by selecting **Subscribe to Updates** on the status page. + +EDB performs periodic maintenance to ensure stability and security. EDB performs minor version upgrades and patch updates as part of periodic maintenance. You are notified in the BigAnimal portal prior to maintenance occurring. Details are available on the [BigAnimal status page](https://status.biganimal.com/). You can subscribe to get these updates in a feed by selecting **Subscribe to Updates** on the status page. + +EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance. You cannot configure minor versions. These updates may cause transient outages that in some cases may cause clusters to go down. If that happens, the outage should be for a minute or less but it is your responsibility to restart the clusters. These outages are not counted toward the minimum connectivity commitments in the service level agreements. -To minimize the time your applications are affected by outages, your application needs to be aware of temporary outages and reconnect after those transient outages are over. +## Handling BigAnimal update outages + +To minimize the time your applications are affected by outages, your application needs to be aware of temporary outages and reconnect after those transient outages are over. \ No newline at end of file From 41675b297608f10f23cb62fb5b993dc112c12eb4 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 26 Apr 2022 13:26:19 -0400 Subject: [PATCH 08/18] Update product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx Co-authored-by: Benjamin Anderson <79652654+ba-edb@users.noreply.github.com> --- .../docs/biganimal/release/overview/04_responsibility_model.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx b/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx index 5c5006086de..4e97b1b5557 100644 --- a/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx +++ b/product_docs/docs/biganimal/release/overview/04_responsibility_model.mdx @@ -10,7 +10,7 @@ The following responsibility model describes the distribution of specific respon - EDB is responsible for deploying clusters with one primary and two replicas. In cloud regions with availability zones, clusters are deployed across multiple availability zones. - You are responsible for choosing whether to enable high availability. -- You are responsible for ensuring your application handles transient outages. +- You are responsible for ensuring your applications reconnect when network connectivity is interrupted. ## Database performance From 45cf9d627d8af166f0c949d803160a668871f889 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 26 Apr 2022 13:27:13 -0400 Subject: [PATCH 09/18] Update product_docs/docs/biganimal/release/overview/updates.mdx Co-authored-by: Benjamin Anderson <79652654+ba-edb@users.noreply.github.com> --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index 2191eea5ab1..ae64bdfc7f0 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -2,7 +2,7 @@ title: Periodic maintenance --- -EDB performs periodic maintenance to ensure stability and security. EDB performs minor version upgrades and patch updates as part of periodic maintenance. You are notified in the BigAnimal portal prior to maintenance occurring. Details are available on the [BigAnimal status page](https://status.biganimal.com/). You can subscribe to get these updates in a feed by selecting **Subscribe to Updates** on the status page. +EDB performs periodic maintenance to ensure stability and security of your clusters. EDB performs minor version upgrades and patch updates as part of this periodic maintenance. You are notified in the BigAnimal portal prior to maintenance occurring. Details are available on the [BigAnimal status page](https://status.biganimal.com/). You can subscribe to get these updates in a feed by selecting **Subscribe to Updates** on the status page. EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance. You cannot configure minor versions. From 6444dbdc3f2a634a402deb7fb4bc65f2ca4ff9e0 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 26 Apr 2022 13:29:12 -0400 Subject: [PATCH 10/18] Update product_docs/docs/biganimal/release/overview/updates.mdx Co-authored-by: Benjamin Anderson <79652654+ba-edb@users.noreply.github.com> --- product_docs/docs/biganimal/release/overview/updates.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index ae64bdfc7f0..ee189158dfa 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -6,7 +6,7 @@ EDB performs periodic maintenance to ensure stability and security of your clust EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance. You cannot configure minor versions. -These updates may cause transient outages that in some cases may cause clusters to go down. If that happens, the outage should be for a minute or less but it is your responsibility to restart the clusters. These outages are not counted toward the minimum connectivity commitments in the service level agreements. +In some cases these updates may terminate existing network connections to your clusters. If that happens, the outage should be very brief - typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. ## Handling BigAnimal update outages From be752c9d4097273c38f2da77972ce01186282fb8 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 26 Apr 2022 13:34:21 -0400 Subject: [PATCH 11/18] deleted merged section --- product_docs/docs/biganimal/release/overview/updates.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx index ee189158dfa..b8cc0eec749 100644 --- a/product_docs/docs/biganimal/release/overview/updates.mdx +++ b/product_docs/docs/biganimal/release/overview/updates.mdx @@ -7,7 +7,3 @@ EDB performs periodic maintenance to ensure stability and security of your clust EDB reserves the right to upgrade customers to the latest minor version without prior notice in an extraordinary circumstance. You cannot configure minor versions. In some cases these updates may terminate existing network connections to your clusters. If that happens, the outage should be very brief - typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. - -## Handling BigAnimal update outages - -To minimize the time your applications are affected by outages, your application needs to be aware of temporary outages and reconnect after those transient outages are over. \ No newline at end of file From 0eead224104999d8e30283e4d2edbdfc548a3963 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 26 Apr 2022 13:59:23 -0400 Subject: [PATCH 12/18] fixed capitalization --- .../ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx index d559b2b468e..f1031c6e251 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/09_jdbc42_rhel8_ppcle.mdx @@ -56,7 +56,7 @@ sudo su - dnf -qy module disable postgresql ``` -## Installing the Package +## Installing the package ```shell dnf -y install edb-jdbc From cb6159b420f70f05654bccad63b1147fcf5b9338 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 26 Apr 2022 12:15:59 -0700 Subject: [PATCH 13/18] Update index.mdx --- product_docs/docs/bart/2.6/bart_inst/index.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/bart/2.6/bart_inst/index.mdx b/product_docs/docs/bart/2.6/bart_inst/index.mdx index e42b5c103ed..372b83ffb2d 100644 --- a/product_docs/docs/bart/2.6/bart_inst/index.mdx +++ b/product_docs/docs/bart/2.6/bart_inst/index.mdx @@ -19,16 +19,16 @@ This guide provides information about how to install and configure the EDB Backu ### Supported Platforms and Database Versions -- To view a complete list of supported platforms, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility). - - !!! Note BART is not supported by EDB Postgres Advanced Server or PostgreSQL version 14 and later. EDB strongly recommends you move to Barman or pgBackRest as your backup recovery tool. See [Moving to a New Backup Tool](../bart_migration) for more information. -- BART supports the following database versions: - - Advanced Server versions 9.6, 10, 11, 12, and 13. - - PostgreSQL versions 9.6, 10, 11, 12, and 13. +- To view a complete list of supported platforms, see [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility). + +- BART supports the following database distributions and versions: + + - EDB Postgres Advanced Server versions 10, 11, 12, and 13. + - PostgreSQL versions 10, 11, 12, and 13. ### Software Requirements From e430da7a87f2903a2c83d47da9846be7f6332900 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 26 Apr 2022 12:22:49 -0700 Subject: [PATCH 14/18] Update index.mdx --- product_docs/docs/bart/2.6/bart_qs_8/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 0d2d06a4cd1..0530d43cc70 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 @@ -14,8 +14,8 @@ For detailed information about BART installation and configuration, see the *BAR - BART is tested with the following database versions: - - Advanced Server - 9.6, 10, 11, 12, and 13. - - PostgreSQL - 9.6, 10, 11, 12, and 13. + - EDB Postgres Advanced Server - 10, 11, 12, and 13. + - PostgreSQL - 10, 11, 12, and 13. **Installing BART** From 6655f89d9d3793bc3eb91b2e1183c43ad56ccc55 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 26 Apr 2022 12:23:35 -0700 Subject: [PATCH 15/18] Update index.mdx --- product_docs/docs/bart/2.6/bart_qs_7/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/bart/2.6/bart_qs_7/index.mdx b/product_docs/docs/bart/2.6/bart_qs_7/index.mdx index d02018c5a23..ca8e9789836 100644 --- a/product_docs/docs/bart/2.6/bart_qs_7/index.mdx +++ b/product_docs/docs/bart/2.6/bart_qs_7/index.mdx @@ -14,8 +14,8 @@ For detailed information about BART installation and configuration, see the *BAR - BART is tested with the following database versions: - - Advanced Server - 9.6, 10, 11, 12, and 13. - - PostgreSQL - 9.6, 10, 11, 12, and 13. + - EDB Postgres Advanced Server - 10, 11, 12, and 13. + - PostgreSQL - 10, 11, 12, and 13. From 45092490f4075b3a6dac4de592643f7ac2a421ea Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 26 Apr 2022 12:26:43 -0700 Subject: [PATCH 16/18] Update index.mdx --- product_docs/docs/bart/2.6/bart_qs_7/index.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/bart/2.6/bart_qs_7/index.mdx b/product_docs/docs/bart/2.6/bart_qs_7/index.mdx index ca8e9789836..4e7f443f041 100644 --- a/product_docs/docs/bart/2.6/bart_qs_7/index.mdx +++ b/product_docs/docs/bart/2.6/bart_qs_7/index.mdx @@ -39,9 +39,9 @@ The following steps describe installing BART on CentOS 7.x OS using `yum`. yum makecache ``` -5. Install an Advanced Server or PostgreSQL database server. +5. Install an EDB Postgres Advanced Server or PostgreSQL database server. - To install Advanced Server, execute the following command: + To install EDB Postgres Advanced Server, execute the following command: ```text yum -y install edb-as12-server @@ -53,7 +53,7 @@ The following steps describe installing BART on CentOS 7.x OS using `yum`. sudo su - enterprisedb ``` - Create an Advanced Server cluster named `acctg` on listener port `5444`: + Create an EDB Postgres Advanced Server cluster named `acctg` on listener port `5444`: ```text /usr/edb/as12/bin/initdb -D /var/lib/edb/as12/acctg @@ -72,7 +72,7 @@ The following steps describe installing BART on CentOS 7.x OS using `yum`. ``` !!! 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.53 version for CentOS 7. + The BART host server is not required to have an EDB Postgres Advanced Server or PostgreSQL installation, but must include a copy of the Postgres `libpq` library, the `pg_basebackup` utility program, and Boost Libraries 1.53 version for CentOS 7. 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: @@ -80,7 +80,7 @@ The following steps describe installing BART on CentOS 7.x OS using `yum`. yum install edb-as-server-client ``` - Where <xx> is the Advanced Server version. + Where <xx> is the EDB Postgres Advanced Server version. 7. As a root user, execute the following command to install BART: From 3be5ae0671bee1eabc03f5b93bb804d9ae75cadd Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 26 Apr 2022 12:29:47 -0700 Subject: [PATCH 17/18] Update index.mdx --- product_docs/docs/bart/2.6/bart_qs_8/index.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) 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 0530d43cc70..0b13a9b6bfe 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 @@ -37,9 +37,9 @@ The following steps describe installing BART on Rocky Linux 8.x OS. dnf makecache ``` -5. Install an Advanced Server or PostgreSQL database server. +5. Install an EDB Postgres Advanced Server or PostgreSQL database server. - To install Advanced Server, execute the following command: + To install EDB Postgres Advanced Server, execute the following command: ```text dnf -y install edb-as12-server @@ -51,7 +51,7 @@ The following steps describe installing BART on Rocky Linux 8.x OS. sudo su - enterprisedb ``` - Create an Advanced Server cluster named `acctg` on listener port `5444`: + Create an EDB Postgres Advanced Server cluster named `acctg` on listener port `5444`: ```text /usr/edb/as12/bin/initdb -D /var/lib/edb/as12/acctg @@ -70,7 +70,7 @@ The following steps describe installing BART on Rocky Linux 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 Rocky Linux 8. + The BART host server is not required to have a full EDB Postgres 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: @@ -253,7 +253,7 @@ If backups are to be taken from a given database server host, but restored to a An example of how to create a passwordless connection is documented in the *EDB Backup and Recovery Reference Guide*, available at the [EDB website](/bart/latest/bart_ref/). -Even when the Advanced Server database is on the same host as BART, and the Advanced Server database cluster owner is also the BART user account, a passwordless SSH/SCP connection must be established from the same user account to itself. +Even when the EDB Postgres Advanced Server database is on the same host as BART, and the EDB Postgres Advanced Server database cluster owner is also the BART user account, a passwordless SSH/SCP connection must be established from the same user account to itself. 1. On the database server, navigate into the target user account’s home directory to check for an existing `.ssh` subdirectory. If it does does not exist, create one in the user account’s home directory with the required privileges. From 33f2907c447e43e6ee6af031ad49cd8d257d5ae4 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Tue, 26 Apr 2022 20:30:54 +0000 Subject: [PATCH 18/18] re-add legacy redirects --- .../index.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx index 85894a81d6c..c875bc572f9 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx @@ -1,6 +1,11 @@ --- title: "Installing and configuring EDB JDBC Connector" - +legacyRedirectsGenerated: + # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. + - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.3/installing_and_configuring_the_jdbc_connector.html" + - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.9.1/installing_and_configuring_the_jdbc_connector.html" + - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.8.1/installing_and_configuring_the_jdbc_connector.html" + - "/edb-docs/d/jdbc-connector/user-guides/jdbc-guide/42.2.12.1/installing_and_configuring_the_jdbc_connector.html" ---