Merge pull request #4107 from EnterpriseDB/release/2023-05-18

Release: 2023-05-18

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

@@ -72,7 +72,7 @@ Enabling [Apache Superset](/biganimal/latest/using_cluster/06_analyze_with_super
 
 ## PgBouncer costs
 
-Enabling [PgBouncer](../getting_started/creating_a_cluster/#pgbouncer) to pool your connections incurs additional costs that depend on your cloud provider. In addition to the cloud provider costs, PgBouncer connects to your primary server and requires an IP address. BigAnimal provisions up to three instances per PgBouncer-enabled cluster to ensure that performance is unaffected, so each availability zone receives its own instance of PgBouncer. 
+Enabling [PgBouncer](../getting_started/creating_a_cluster/#pgbouncer) to pool your connections incurs additional costs that depend on your cloud provider. In addition to the cloud provider costs, PgBouncer connects to your primary server and requires an IP address. BigAnimal provisions up to three instances per PgBouncer-enabled cluster to ensure that performance is unaffected, so each availability zone receives its own instance of PgBouncer. The extra VM costs are the 2vcpu SKU times the number of PgBouncer instances. For AWS the instance type is c5.large and for Azure the instance type is F2s_v2.
 
 ## Billing
 

product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx

@@ -3,6 +3,7 @@ title: "Release notes"
 redirects:
   - ../01_whats_new/
 navigation:
+- mp_4.5_rel_notes
 - mp_4.4_rel_notes
 - mp_4.3_rel_notes
 - mp_4.2_rel_notes
@@ -14,6 +15,7 @@ The Migration Portal documentation describes the latest version of Migration Por
 
 | Version | Release date | 
 | ------- | ------------ | 
+| [4.5](mp_4.5_rel_notes) | 18 May 2023  |
 | [4.4](mp_4.4_rel_notes) | 14 Feb 2023  |
 | [4.3](mp_4.3_rel_notes) | 08 Dec 2022  |
 | [4.2](mp_4.2_rel_notes) | 04 Oct 2022  |

product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5_rel_notes.mdx

@@ -0,0 +1,29 @@
+---
+title: "Version 4.5"
+---
+
+
+New features, enhancements, bug fixes, and other changes in Migration Portal 4.5 include the following:
+
+| Type | Description |
+| ---- |------------ |
+| Enhancement | The Migration Portal’s migration complexity and feature analysis capability now captures and reports the presence of the following Oracle features that hadn't previously been captured: `SELECT FOR UPDATE OF`, `ANY with = <> != operators`, `ANY with > < >= <= operators`, `IS JSON CHECK CONSTRAINT`, `LISTAGG ON OVERFLOW`, `UNDER IN TYPE DEFINITION`, `REF IN TYPE SPECIFICATIONS`, `OVERRIDING SUBPROGRAM DECLARATION IN TYPE`, and `OF IN OBJECT VIEW CLAUSE`.  |
+| Enhancement | The EDB DDL Extractor utility now provides you with the option to extract `GRANT` statements only if desired when extracting schemas. Previously, `GRANT` statements were always extracted. Now, you can choose to extract them.  By default, `GRANT` statements aren't extracted. |
+| Enhancement | The Migration Portal now indicates when a project is targeting an EDB Postgres Advanced Server database version that is nearing the end of normal support and to restrict further updates to the project when support for the target database is removed from the Migration Portal. |
+| Enhancement | Migration Portal now shows the project creation date and the Migration Portal version used when the project was created in the **Overview** section of the Migration Portal user interface.  |
+| Enhancement | Migration Portal now detects the `SQLERRM()` function as an incompatible function for target database versions 11 to 14. |
+| Enhancement | Migration Portal has been enhanced with a new repair handler (ERH-2103), which replaces the use of the `= ANY` operator with `IN` and the `!= ANY` operator with `NOT IN`. |
+| Enhancement | Repair handler ERH-2100 now detects and removes `WRITE ON DIRECTORY` grant privileges, which aren't supported by EDB Postgres Advanced Server. |
+| Bug fix | Fixed the issue where some unsupported system grants like `IMPORT FULL` and `EXPORT FULL` weren't being removed by Migration Portal.  |
+| Bug fix | Fixed the issue where the `DBMS_UTILITY.FORMAT_CALL_STACK` and `DBMS_UTILITY.LNAME_ARRAY` functions were incorrectly flagged as being incompatible although they are supported in EDB Postgres Advanced Server.  |
+| Bug fix | Fixed the issue where the `CREATE ROLE` statement wasn't getting extracted for a role that is assigned to another role. |
+| Bug fix | Removed the unnecessary `SET SEARCH_PATH=GLOBAL_OBJECTS` statement from the project export sql file.  |
+| Bug fix | Fixed the issue that was causing the Migration Portal assessment process to error out during the file parsing phase in a specific use case. |
+| Bug fix | Fixed the issue where nested tables that were being extracted and  included in the uploaded source DDL by the Oracle Data Pump utilities was causing a parsing failure.  EDB Postgres Advanced Server doesn't support nested tables.  As a result, they are removed from the source DDL prior to processing and assessment by the Migration Portal.  |
+| Security fix | The ejs library (for Node.js) used by the Migration Portal has been updated to address the security vulnerabilities identified in [CVE-2022-29078](https://nvd.nist.gov/vuln/detail/CVE-2022-29078) and [CVE-2021-23566](https://nvd.nist.gov/vuln/detail/CVE-2021-23566).|
+| Security fix | The terser (NPM) library used by the Migration Portal has been updated to address the security vulnerability identified in [CVE-2022-25858](https://nvd.nist.gov/vuln/detail/CVE-2022-25858). |
+
+## End of support notice
+Since the end of standard support for EDB Postgres Advanced Server (EPAS) version 11 is scheduled for November 20, 2023, more recent versions of EPAS that will be supported beyond 2023 should be selected for new Migration Portal projects.  Support for EPAS 11 is planned to begin being removed from the Migration Portal on May 20, 2023 to help ensure that no new EPAS 11 projects will be created after this date. 
+
+To maximize the length of available support and to take advantage of new features, particularly those that provide additional compatibility with Oracle, EDB recommends selecting the latest EPAS version as the target of a Migration Portal project.  See the EDB [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility#epas) page for more information on the support periods for each EDB Postgres Advanced Server major version. 

product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx

@@ -54,6 +54,8 @@ You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses
 
 5.  When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas.
 
+6.  When prompted, enter `yes`or `no` depending on whether you want to extract grant statements from other schemas.
+
 For example:
 
 1. Run the extractor script:
@@ -96,6 +98,12 @@ For example:
    Extract dependent object from other schemas?(yes/no) (Default no / Ignored for all schemas option): yes
    ```
 
+6. Enter `yes` to extract grant statements:
+
+   ```text
+   Extract GRANT statements?(yes/no) (Default no): yes
+   ```
+
 #### 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.
@@ -108,6 +116,8 @@ After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecti
 
 4.  Enter `yes` or `no` to extract dependent objects and select **OK**. The default is to not extract dependent objects. 
 
+5. Enter `yes` or `no` to extract grant statements and select **OK**. The default setting isn't to extract grant statements.
+
 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

product_docs/docs/migration_portal/4/known_issues_notes.mdx

@@ -218,6 +218,7 @@ While using the Oracle default case, you may experience a lower compatibility ra
 -   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 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.
 -   The EDB DDL Extractor automatically extracts the information for the profiles, roles, and grants.
+-   The EDB DDL Extractor currently doesn't support the extraction of `ROLES`, `SYSTEM GRANTS ON ROLES`, `OBJECT GRANTS ON ROLES`, and `ROLE GRANTS` from Oracle 11g. This results in error messages being written to the extracted files in the sections corresponding to these object types. These errors do not cause any issue in the assessment of these files by Migration Portal.
 
 ## Oracle Data Pump utilities
 
@@ -226,3 +227,5 @@ While using the Oracle default case, you may experience a lower compatibility ra
 - The DDL generated by Oracle Data Pump utilities might contain `ALTER STATEMENTS` such as `ALTER FUNCTION`, `ALTER PACKAGE`, and `ALTER TYPE`, which are not processed by Migration Portal.
 
 - Profiles and roles are not extracted when the Oracle Data Pump is executed in schema mode - that is, when the `SCHEMAS` parameter is used when executing the `expdp` command. If the schema user being exported has a profile assigned to it, the assessment of the schema user object fails in Migration Portal since the profile is not part of the exported `impdp` file. To correct the issue, remove the profile assignment in the user object target DDL and reassess the user creation object. 
+
+- You may see some errors while trying to extract `ROLES`, `SYSTEM GRANTS ON ROLES`, `OBJECT GRANTS ON ROLES`, and `ROLE GRANTS` from Oracle 11g using `impdp` or `expdp` in schema mode. The workaround is to use the `full=y` option, which extracts all the schemas and the mentioned object types without error.

product_docs/docs/tpa/23/reference/distributions.mdx

@@ -14,7 +14,7 @@ and is not suitable for production use.
 !!! Note
 This page is about distribution support on target instances that you
 are deploying *to*, not about the system you are running TPA *from*.
-See the [installation instructions](INSTALL.md#distribution-support) for
+See the [installation instructions](../INSTALL/#distribution-support) for
 more on the latter.
 !!!