Merge pull request #2961 from EnterpriseDB/release/2022-07-20

Release: 2022-07-20

install_template/deploy.mjs

@@ -216,6 +216,12 @@ const moveDoc = async (product, platform, version) => {
       (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_sles12_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "SLES 15"}}, 
       (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_sles15_${fmtArchFilename(ctx)}.mdx`),
+    when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "Debian 10"}}, 
+      (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_deb10_${fmtArchFilename(ctx)}.mdx`),
+    when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "Ubuntu 18.04"}}, 
+      (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_ubuntu18_${fmtArchFilename(ctx)}.mdx`),
+    when({product: {name: "MySQL Foreign Data Wrapper", version: 2}, platform: {name: "Ubuntu 20.04"}}, 
+      (ctx) => `mysql_data_adapter/2/04_installing_the_mysql_data_adapter/${fmtArchPath(ctx)}/${prefix[plat]}_mysql_ubuntu20_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 12"}}, 
       (ctx) => `ocl_connector/${ctx.product.version}/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/${fmtArchPath(ctx)}/ocl_connector14_sles12_${fmtArchFilename(ctx)}.mdx`),
     when({product: {name: "EDB OCL Connector"}, platform: {name: "SLES 15"}}, 

install_template/templates/platformBase/debian.njk

@@ -16,11 +16,11 @@ apt-get -y install apt-transport-https
 #  Add the EDB signing key. Substitute your EnterpriseDB credentials
 #  for the '<USERNAME>' and '<PASSWORD>' placeholders.
 wget -q -O - https://<USERNAME>:<PASSWORD>@apt.enterprisedb.com/edb-deb.gpg.key  | sudo apt-key add -
-
+{% block mysqlfdw %}
 #  Update the repository metadata:
 apt-get update
 ```
-{% endblock prerequisites %}
+{% endblock mysqlfdw %}{% endblock prerequisites %}
 
 {% block installCommand %}{% block odbcconnector %}
 ```shell

install_template/templates/platformBase/sles-12.njk

@@ -14,7 +14,7 @@ zypper install SUSEConnect
 # Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE 
 # registration information
 SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'
-
+{% block mysqlfdw %}{% endblock mysqlfdw %}
 # Activate the required SUSE module
 {% block activateSUSEmodule %}SUSEConnect -p PackageHub/12.5/{{ platform.arch }}
 SUSEConnect -p sle-sdk/12.5/{{ platform.arch }}

install_template/templates/platformBase/ubuntu.njk

@@ -15,11 +15,11 @@ apt-get -y install apt-transport-https
 #  Add the EDB signing key. Substitute your EnterpriseDB credentials
 #  for the '<USERNAME>' and '<PASSWORD>' placeholders.
 wget -q -O - https://<USERNAME>:<PASSWORD>@apt.enterprisedb.com/edb-deb.gpg.key  | sudo apt-key add -
-
+{% block mysqlfdw %}
 #  Update the repository metadata:
 apt-get update
 ```
-{% endblock prerequisites %}
+{% endblock mysqlfdw %}{% endblock prerequisites %}
 
 {% block installCommand %}{% block odbcconnector %}
 ```shell

install_template/templates/products/mysql-foreign-data-wrapper/base.njk

@@ -1,6 +1,6 @@
 {% extends "platformBase/" + platformBaseTemplate + '.njk' %}
-{% set packageName %}edb-as14-mysql8_fdw{% endset %}
+{% set packageName %}edb-as<xx>-mysql<y>-fdw{% endset %}
 {% block installCommand %}
 {{ super() }}
-{% include "platformBase/_epasVersionInPackageName.njk" %}
+Where `<xx>` is the version of EDB Postgres Advanced server and `<y>` is the version of MySQL to be installed. For example if EDB Postgres Version is 13 and MySQL version is 8 then the package name is `edb-as13-mysql8-fdw`.
 {% endblock installCommand %}

install_template/templates/products/mysql-foreign-data-wrapper/debian-10.njk

@@ -1,2 +1,19 @@
 {% extends "products/mysql-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "debian-10" %}
+{% set platformBaseTemplate = "debian-10" %}
+{% block mysqlfdw %}
+# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command:
+apt-get remove  libmysqlclient-dev
+
+# Enable the MySQL repo:
+# For MySQL 8:
+sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee  /etc/apt/sources.list.d/mysql.list
+# For MySQL 5:
+sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee  /etc/apt/sources.list.d/mysql.list
+
+# Add the mysql repo key using the following commands:
+sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5
+
+#  Update the repository metadata:
+apt-get update
+```
+{% endblock mysqlfdw %}

install_template/templates/products/mysql-foreign-data-wrapper/sles-12.njk

@@ -1,34 +1,11 @@
 {% extends "products/mysql-foreign-data-wrapper/base.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
-{% block prerequisites %}
-Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps.
-```shell
-# Install the repository configuration and enter your EDB repository
-# credentials when prompted
-zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo
-
-# Install SUSEConnect to register the host with SUSE, allowing access 
-# to SUSE repositories
-zypper install SUSEConnect
-
-# Register the host with SUSE, allowing access to SUSE repositories
-# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE registration 
-# information
-SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'
-
+{% block mysqlfdw %}
 # Install the MySQL community repository
 wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm
 rpm --import /etc/RPM-GPG-KEY-mysql-2022
 
 # Enable the MySQL8 repository and disable the MySQL 5 repository
 zypper modifyrepo -e mysql80-community
 zypper modifyrepo -d mysql57-community
-
-# Activate the required SUSE modules
-SUSEConnect -p PackageHub/12.5/x86_64
-SUSEConnect -p sle-sdk/12.5/x86_64
-
-# Refresh the metadata
-zypper refresh
-```
-{% endblock prerequisites %}
+{% endblock mysqlfdw %}

install_template/templates/products/mysql-foreign-data-wrapper/sles-12_ppc64le.njk

@@ -1,26 +1,3 @@
-{% extends "products/mysql-foreign-data-wrapper/base.njk" %}
+{% extends "products/mysql-foreign-data-wrapper/sles-12.njk" %}
 {% set platformBaseTemplate = "sles-12" %}
-{% block prerequisites %}
-Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps.
-```shell
-# Install the repository configuration and enter your EDB repository
-# credentials when prompted
-zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo
-
-# Install SUSEConnect to register the host with SUSE, allowing access 
-# to SUSE repositories
-zypper install SUSEConnect
-
-# Register the host with SUSE, allowing access to SUSE repositories
-# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE 
-# registration information
-SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'
-
-# Activate the required SUSE modules
-SUSEConnect -p PackageHub/12.5/ppc64le
-SUSEConnect -p sle-sdk/12.5/ppc64le
-
-# Refresh the metadata
-zypper refresh
-```
-{% endblock prerequisites %}
+{% set includePPC = true %}

install_template/templates/products/mysql-foreign-data-wrapper/sles-15.njk

@@ -1,29 +1,11 @@
 {% extends "products/mysql-foreign-data-wrapper/base.njk" %}
 {% set platformBaseTemplate = "sles-15" %}
-{% block prerequisites %}
-Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps.
-```shell
-# Install the repository configuration and enter your EDB repository
-# credentials when prompted
-zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo
-
-# Install SUSEConnect to register the host with SUSE, allowing access 
-# to SUSE repositories
-zypper install SUSEConnect
-
-# Register the host with SUSE, allowing access to SUSE repositories
-# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE 
-# registration information
-SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'
-
-# Activate the required SUSE module
-SUSEConnect -p PackageHub/15.3/x86_64
-
-# Install the community MySQL repository
-rpm -i https://dev.mysql.com/get/mysql80-community-release-sl15-5.noarch.rpm
+{% block mysqlfdw %}
+# Install the MySQL community repository
+wget https://dev.mysql.com/get/mysql80-community-release-sles12-5.noarch.rpm
 rpm --import /etc/RPM-GPG-KEY-mysql-2022
 
-# Refresh the metadata
-zypper refresh
-```
-{% endblock prerequisites %}
+# Enable the MySQL8 repository and disable the MySQL 5 repository
+zypper modifyrepo -e mysql80-community
+zypper modifyrepo -d mysql57-community
+{% endblock mysqlfdw %}

install_template/templates/products/mysql-foreign-data-wrapper/sles-15_ppc64le.njk

@@ -1,30 +1,3 @@
-{% extends "products/mysql-foreign-data-wrapper/base.njk" %}
+{% extends "products/mysql-foreign-data-wrapper/sles-15.njk" %}
 {% set platformBaseTemplate = "sles-15" %}
-{% set includePPC = true %}
-{% block prerequisites %}
-Setting up the repository is a one time task. If you have already set up your repository, you do not need to perform these steps.
-```shell
-# Install the repository configuration and enter your EDB repository
-# credentials when prompted
-zypper addrepo https://zypp.enterprisedb.com/suse/edb-sles.repo
-
-# Install SUSEConnect to register the host with SUSE, allowing access 
-# to SUSE repositories
-zypper install SUSEConnect
-
-# Register the host with SUSE, allowing access to SUSE repositories
-# Replace 'REGISTRATION_CODE' and 'EMAIL' with your SUSE 
-# registration information
-SUSEConnect -r 'REGISTRATION_CODE' -e 'EMAIL'
-
-# Activate the required SUSE module
-SUSEConnect -p PackageHub/15.3/{{ platform.arch }}
-
-# Install the community MySQL repository
-rpm -i https://dev.mysql.com/get/mysql80-community-release-sl15-5.noarch.rpm
-rpm --import /etc/RPM-GPG-KEY-mysql-2022
-
-# Refresh the metadata
-zypper refresh
-```
-{% endblock prerequisites %}
+{% set includePPC = true %}

install_template/templates/products/mysql-foreign-data-wrapper/ubuntu-18.04.njk

@@ -1,2 +1,19 @@
 {% extends "products/mysql-foreign-data-wrapper/base.njk" %}
-{% set platformBaseTemplate = "ubuntu-18.04" %}
+{% set platformBaseTemplate = "ubuntu-18.04" %}
+{% block mysqlfdw %}
+# If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command:
+apt-get remove  libmysqlclient-dev
+
+# Enable the MySQL repo:
+# For MySQL 8:
+echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee  /etc/apt/sources.list.d/mysql.list
+# For MySQL 5:
+echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee  /etc/apt/sources.list.d/mysql.list
+
+# Add the mysql repo key using the following commands:
+apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5
+
+# Update the repository metadata:
+apt-get update
+```
+{% endblock mysqlfdw %}

product_docs/docs/biganimal/release/pricing_and_billing/index.mdx

@@ -62,6 +62,10 @@ At list price, estimated overall monthly management costs are $400–$600 fo
 
 To get a better sense of your AWS costs, check out the AWS pricing [calculator](https://calculator.aws/#/) and reach out to [BigAnimal Support](../overview/support).  
 
+## Apache Superset costs
+
+Enabling [Apache Superset](/biganimal/latest/using_cluster/06_analyze_with_superset/) to analyze your data has an additional cost. In most cases the costs are approximately $150 per month, based on your cloud provider, instance and storage type selections, and other factors.
+
 ## Billing
 
 If you're using Microsoft Azure Marketplace, all billing is handled directly by Microsoft Azure. This includes infrastructure costs as well as database costs. For database costs, Microsoft bills on actual hours in a given month. You can view invoices and usage on the Microsoft Azure Portal billing page. [Learn more](https://docs.microsoft.com/en-us/azure/cost-management-billing/).

product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/02_connecting_from_aws/01_vpc_endpoint.mdx

@@ -92,11 +92,11 @@ Now that your endpoint service is created, you can connect it to the cluster VPC
 
 1. In your AWS account connected to BigAnimal, select **VPCs** and then select **Endpoint services**. 
 
-1. Select the endpoint service instance you created previously and accept the connection. 
+1. Select the endpoint service instance you created previously and accept the endpoint connection request under **Endpoint connections**. 
 
 1. You can now successfully connect to your cluster.
 
- In your application's AWS account, select the **Load Balancers** service, search for the load balancer with cluster ID you want to access, and use the DNS name provided in the details section to access your cluster.
+ In your application's AWS account, select **VPC** and then select **Endpoints**. Select the endpoint you created previously and use the DNS name provided in the details section to access your cluster.
 
     ```shell     
     $ psql -h vpce-XXXXXXXXXXXXXXXXXXXX.eu-west-1.vpce.amazonaws.com -U edb_admin      

product_docs/docs/migration_toolkit/55/02_supported_operating_systems_and_database_versions.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Supported operating systems and database versions"
+title: "Supported platforms and databases"
 
 ---
 

product_docs/docs/migration_toolkit/55/04_functionality_overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Functionality overview"
+title: "Overview"
 
 ---
 
@@ -67,3 +67,28 @@ Migration Toolkit can migrate immediately and directly into a Postgres database
 By default, Migration Toolkit creates objects directly into a Postgres database. Alternatively, include the `-offlineMigration` option to generate SQL scripts you can use later to reproduce the migrated objects or data in a new database. You can alter migrated objects by customizing the migration scripts generated by Migration Toolkit before you execute them. With the `-offlineMigration` option, you can schedule the actual migration at a time that best suits your system load.
 
 For more information about the `-offlineMigration` option, see [Offline migration options](08_mtk_command_options/#offline_migration).
+
+## Limitations
+
+EDB Postgres Advanced Server offers complete support for some Oracle features and partial support for others. Migration Toolkit can't migrate any object that uses an unsupported feature.
+
+In some cases, Migration Toolkit can migrate objects that use features that offer partial compatibility. In other cases, EDB Postgres Advanced Server supports suitable workarounds.
+
+Full-text search is an example of functionality that isn't fully compatible with Oracle. The EDB Postgres Advanced Server database has included support for full-text search for quite some time, but the implementation is different from Oracle's. Migration Toolkit can't migrate objects that use this feature.
+
+EDB Postgres Advanced Server doesn't yet support other features. Features in this category include Automated Storage Management, table compression, and external tables. You can often implement a successful workaround:
+
+-   You can replace Automated Storage Management with system-specific volume management software.
+-   You can implement table compression by storing data in a tablespace that resides on a compressed filesystem.
+-   External tables don't exist in EDB Postgres Advanced Server, but you can load flat text files into staging tables in the database. We recommend using the EDB\*Loader utility to load the data into an EDB Postgres Advanced Server database quickly.
+-   When migrating multiple profiles from an Oracle database into EDB Postgres Advanced Server, you must manually assign the profile to a user or users when the migration completes.
+
+
+### Unsupported Postgres features
+
+Migration Toolkit doesn't support migration of the following Postgres features:
+
+-   `OPERATOR CLASS`
+-   `OPERATOR FAMILY`
+
+For information about `OPERATOR CLASS` and `OPERATOR FAMILY`, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/indexes-opclass.html).

product_docs/docs/migration_toolkit/55/05_installing_mtk/index.mdx

@@ -1,5 +1,6 @@
 ---
 title: "Installing Migration Toolkit"
+navTitle: "Installing"
 legacyRedirects:
   - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_mac.html"
   - "/edb-docs/d/edb-postgres-migration-toolkit/user-guides/user-guide/55.0.0/installing_on_debian_or_ubuntu.html"

product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Building the toolkit.properties file"
+title: "Specifying connection properities"
 
 ---
 

product_docs/docs/migration_toolkit/55/08_mtk_command_options.mdx → product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx

@@ -1,6 +1,9 @@
 ---
 title: "Migration Toolkit command options"
+navTitle: "Command options"
 
+redirects:
+  - /migration_toolkit/latest/08_mtk_command_options/
 ---
 
 <div id="mtk_command_options" class="registered_link"></div>

product_docs/docs/migration_toolkit/55/07_invoking_mtk.mdx → product_docs/docs/migration_toolkit/55/07_invoking_mtk/index.mdx

@@ -15,6 +15,9 @@ On Windows, the executable is located in:
 
 `C:\Program Files\edb\mtk\bin`
 
+See [Migration Toolkit command options](08_mtk_command_options) for information on controlling details of the migration.
+
+
 !!! Note
     If the following error appears upon invoking the Migration Toolkit, check the file permissions of the `toolkit.properties` file.
 

product_docs/docs/migration_toolkit/55/11_unsupported_features.mdx

@@ -1,38 +1,8 @@
 ---
-title: "Unsupported features"
+title: "FAQ"
 
 ---
 
-<div id="unsupported_features" class="registered_link"></div>
-
-EDB Postgres Advanced Server offers complete support for some Oracle features and partial support for others. Migration Toolkit can't migrate any object that uses an unsupported feature.
-
-In some cases, Migration Toolkit can migrate objects that use features that offer partial compatibility. In other cases, EDB Postgres Advanced Server supports suitable workarounds.
-
-Full-text search is an example of functionality that isn't fully compatible with Oracle. The EDB Postgres Advanced Server database has included support for full-text search for quite some time, but the implementation is different from Oracle's. Migration Toolkit can't migrate objects that use this feature.
-
-EDB Postgres Advanced Server doesn't yet support other features. Features in this category include Automated Storage Management, table compression, and external tables. You can often implement a successful workaround:
-
--   You can replace Automated Storage Management with system-specific volume management software.
--   You can implement table compression by storing data in a tablespace that resides on a compressed filesystem.
--   External tables don't exist in EDB Postgres Advanced Server, but you can load flat text files into staging tables in the database. We recommend using the EDB\*Loader utility to load the data into an EDB Postgres Advanced Server database quickly.
--   When migrating multiple profiles from an Oracle database into EDB Postgres Advanced Server, you must manually assign the profile to a user or users when the migration completes.
-
-<div id="unsupported_pg_features" class="registered_link"></div>
-
-## Unsupported Postgres features
-
-Migration Toolkit doesn't support migration of the following Postgres features:
-
--   `OPERATOR CLASS`
--   `OPERATOR FAMILY`
-
-For information about `OPERATOR CLASS` and `OPERATOR FAMILY`, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/indexes-opclass.html).
-
-<div id="faq" class="registered_link"></div>
-
-## Frequently asked questions
-
 **Does Migration Toolkit support the migration of packages?**
 
 Migration Toolkit supports the migration of packages from an Oracle database into EDB Postgres Advanced Server. See [Functionality overview](04_functionality_overview/#functionality_overview) for information about the migration support offered by EDB Postgres Advanced Server.

product_docs/docs/migration_toolkit/55/13_upgrading_rpm_install.mdx

@@ -1,8 +1,8 @@
 ---
-title: Upgrading an RPM installation
+title: Upgrading
 ---
 
-If you have an existing RPM installation, you can use `yum` to upgrade your repository configuration file and update to a more recent product version. To update the edb.repo file, assume superuser privileges and enter:
+If you have an existing RPM installation, you can use `yum` (or the appropriate package manager for your operating system) 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:
 
 ```text
 yum upgrade edb-repo