What’s New

The following features are added to the EDB Postgres Migration Portal for this release:

  • You can now choose to extract dependent objects while extracting the schemas. The dependent objects from the other schemas will also be extracted, which will help in improving the assessment results.
  • New users will have an improved experience when getting started with the Migration Portal.
  • As Advanced Server does not support the same name for tables and indexes, you may now choose to add an index prefix, ‘idx’, while creating a project for better assessment results.
  • The assessment report shows the count of distinct repair handlers applied to the DDLs under the selected schema.
distinct repair handler count

Applied repair handlers count

  • You can now filter system-repaired and manually-repaired objects on the Workspace page.
manually repaired objects

Manually repaired objects

Note:

Starting this release, Migration Portal will accept DDLs extracted by the latest EDB DDL Extractor only.

New Repair Handlers

The following repair handlers are added to improve the Advance Server compatibility ratio:

  • ERH 2073 - Removes CONSTRAINT constraint_name NOT NULL DISABLE clause from the source DDL for tables.

    For example, CREATE TABLE TEST (COL1 VARCHAR2(40) CONSTRAINT TEST_COL1_NN NOT NULL DISABLE); would become CREATE TABLE TEST (COL1 VARCHAR2(40));

  • ERH 2074 - Removes NOT NULL DISABLE clause from the source DDL for tables.

    For example, CREATE TABLE TEST(COL1 VARCHAR2(40) NOT NULL DISABLE ); would become CREATE TABLE TEST (COL1 VARCHAR2(40));

  • ERH 2075 - Removes CONSTRAINT constraint_name CHECK|UNIQUE|PRIMARY KEY parameters DISABLE clause from the source DDL for tables.

For example, CREATE TABLE TEST(DATE_COL1 DATE, CONSTRAINT TEST_DATE_COL1_CHK CHECK (DATE_COL1 > '01-JAN-2018') DISABLE); would become CREATE TABLE TEST (DATE_COL1 DATE);

  • ERH 2076 - Removes CHECK|UNIQUE|PRIMARY KEY parameters DISABLE clause from the source DDL for tables.

    For example, CREATE TABLE TEST (ID VARCHAR2(40), PRIMARY KEY (ID) DISABLE); would become CREATE TABLE TEST (ID VARCHAR2(40));

Knowledge Base

The following new knowledge base entry is added; refer to the Knowledge Base section on the Migration Portal for workaround details.

  • NVL function inside Index definition

In Advanced Server, the DATE datatype from Oracle is converted into a timestamp without time zone datatype for compatibility. However, in Advanced Server v10, the nvl() function does not support the timestamp without time zone datatype in arguments. The following data types are supported as input arguments for the nvl() function in Advanced Server v10:

character varying

Numeric

Date

timestamp with time zone

Any other datatype used as an input value for the nvl() function inside the index definition will return an error.