Merge pull request #2176 from EnterpriseDB/release/2021-12-30

Release: 2021-12-30

product_docs/docs/biganimal/release/reference/cli.mdx

@@ -185,7 +185,7 @@ Here is a sample configuration file in YAML format:
         instanceType: azure:Standard_E2s_v3     # <string:  instance type id>
         volumeProperties: P1                    # <string:  volume properties id>
         volumeType: azurepremiumstorage         # <string:  volume type id>
-        networking: publish                     # <string:  input "private" or "public" network>
+        networking: public                      # <string:  input "private" or "public" network>
         highAvailability: true                  # <bool:  turn on high-availability>
         ---
 ```

product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/05_db_configuration_parameters.mdx

@@ -11,8 +11,6 @@ The list of parameters is populated based on the type of database you selected o
 
 -   For EDB Postgres Advanced Server, see [Summary of Configuration Parameters](https://www.enterprisedb.com/docs/epas/latest/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/#summary_of_configuration_parameters) and [Configuration Parameters](https://www.enterprisedb.com/docs/epas/latest/epas_guide/03_database_administration/01_configuration_parameters/).
 
--   For additional information on parameters, see [postgresqlco.nf](https://postgresqlco.nf/).
-
 !!!note
 Not all database configuration parameters are supported by BigAnimal. Some parameters, such as `wal_level` and `restore_command`, are reserved for EDB to provide the managed database features of BigAnimal. 
 !!!

product_docs/docs/migration_portal/3.4.0/02_supported_platforms.mdx

@@ -1,27 +1,27 @@
 ---
-title: "Supported Platforms"
+title: "Supported platforms"
 
 
 ---
 
 <div id="supported_platforms" class="registered_link"></div>
 
-The Migration Portal supports assessment and migration from Oracle 11g, 12c, 18c, and 19c to EDB Postgres Advanced Server 10, 11, 12, or 13. Migration Portal is supported on the following browsers and operating systems:
+The Migration Portal supports assessment and migration from Oracle 11g, 12c, 18c, and 19c to EDB Postgres Advanced Server 10, 11, 12, or 13. Migration Portal is supported on the following browsers and operating systems.
 
-**Supported Browsers**
+## Supported browsers
 
 For the best user experience, we recommend using the Google Chrome browser. Migration Portal is also supported on the following browsers:
 
-| **Browser**                  | **Supported Version** |
+| **Browser**                  | **Supported version** |
 | ---------------------------- | --------------------- |
 | Apple Safari on Macintosh OS | 14 and above          |
 | Google Chrome                | 68 and above          |
 | Microsoft Edge               | 42 and above          |
 | Mozilla Firefox              | 60 and above          |
 
-**Supported Operating Systems**
+## Supported operating systems
 
-| **Operating Systems** | **Supported Version** |
+| **Operating systems** | **Supported version** |
 | --------------------- | --------------------- |
 | Macintosh             | OS X Sierra           |
 | Windows               | 10                    |

product_docs/docs/migration_portal/3.4.0/03_mp_using_portal/01_mp_overview_home.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Overview of the Migration Portal Home Page"
+title: "Overview of the Migration Portal home page"
 
 
 legacyRedirectsGenerated:
@@ -13,33 +13,31 @@ The Migration Portal home page provides quick access to migration tools.
 
 ![The Migration Portal home page.](../images/mp_overview_home.png)
 
-*Figure 2-3: The Migration Portal home*
-
 The Migration Portal home page allows access to the following Migration Portal features:
 
-1.  **Projects**: The `Projects` panel displays a list of assessed projects.
+-  **Projects**: The Projects panel displays a list of assessed projects.
 
-2.  **Create project**: Click `+ New` (the button located to the right of the `Projects` label) to create a new project.
+-  **Create project**: Select **+ New** to create a project.
 
 !!!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 on Migration Portal.
 
-3.  **Search projects**: Use the `Search` box to search for projects.
+-  **Search projects**: Use the **Search** box to search for projects.
 
-4.  **Overview**: The `Overview` panel provides details about the selected project and displays the compatibility percentage after schema assessment.
+-  **Overview**: The Overview panel provides details about the selected project and displays the compatibility percentage after schema assessment.
 
-5.  **Migrate to**: Use the `Migrate to` button to either download an EDB Postgres Advanced Server compatible `.sql` file or migrate a schema to an EDB Postgres Advanced Server on-premise or on the cloud. For more information, see [Schema Migration](../04_mp_migrating_database/03_mp_schema_migration/#mp_schema_migration).
+-  **Migrate to**: Select **Migrate to** either to download an EDB Postgres Advanced Server compatible `.sql` file or migrate a schema to an EDB Postgres Advanced Server on premises or in the cloud. For more information, see [Schema migration](../04_mp_migrating_database/03_mp_schema_migration/#mp_schema_migration).
 
-6.  **Report**: Use the `Report` button to view and download the schema assessment report.
+-  **Report**: Select **Report** to view and download the schema assessment report.
 
-7.  **Delete**: Use the `Delete` button to delete a selected project.
+-  **Delete**: Select **Delete** to delete a selected project.
 
-8.  **Warning sign**: A warning message is displayed if a project or a schema is less than 70% compatible or any DDL doesn’t succeed after multiple attempts.
+-  **Warning sign**: A warning message appears if a project or a schema is less than 70% compatible or any DDL doesn’t succeed after multiple attempts.
 
-9.  **Upload DDL file**: Use the `Upload new schema` button to upload a new or additional DDL file.
+-  **Upload DDL file**: Select **Upload new schema** to upload a new DDL file.
 
-10. **Schemas**: The `Schemas` panel displays the assessment result from an uploaded DDL file.
+-  **Schemas**: The Schemas panel displays the assessment result from an uploaded DDL file.
 
-11. **Quick help**: The `Quick help` panel contains quick handles to a few required resources.
+-  **Quick help**: The Quick help panel contains quick links to a few required resources.
 
-12. **Portal Wiki**: The `Portal Wiki` has links to product information and different help guides.
+-  **Portal Wiki**: Select **Portal Wiki** to access links to product information and more help guides.

product_docs/docs/migration_portal/3.4.0/03_mp_using_portal/02_mp_overview_project.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Overview of the Migration Portal Projects Page"
+title: "Overview of the Migration Portal Projects page"
 
 
 legacyRedirectsGenerated:
@@ -13,40 +13,32 @@ The Migration Portal Projects page provides detailed information about your migr
 
 ![The Migration Portal Projects Page overview.](../images/mp_overview_project_numbered.png)
 
-*Figure 2-4: The Migration Portal Projects Page overview*
-
 Use the following resources to gather information about your migration projects:
 
-1.  **Compatible**: The `Compatible` gauge displays the color on the basis of the compatibility percentage of the assessed schema.
+-  **Compatible**: The **Compatible** gauge displays the color on the basis of the compatibility percentage of the assessed schema.
 
-2.  **Schema Count**: Displays the number of schemas in a project.
+-  **Schema Count**: Displays the number of schemas in a project.
 
-3.  **Migrate to**: Use the `Migrate to` to migrate the schema to an *EDB Postgres Advanced Server* on-prmise or on cloud.
+-  **Migrate to**: Select **Migrate to** to migrate the schema to an EDB Postgres Advanced Server on premises or in the cloud.
 
-4.  **Search objects**: Use the `Search` box to search for objects.
+-  **Search objects**: Use the **Search** box to search for objects.
 
-5.  **Filters**: You can filter the system repaired and manual repaired objects from the left panel of the Projects page. In addition, you can select one or more filter combinations to refine the information.
+-  **Filters**: From the left panel of the Projects page, you can filter the system repaired and manual repaired objects. You can select one or more filter combinations to refine the information.
 
-6.  **Objects**: Displays the objects for the selected schemas.
+-  **Objects**: Displays the objects for the selected schemas.
 
-7.  **Common Failures**: Displays the reason for the failed objects for the selected schemas.
+-  **Common Failures**: Displays the reason for the failed objects for the selected schemas.
 
     ![Common Failures tab](../images/mp_whats_new_common_failures.png)
 
-    *Figure 2-5: Common Failures tab*
-
-    !!! Note
-        You can download a `CSV` file for the common failures for the project.
+    You can download a `.csv` file for the common failures for the project.
 
-8.  **Schema**: The `Schema` panel displays the result of the assessment.
+-  **Schema**: Displays the result of the assessment.
 
-9.  **Tooltip**: Hover over a result set to display a tooltip with the number of passed, failed, and repaired objects.
+-  **Tooltip**: Hover over a result set to display a tooltip with the number of passed, failed, and repaired objects.
 
+-  **Quick help**: The Quick help panel displays links to Knowledge Base articles and repair handler documentation.
 
-10. **Quick help**: The `Quick help` panel displays links to Knowledge base articles and repair handler documentation.
-
-11. **Search**: Use the `Search` box to search the `Knowledge base` entries or repair handler documentation for specific information.
+-  **Search**: Use the **Search** box to search the Knowledge Base entries or repair handler documentation for specific information.
 
 ![Searching the Knowledge Base entry.](../images/mp_overview_project_kb.png)
-
-*Figure 2-6: Searching the Knowledge Base entry*

product_docs/docs/migration_portal/3.4.0/03_mp_using_portal/03_mp_overview_wiki.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Overview of the Migration Portal Wiki Page"
+title: "Overview of the Migration Portal wiki page"
 
 
 legacyRedirectsGenerated:
@@ -9,18 +9,16 @@ legacyRedirectsGenerated:
 
 <div id="mp_overview_wiki" class="registered_link"></div>
 
-The Portal Wiki page provides quick access to:
+The Portal wiki page provides quick access to:
 
 -   What’s New information
 -   Quick Start guide
--   Migrating Schema
--   Migrating Data
+-   Migrating schema
+-   Migrating data
 -   DDL Extractor guide
 -   Knowledge Base
 -   Repair handlers
--   Migration Portal User's Guide
+-   Migration Portal User Guide
 -   FAQs
 
 ![The Migration Portal Wiki page.](../images/mp_overview_wiki.png)
-
-*Figure 2-7: The Migration Portal Wiki page*

product_docs/docs/migration_portal/3.4.0/03_mp_using_portal/index.mdx

@@ -9,27 +9,22 @@ legacyRedirectsGenerated:
 
 <div id="mp_using_portal" class="registered_link"></div>
 
-Migration Portal allows you to easily migrate your database schema from Oracle to EDB Postgres Advanced Server. You can upload schemas for assessment and get immediate feedback and suggestions. The portal allows you to download assessed DDLs for all objects and create your EDB Postgres database on-premises or in the cloud.
+Migration Portal allows you to easily migrate your database schema from Oracle to EDB Postgres Advanced Server. You can upload schemas for assessment and get immediate feedback and suggestions. The portal allows you to download assessed DDLs for all objects and create your EDB Postgres database on premises or in the cloud.
 
 ![The assessment and migration process](../images/mp_using_portal.png)
 
-*Figure 2-1: The assessment and migration process*
-
 !!! Note
-    Migration Portal currently does not have team collaboration features. We recommend collaborative meetings, screen sharing, and using the downloadable assessment report to share results.
+    Migration Portal currently doesn't have team collaboration features. We recommend collaborative meetings, screen sharing, and using the downloadable assessment report to share results.
 
 To access the Migration Portal:
 
 1.  Open a browser and navigate to <https://www.enterprisedb.com/>.
 
-2.  On the EnterpriseDB home page, click `PostgreSQL Software` > `Migration` > .
+2.  On the EnterpriseDB home page, select **PostgreSQL Software > Migration**.
 
 ![Migration Portal on the EnterpriseDB home page](../images/mp_enterprisedb_website.png)
 
-*Figure 2-2: Migration Portal on the EnterpriseDB home page*
-
-3. On the Migration Portal page click `Find out more` > `Open Migration Portal`.
-
+3. On the Migration Portal page, select **Find out more > Open Migration Portal**.
 
 4.  Log in using your credentials.
 

product_docs/docs/migration_portal/3.4.0/04_mp_migrating_database/01_mp_schema_extraction.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Performing a Schema Extraction"
+title: "Performing a schema extraction"
 
 
 legacyRedirectsGenerated:
@@ -9,27 +9,27 @@ legacyRedirectsGenerated:
 
 <div id="mp_schema_extraction" class="registered_link"></div>
 
-**Prerequisites**
+## Prerequisites
 
-Before extracting a schema, you must download the latest EDB DDL Extractor script from the Migration Portal `Projects` page or from the link provided in the DDL Extractor guide in the Portal Wiki. The 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.
+Before extracting a schema, you must download the latest EDB DDL Extractor script from the Migration Portal Projects page or from the link provided in the DDL Extractor guide in the Portal wiki. You can run the script in SQL Developer or SQL\*Plus. It uses Oracle’s `DBMS_METADATA` built-in package to extract DDLs for different objects under schemas, which you specify while running the script. The EDB DDL extractor creates the DDL file uploaded to the portal and analyzed for EDB Postgres 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:
 
     `SQL>@edb_ddl_extractor.sql`
 
-2.  Provide the schema name and the path or directory in which the extractor will store the extracted DDL. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter.
+2.  Provide the schema name and the path or directory in which the extractor stores the extracted DDL. 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 that you mention the schema names that you want to extract.
 
 3.  If you want to extract dependent objects from other schemas, enter `yes` or `no`.
 
-    **For example, on Linux:**
+## On Linux
 
 ```text
 Enter a comma separated list of schemas to be extracted (Default all schemas): HR, SCOTT, FINANCE
@@ -42,7 +42,8 @@ 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
@@ -56,83 +57,75 @@ 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 Developers
 
 1.  Connect to the SQL server and run the following command:
 
 ![Enter the path for Linux or Windows.](../images/mp_schema_extraction_paths.png)
 
-*Figure 3-1: Enter the path for Linux or Windows*
-
 2.  Enter a comma-separated list of schemas:
 
 ![Provide a list of schemas.](../images/mp_schema_extraction_list.png)
 
-*Figure 3-2: Provide a list of schemas*
-
 3.  Enter the path for the output file:
 
 ![Specify the output file path.](../images/mp_schema_extraction_target.png)
 
-*Figure 3-3: Specify the output file path*
-
-4.  Enter (yes/no) to extract dependant objects:
+4.  Enter **yes** or **no** to extract dependent objects:
 
 ![Extracting dependent objects.](../images/mp_schema_dependent_objects.png)
 
-*Figure 3-4: Extracting dependent objects*
-
 !!! Note
-    You can also enter single schema name in both SQL\*Plus and SQL Developer.
+    You can also enter a 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, i.e., `c:\Users\Example\Desktop\`.
+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 location entered for the output file.
 
-**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.
--   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 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 name of the objects and rerun the extraction process.
+-   DDL Extractor extracts `nologging` tables as normal tables. Once these tables are migrated to EDB Postgres Advanced Server, `WAL` log files are created.
 -   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.
--   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.
+-   DDL Extractor script doesn't extract schemas whose name starts with `PG_` because PostgreSQL doesn't support this prefix. If you want to extract these schemas, you must change name of schema before extraction.
 
-## Supported Object Types
+## Supported object types
 
 The Migration Portal supports the migration of the following object types:
 
 -   Synonyms
 -   DB Links
--   Types and Type Body
+-   Types and type body
 -   Sequences
 -   Tables
 -   Constraints
 -   Indexes (Except LOB indexes and indexes on materialized views)
 -   Views
--   Materialized Views
+-   Materialized views
 -   Triggers
 -   Functions
 -   Procedures
 -   Packages
 
 !!! Note
-    COMMENTS on Columns, Tables, and Materialized Views are also supported.
+    COMMENTS on columns, tables, and materialized views are also supported.
 
-## Unsupported Object Types
+## Unsupported object types
 
 -   Editions
 -   Operators
 -   Schedulers
--   LOB indexes and Indexes on Materialized Views
--   XML Schemas
+-   LOB indexes and indexes on materialized views
+-   XML schemas
 -   Profiles
--   Role and Object Grants
+-   Role and object grants
 -   Tablespaces
 -   Directories
 -   Users
--   RLS Policy
+-   RLS policy
 -   Queues
 
-## Oracle System Schemas
+## Oracle system schemas
 
-EDB DDL Extractor script will ignore the following system schemas while extracting from Oracle:
+EDB DDL Extractor script ignores the following system schemas while extracting from Oracle:
 
 |                       |                       |                    |
 | --------------------- | --------------------- | ------------------ |