Skip to content

Commit

Permalink
Merge pull request #4934 from EnterpriseDB/release/2023-10-19
Browse files Browse the repository at this point in the history 
Release: 2023-10-19
  • Loading branch information
@nidhibhammar
nidhibhammar authored Oct 19, 2023
2 parents a7fe351 + 43a60d6 commit b6e08f2
Show file tree
Hide file tree
Showing 5 changed files with 60 additions and 22 deletions.
20 changes: 11 additions & 9 deletions product_docs/docs/migration_portal/4/01_mp_release_notes/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 |
34 changes: 34 additions & 0 deletions product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
@@ -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 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. |
| 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. 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.

4 changes: 2 additions & 2 deletions product_docs/docs/migration_portal/4/known_issues_notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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 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.
Expand Down
13 changes: 7 additions & 6 deletions product_docs/docs/pgd/5/appusage/index.mdx
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Application use
redirects:
redirects:
- ../bdr/appusage
navigation:
- behavior
Expand All @@ -15,13 +15,14 @@ Developing an application with PGD is mostly the same as working with any Postgr

* [Application behavior](behavior) looks at how PGD replication appears to an application, such as:
- The commands that are replicated
- The commands that run locally
- When row-level locks are acquired
- How and where triggers fire
- Large objects
- The commands that run locally
- When row-level locks are acquired
- How and where triggers fire
- Large objects
- Toast

* [DML and DDL replication](dml-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.

* [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](nodes-with-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.

Expand Down
11 changes: 6 additions & 5 deletions product_docs/docs/pgd/5/cli/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.

1 comment on commit b6e08f2

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Published on https://edb-docs.netlify.app as production
🚀 Deployed on https://6531404505546c22ca463016--edb-docs.netlify.app

Please sign in to comment.