From bc233be651ab908c63f4e0b649482f92bcc69194 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 9 Oct 2023 11:26:05 +0530 Subject: [PATCH 1/8] Added new file without content for release notes --- .../4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx new file mode 100644 index 00000000000..ea68249e269 --- /dev/null +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx @@ -0,0 +1,11 @@ +--- +title: "Migration Portal 4.5.2 release notes" +navTitle: Version 4.5.2 +--- + +Released: + +New features, enhancements, bug fixes, and other changes in Migration Portal 4.5.2 include the following: + +| Type | Description | +| ---- |------------ | From 744209aca5aebe2dcb2cadbbaa2fc0f1c0a07e55 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 9 Oct 2023 10:53:23 -0400 Subject: [PATCH 2/8] Recommended updates --- product_docs/docs/migration_portal/4/known_issues_notes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/migration_portal/4/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/known_issues_notes.mdx index 91e84ab36cd..e0c157eb212 100644 --- a/product_docs/docs/migration_portal/4/known_issues_notes.mdx +++ b/product_docs/docs/migration_portal/4/known_issues_notes.mdx @@ -27,7 +27,7 @@ Migration Portal recommends the `.SQL` output file be in the UTF-8 encoding form ### ALTER statements -Except for ALTER TABLE and ALTER TRIGGER, Migration Portal doesn't process any other ALTER statements in the DDL. +Except for `ALTER PROFILE DEFAULT`, `ALTER TABLE` and `ALTER TRIGGER`, Migration Portal doesn't process any other `ALTER` statements in the DDL. ### Users, roles, profiles, and grants @@ -53,7 +53,7 @@ When migrating users, the Migration Portal does not migrate the users' passwords #### Profiles -The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server only supports the Oracle password related limits. Resource limits are extracted with the profiles, but only the password limits are uploaded, assessed, and migrated by the Migration Portal. Also, in the Oracle database, the `DEFAULT` profile may have been overridden with new limit values. The `DEFAULT` profile is not migrated by the Migration Portal. If it is desired that the `DEFAULT` profile in EDB Postgres Advanced Server be configured with any limit overrides that have been applied to the Oracle `DEFAULT` profile, then they have to be applied manually in the target EDB Postgres Advanced Server database by using the `ALTER PROFILE` statement. +The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server only supports the Oracle password related limits. Resource limits are extracted with the profiles, but only the password limits are uploaded, assessed, and migrated by the Migration Portal. Also, in the Oracle database, the `DEFAULT` profile may have been overridden with new limit values. The EDB DDL Extractor extracts `ALTER PROFILE` statements for `DEFAULT` profiles that have been overridden in the Oracle database, and Migration Portal attempts to apply these statements in the target EDB Postgres Advanced Server database. If the schema is being migrated to an EDB Postgres Advanced Server instance with existing users and databases, we recommend that the settings of the `ALTER PROFILE DEFAULT` statement be verified and updated, if necessary, before migrating the DDL to the target database. !!! Note Starting with version 4.3.0, the Migration Portal supports assessment of users, roles, profiles, and grants. However for the projects created using an earlier version (earlier than 4.3.0) of the Migration Portal, this capability is not supported. In order to assess the users, roles, profiles, and grants, use the latest version of the EDB DDL Extractor and create a new project. From 578b69005fce9cdd4b6a520fa074cb322a3a8f19 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 10 Oct 2023 11:37:41 +0530 Subject: [PATCH 3/8] Update product_docs/docs/migration_portal/4/known_issues_notes.mdx --- product_docs/docs/migration_portal/4/known_issues_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_portal/4/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/known_issues_notes.mdx index e0c157eb212..9e30dc94648 100644 --- a/product_docs/docs/migration_portal/4/known_issues_notes.mdx +++ b/product_docs/docs/migration_portal/4/known_issues_notes.mdx @@ -53,7 +53,7 @@ When migrating users, the Migration Portal does not migrate the users' passwords #### Profiles -The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server only supports the Oracle password related limits. Resource limits are extracted with the profiles, but only the password limits are uploaded, assessed, and migrated by the Migration Portal. Also, in the Oracle database, the `DEFAULT` profile may have been overridden with new limit values. The EDB DDL Extractor extracts `ALTER PROFILE` statements for `DEFAULT` profiles that have been overridden in the Oracle database, and Migration Portal attempts to apply these statements in the target EDB Postgres Advanced Server database. If the schema is being migrated to an EDB Postgres Advanced Server instance with existing users and databases, we recommend that the settings of the `ALTER PROFILE DEFAULT` statement be verified and updated, if necessary, before migrating the DDL to the target database. +The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server only supports the Oracle password related limits. Resource limits are extracted with the profiles, but the Migration Portal only uploads, assesses, and migrates the password limits. Also, the `DEFAULT` profile may have been overridden in the Oracle database with new limit values. The EDB DDL Extractor extracts `ALTER PROFILE` statements for `DEFAULT` profiles that are overridden in the Oracle database, and the Migration Portal attempts to apply these statements in the target EDB Postgres Advanced Server database. If the schema is being migrated to an EDB Postgres Advanced Server instance with existing users and databases, we recommend that the settings of the `ALTER PROFILE DEFAULT` statement be verified and updated, if necessary, before migrating the DDL to the target database. !!! Note Starting with version 4.3.0, the Migration Portal supports assessment of users, roles, profiles, and grants. However for the projects created using an earlier version (earlier than 4.3.0) of the Migration Portal, this capability is not supported. In order to assess the users, roles, profiles, and grants, use the latest version of the EDB DDL Extractor and create a new project. From 0b7f0edc915c5dab9f8f30b349753b99ff49f14a Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 12 Oct 2023 12:46:44 +0100 Subject: [PATCH 4/8] Format fixes (also for app usage) Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/appusage/index.mdx | 1 + product_docs/docs/pgd/5/cli/index.mdx | 11 ++++++----- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pgd/5/appusage/index.mdx b/product_docs/docs/pgd/5/appusage/index.mdx index ca9f8971ac6..031148504a2 100644 --- a/product_docs/docs/pgd/5/appusage/index.mdx +++ b/product_docs/docs/pgd/5/appusage/index.mdx @@ -21,6 +21,7 @@ Developing an application with PGD is mostly the same as working with any Postgr - Large objects - Toast + * [DML and DDL replication](dml-and-ddl) shows the differences between the two classes of SQL statements and how PGD handles replicating them. It also looks at the commands PGD doesn't replicate at all. * [Nodes with differences](differences) examines how PGD works with configurations where there are differing table structures and schemas on replicated nodes. Also covered is how to compare between such nodes with LiveCompare and how differences in PostgreSQL versions running on nodes can be handled. diff --git a/product_docs/docs/pgd/5/cli/index.mdx b/product_docs/docs/pgd/5/cli/index.mdx index 66a60be0b08..92a67f0e5b6 100644 --- a/product_docs/docs/pgd/5/cli/index.mdx +++ b/product_docs/docs/pgd/5/cli/index.mdx @@ -15,13 +15,14 @@ directoryDefaults: The EDB Postgres Distributed Command Line Interface (PGD CLI) is a tool for managing your EDB Postgres Distributed cluster. It allows you to run commands against EDB Postgres Distributed clusters. It's installed automatically on systems in a TPA-deployed PGD cluster. Or it can be installed manually on systems that can connect to any PGD cluster, such as EDB BigAnimal distributed high-availability clusters or PGD clusters deployed using the EDB PGD for Kubernetes operator. -See [Installing PGD CLI](installing_cli) for information about how to manually install PGD CLI on systems. +* [Installing PGD CLI](installing_cli) has instructions on manually installing PGD CLI on various systems. -See [Using PGD CLI](using_cli) for an introduction to using the PGD CLI and connecting to your PGD cluster. +* [Using PGD CLI](using_cli) offers an introduction to using the PGD CLI and how to connect to your PGD cluster. -See [Configuring PGD CLI](configuring_cli) for details on creating persistent configurations for quicker connections. +* [Configuring PGD CLI](configuring_cli) has details on creating persistent configurations for quicker connections. -See the [Command reference](command_ref) for the available commands to inspect, manage, and get information about cluster resources. +* [PGD CLI's Command reference](command_ref) covers all the available commands to inspect, manage, and get information about cluster resources. + +* [Discovering connection strings](discover_connections) shows how to obtain the correct connection strings for your PGD-powered deployment. -See [Discovering connection strings](discover_connections) to learn how to obtain the correct connection strings for your PGD-powered deployment. From e5d33ca2fe2f9791037d170e5019df78479115e9 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Tue, 17 Oct 2023 16:26:59 -0400 Subject: [PATCH 5/8] Updated release version number and content Changed all occurrences of 4.5.2 to 4.6.0 (the correct version number) with the text. Note that the file name also needs to be updated from mp_4.5.2_rel_notes.mdx to mp_4.6.0_rel_notes.mdx. Added content to the release highlights table. Added End-of-support notice for EPAS 11. --- .../mp_4.5.2_rel_notes.mdx | 31 ++++++++++++++++--- 1 file changed, 26 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx index ea68249e269..23f6399f723 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx @@ -1,11 +1,32 @@ --- -title: "Migration Portal 4.5.2 release notes" -navTitle: Version 4.5.2 +title: "Migration Portal 4.6.0 release notes" +navTitle: Version 4.6.0 --- Released: -New features, enhancements, bug fixes, and other changes in Migration Portal 4.5.2 include the following: +New features, enhancements, bug fixes, and other changes in Migration Portal 4.6.0 include the following: -| Type | Description | -| ---- |------------ | +| Type | Description | +| ----------- |------------ | +| Enhancement | Improved performance of the schema parsing phase for large schema files that contain a large number of Oracle objects. | +| Enhancement | Migration Portal now supports the assessment and migration of the `DEFAULT` profile. | +| Enhancement | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. | +| Enhancement | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements. | +| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable name references in the `REFERENCING` clause updated by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | +| Bug Fix | Fixed the ERH-2065 repair handler to remove the `NO INMEMORY` clause from the `SUBPARTITION TEMPLATE` clause. | +| Bug Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios. | +| Bug Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios. | +| Bug Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects was not handled in the parsing phase. | +| Bug Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements were not getting removed from the uploaded source DDL scripts. | +| Bug Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it is supported in EDB Postgres Advanced Server. | +| Bug Fix | Fixed the issue where an assessment fails because of an `OutOfMemoryError` exception in some scenarios. | +| Bug Fix | Fixed parsing issues related to the usage of the `REMARK`, `HOST` and `PROMPT` keywords in schema files. | +| Bug Fix | Fixed the issue where column names inside check constraints were not getting double-quoted when the **Use Oracle's default case for schema migration** option was selected for the project. | +| Bug Fix | Fixed the EDB DDL Extractor script so that it performs the permission check prior to performing the Oracle version check and actual schema extraction. | +| Bug Fix | Updated the DDL parser to comment out `GRANT RESOURCE` statements generated for roles without a schema. | + +## End-of-support notice ## +Since the end of standard support for EDB Postgres Advanced Server version 11 is scheduled for November 20, 2023, select more recent versions of EDB Postgres Advanced Server that are supported beyond 2023 for new Migration Portal projects. Support for EDB Postgres Advanced Server 11 was removed from Migration Portal on May 20, 2023 to help ensure that no new EDB Postgres Advanced Server 11 projects are created after this date. + +To maximize the length of available support and to take advantage of new features, particularly those that provide added compatibility with Oracle, we recommend selecting the latest EDB Postgres Advanced Server version as the target of a Migration Portal project. See the EDB Platform Compatibility page for more information on the support periods for each EDB Postgres Advanced Server major version. From 662296ba6ee27690e9cbce7d7ba0d0bec75bb300 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 18 Oct 2023 12:49:33 +0530 Subject: [PATCH 6/8] Renamed the file, added the release notes to the table and did minor edits --- .../4/01_mp_release_notes/index.mdx | 20 ++++++----- .../mp_4.5.2_rel_notes.mdx | 32 ----------------- .../mp_4.6.0_rel_notes.mdx | 34 +++++++++++++++++++ 3 files changed, 45 insertions(+), 41 deletions(-) delete mode 100644 product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx create mode 100644 product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx index d7bd4172687..2305cc64bb7 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx @@ -4,6 +4,7 @@ redirects: - ../01_whats_new/ - 09_mp_3.5.1_rel_notes navigation: +- mp_4.6.0_rel_notes - mp_4.5.1_rel_notes - mp_4.5_rel_notes - mp_4.4_rel_notes @@ -15,12 +16,13 @@ navigation: The Migration Portal documentation describes the latest version of Migration Portal 4.0. -| Version | Release date | -| ------- | ------------ | -| [4.5.1](mp_4.5.1_rel_notes) | 12 Jul 2023 | -| [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 | -| [4.1](mp_4.1_rel_notes) | 04 Aug 2022 | -| [4.0](10_mp_4.0_rel_notes) | 22 Apr 2022 | +| Version | Release date | +| --------------------------- | ------------ | +| [4.6.0](mp_4.6.0_rel_notes) | 19 Oct 2023 | +| [4.5.1](mp_4.5.1_rel_notes) | 12 Jul 2023 | +| [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 | +| [4.1](mp_4.1_rel_notes) | 04 Aug 2022 | +| [4.0](10_mp_4.0_rel_notes) | 22 Apr 2022 | diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx deleted file mode 100644 index 23f6399f723..00000000000 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.5.2_rel_notes.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: "Migration Portal 4.6.0 release notes" -navTitle: Version 4.6.0 ---- - -Released: - -New features, enhancements, bug fixes, and other changes in Migration Portal 4.6.0 include the following: - -| Type | Description | -| ----------- |------------ | -| Enhancement | Improved performance of the schema parsing phase for large schema files that contain a large number of Oracle objects. | -| Enhancement | Migration Portal now supports the assessment and migration of the `DEFAULT` profile. | -| Enhancement | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. | -| Enhancement | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements. | -| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable name references in the `REFERENCING` clause updated by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | -| Bug Fix | Fixed the ERH-2065 repair handler to remove the `NO INMEMORY` clause from the `SUBPARTITION TEMPLATE` clause. | -| Bug Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios. | -| Bug Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios. | -| Bug Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects was not handled in the parsing phase. | -| Bug Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements were not getting removed from the uploaded source DDL scripts. | -| Bug Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it is supported in EDB Postgres Advanced Server. | -| Bug Fix | Fixed the issue where an assessment fails because of an `OutOfMemoryError` exception in some scenarios. | -| Bug Fix | Fixed parsing issues related to the usage of the `REMARK`, `HOST` and `PROMPT` keywords in schema files. | -| Bug Fix | Fixed the issue where column names inside check constraints were not getting double-quoted when the **Use Oracle's default case for schema migration** option was selected for the project. | -| Bug Fix | Fixed the EDB DDL Extractor script so that it performs the permission check prior to performing the Oracle version check and actual schema extraction. | -| Bug Fix | Updated the DDL parser to comment out `GRANT RESOURCE` statements generated for roles without a schema. | - -## End-of-support notice ## -Since the end of standard support for EDB Postgres Advanced Server version 11 is scheduled for November 20, 2023, select more recent versions of EDB Postgres Advanced Server that are supported beyond 2023 for new Migration Portal projects. Support for EDB Postgres Advanced Server 11 was removed from Migration Portal on May 20, 2023 to help ensure that no new EDB Postgres Advanced Server 11 projects are created after this date. - -To maximize the length of available support and to take advantage of new features, particularly those that provide added compatibility with Oracle, we recommend selecting the latest EDB Postgres Advanced Server version as the target of a Migration Portal project. See the EDB Platform Compatibility page for more information on the support periods for each EDB Postgres Advanced Server major version. diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx new file mode 100644 index 00000000000..65b4bc55d89 --- /dev/null +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx @@ -0,0 +1,34 @@ +--- +title: "Migration Portal 4.6.0 release notes" +navTitle: Version 4.6.0 +--- + +Released: 19 Oct 2023 + +New features, enhancements, bug fixes, and other changes in Migration Portal 4.6.0 include the following: + +| Type | Description | +| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Enhancement | Improved performance of the schema parsing phase for large schema files that contain a large number of Oracle objects. | +| Enhancement | Migration Portal now supports the assessment and migration of the `DEFAULT` profile. | +| Enhancement | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. | +| Enhancement | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements. | +| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable name references in the `REFERENCING` clause updated by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | +| Bug Fix | Fixed the ERH-2065 repair handler to remove the `NO INMEMORY` clause from the `SUBPARTITION TEMPLATE` clause. | +| Bug Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios. | +| Bug Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios. | +| Bug Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects was not handled in the parsing phase. | +| Bug Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements were not getting removed from the uploaded source DDL scripts. | +| Bug Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it is supported in EDB Postgres Advanced Server. | +| Bug Fix | Fixed the issue where an assessment fails because of an `OutOfMemoryError` exception in some scenarios. | +| Bug Fix | Fixed parsing issues related to the usage of the `REMARK`, `HOST` and `PROMPT` keywords in schema files. | +| Bug Fix | Fixed the issue where column names inside check constraints were not getting double-quoted when the **Use Oracle's default case for schema migration** option was selected for the project. | +| Bug Fix | Fixed the EDB DDL Extractor script so that it performs the permission check prior to performing the Oracle version check and actual schema extraction. | +| Bug Fix | Updated the DDL parser to comment out `GRANT RESOURCE` statements generated for roles without a schema. | + +## End-of-support notice ## + +EDB Postgres Advanced Server version 11 standard support is ending by November 20, 2023. The support for EDB Postgres Advanced Sever version 11 is removed from Migration Portal on May 20, 2023 to ensure that no new EDB Postgres Advanced Server version 11 projects are created post this date. + +To maximize the length of available support and to take advantage of new features, particularly those that provide added compatibility with Oracle, we recommend selecting the latest EDB Postgres Advanced Server version as the target of a Migration Portal project. See the [EDB Platform Compatibility page](https://www.enterprisedb.com/resources/platform-compatibility) for more information on the support periods for each EDB Postgres Advanced Server major version. + From 7c4f8520cb4632cbae35fc34ded1325b6cc00104 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Wed, 18 Oct 2023 12:08:48 -0400 Subject: [PATCH 7/8] A few minor wording changes --- .../4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx index 65b4bc55d89..12d3edc2c6f 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx @@ -13,7 +13,7 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.6 | Enhancement | Migration Portal now supports the assessment and migration of the `DEFAULT` profile. | | Enhancement | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. | | Enhancement | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements. | -| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable name references in the `REFERENCING` clause updated by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | +| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable names updated in the `REFERENCING` clause by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | | Bug Fix | Fixed the ERH-2065 repair handler to remove the `NO INMEMORY` clause from the `SUBPARTITION TEMPLATE` clause. | | Bug Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios. | | Bug Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios. | @@ -28,7 +28,7 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.6 ## End-of-support notice ## -EDB Postgres Advanced Server version 11 standard support is ending by November 20, 2023. The support for EDB Postgres Advanced Sever version 11 is removed from Migration Portal on May 20, 2023 to ensure that no new EDB Postgres Advanced Server version 11 projects are created post this date. +EDB Postgres Advanced Server version 11 standard support is ending by November 20, 2023. Support for EDB Postgres Advanced Sever version 11 was removed from Migration Portal on May 20, 2023 to ensure that no new EDB Postgres Advanced Server version 11 projects were created after this date. To maximize the length of available support and to take advantage of new features, particularly those that provide added compatibility with Oracle, we recommend selecting the latest EDB Postgres Advanced Server version as the target of a Migration Portal project. See the [EDB Platform Compatibility page](https://www.enterprisedb.com/resources/platform-compatibility) for more information on the support periods for each EDB Postgres Advanced Server major version. From 31b9f3a5ed831e2ba94331eec0ff11307994b87e Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Wed, 18 Oct 2023 13:19:06 -0400 Subject: [PATCH 8/8] Added INMEMORY clause NO INMEMORY bug fix description --- .../4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx index 12d3edc2c6f..4f68e42b212 100644 --- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx +++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx @@ -13,8 +13,8 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.6 | Enhancement | Migration Portal now supports the assessment and migration of the `DEFAULT` profile. | | Enhancement | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. | | Enhancement | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements. | -| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable names updated in the `REFERENCING` clause by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | -| Bug Fix | Fixed the ERH-2065 repair handler to remove the `NO INMEMORY` clause from the `SUBPARTITION TEMPLATE` clause. | +| Bug Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable names updated in the `REFERENCING` clause by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition. | +| Bug Fix | Fixed the ERH-2065 repair handler to remove the `INMEMORY` and `NO INMEMORY` clauses from the `SUBPARTITION TEMPLATE` clause. | | Bug Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios. | | Bug Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios. | | Bug Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects was not handled in the parsing phase. |