Skip to content

Commit

Permalink
Merge pull request #5009 from EnterpriseDB/release/2023-11-14
Browse files Browse the repository at this point in the history 
Release: 2023-11-14
  • Loading branch information
@djw-m
djw-m authored Nov 14, 2023
2 parents c3804c8 + 5308309 commit 34b2542
Show file tree
Hide file tree
Showing 19 changed files with 515 additions and 327 deletions.
6 changes: 3 additions & 3 deletions product_docs/docs/lasso/4/linux.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ option as follows:
./lasso --barman-configuration /opt/barman/barman.conf
```

## Replication Manger (repmgr) report
## Replication Manager (repmgr) report

Lasso can run on systems where repmgr is installed. In that
case, it gathers repmgr-related information.
Expand Down Expand Up @@ -130,7 +130,7 @@ option as follows:
This approach is preferred, as it guarantees Lasso will use
the correct repmgr configuration file instead of trying to find it automatically.

## Postres Enterprise Manager (PEM) report
## Postgres Enterprise Manager (PEM) report

Lasso can run on systems where PEM is installed. In that
case, it also gathers PEM-related information, like some configuration
Expand Down Expand Up @@ -317,4 +317,4 @@ You can run a system-only report with the following command:

```
./lasso --system-only
```
```
25 changes: 12 additions & 13 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
Expand Up @@ -10,25 +10,24 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.6
| 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. |
| Enhancement | Migration Portal now supports assessing and migrating the `DEFAULT` profile. |
| Enhancement | A new repair handler (ERH-2104) was added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument. |
| Enhancement | A new repair handler (ERH-2105) was added that puts 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 weren't also 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 ERH-2002 repair handler issue where it wasn't being applied in some scenarios. |
| Bug Fix | Fixed the ERH-2009 repair handler issue where it wasn't 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 wasn't handled in the parsing phase. |
| Bug Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements weren't getting removed from the uploaded source DDL scripts. |
| Bug Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it's 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 | Fixed the issue where column names inside check constraints weren't 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 ##
## 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.

6 changes: 3 additions & 3 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 @@ -4,7 +4,7 @@ redirects:
- /migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes/
---

This page lists known issues, limitations, and notes for:
These are the known issues, limitations, and notes for:

- [Migration Portal](#migration-portal)
- [EDB DDL Extractor](#edb-ddl-extractor)
Expand Down Expand Up @@ -53,10 +53,10 @@ 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 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.
The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server supports only the Oracle password-related limits. Resource limits are extracted with the profiles, but the Migration Portal uploads, assesses, and migrates only the password limits. Also, the `DEFAULT` profile might be 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.
Starting with version 4.3.0, the Migration Portal supports assessment of users, roles, profiles, and grants. However, for the projects created using a version earlier than 4.3.0 of the Migration Portal, this capability isn't supported. To assess the users, roles, profiles, and grants, use the latest version of the EDB DDL Extractor and create a new project.


### Using Oracle default case
Expand Down
Loading

2 comments on commit 34b2542

@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://6553eaf7d4c7e01addf28948--edb-docs.netlify.app

@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-staging.netlify.app as production
🚀 Deployed on https://6553eee4bed9d61d08570c02--edb-docs-staging.netlify.app

Please sign in to comment.