From a95e940dba8fa2722fee5edf42c0fb12514cc858 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 7 Jul 2022 17:20:42 -0400 Subject: [PATCH 1/6] BigAnimal: fixed --high-availability examples --- .../getting_started/02_connecting_to_your_cloud/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx index 8be9733ec89..3a2c639571b 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx @@ -60,7 +60,7 @@ Perform the following steps: setup-csp --provider {--account-id | --subscription-id} --region - [--instance-type --high-availability --networking | --skip-preflight] + [--instance-type --cluster-architecture --networking | --skip-preflight] [--run] ``` !!! Important @@ -68,12 +68,12 @@ Perform the following steps: Here is an example of setting up an AWS account: ```shell - biganimal setup-csp --provider aws --account-id 123456789102 --region us-east-1 --instance-type aws:r5.large --high-availability --networking private --run + biganimal setup-csp --provider aws --account-id 123456789102 --region us-east-1 --instance-type aws:r5.large --cluster-architecture ha --networking private --run ``` Here is an example if setting up an Azure account: ```shell - biganimal setup-csp --provider azure --subscription-id abc12345-1234-1234-abcd-12345678901 --region eastus --instance-type azure:Standard_E4s_v3 --high-availability --networking private --run + biganimal setup-csp --provider azure --subscription-id abc12345-1234-1234-abcd-12345678901 --region eastus --instance-type azure:Standard_E4s_v3 --cluster-architecture ha --networking private --run ``` For more information on the command arguments, run the following command: From c38bb7039a958b0e968bd38e282410b5cbccc985 Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Fri, 5 Aug 2022 15:05:46 +0530 Subject: [PATCH 2/6] Adding details in impdp/expdp doc page --- .../01_mp_schema_extraction/01_data_pump_utility.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index 2757dcae899..9be584cfea6 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -31,7 +31,7 @@ Perform either of the following procedures: - [Extract all schemas in a database](#extract-all-schemas-in-a-database) -### Extract one or more schemas in a database +## Extract one or more schemas in a database 1. Before running the `expdp` command, create a file with a `.par` extension (for example, `export.par`) on your server. Add attributes and values to the file: @@ -63,7 +63,7 @@ Perform either of the following procedures: See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. -### Extract all schemas in a database +## Extract all schemas in a database !!! Note Don't perform this procedure from a user account that belongs to the excluded schemas list (see [Unsupported schemas](../01_mp_schema_extraction/#unsupported-schemas)). The `impdp` command fails if the user account running the command is in the excluded list of schemas. @@ -113,4 +113,8 @@ See an important [note](../01_mp_schema_extraction/#about-file-encoding) about t ```shell impdp @ DIRECTORY=DMPDIR TRANSFORM=OID:n,SEGMENT_ATTRIBUTES:n SQLFILE=YourSchemas.sql DUMPFILE=schemas_metadata.dump parfile=import.par ``` -See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. +See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. + +## Known Issues and Additional Notes + +- Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator, for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password, for example, `IDENTIFIED BY my_password`. From b7ef316085e8763627a781a41f281204538648b3 Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Fri, 5 Aug 2022 15:52:47 +0530 Subject: [PATCH 3/6] Update 01_data_pump_utility.mdx https://enterprisedb.atlassian.net/browse/MIG-3874 - Adding note and unsupported objects MIG-3897 - Incorporated Dee Dee's feedback --- .../01_mp_schema_extraction/01_data_pump_utility.mdx | 4 ++-- .../01_mp_schema_extraction/index.mdx | 10 +++++++++- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index 9be584cfea6..b1642a45b22 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -115,6 +115,6 @@ See an important [note](../01_mp_schema_extraction/#about-file-encoding) about t ``` See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. -## Known Issues and Additional Notes +## Known issues and additional notes -- Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator, for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password, for example, `IDENTIFIED BY my_password`. +- Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator; for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password; for example, `IDENTIFIED BY my_password`. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index a75f02e933a..df128fc15b0 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -163,7 +163,15 @@ Exclude these Oracle systems schemas while generating the SQL dump file. - Directories - Users - RLS policy -- Queues +- Queues * +- Library +- Alter Function +- Alter Package +- Alter Type +- Indextype + + + \* Even though EDB Postgres Advanced Server provides support for Queue tables, Migration Portal does not currently support it. Queue tables in the source DDL are not uploaded as source and target DDL objects. ## Wrapped objects From c3bc36638d683bdda32c5425f36ac049e8093d8e Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Wed, 10 Aug 2022 15:41:21 +0530 Subject: [PATCH 4/6] Updated based on feedback from Matt MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Because Alter Function, Alter Package, and Alter Type are generated only by the Oracle's data pump utility, I added the following notes: In the page describing the DDL extractor: "Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any other ALTER statement in the DDL." In the page describing the utility: "The DDL generated by Oracle’s Data Pump utility might contain ALTER STATEMENTS such as ALTER FUNCTION, ALTER PACKAGE, and ALTER TYPE. Migration Portal does not process these statements." --- .../01_mp_schema_extraction/01_data_pump_utility.mdx | 2 ++ .../01_mp_schema_extraction/index.mdx | 9 +++------ 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index b1642a45b22..32c9e25fc1d 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -118,3 +118,5 @@ See an important [note](../01_mp_schema_extraction/#about-file-encoding) about t ## Known issues and additional notes - Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator; for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password; for example, `IDENTIFIED BY my_password`. + +- The DDL generated by Oracle’s Data Pump utility might contain ALTER STATEMENTS such as ALTER FUNCTION, ALTER PACKAGE, and ALTER TYPE. Migration Portal does not process these statements. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index df128fc15b0..3ea6924c8de 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -148,7 +148,8 @@ Exclude these Oracle systems schemas while generating the SQL dump file. - Packages !!! Note - COMMENTS on columns, tables, and materialized views are also supported. + - COMMENTS on columns, tables, and materialized views are also supported. + - Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any other ALTER statement in the DDL. ### Unsupported object types @@ -165,13 +166,9 @@ Exclude these Oracle systems schemas while generating the SQL dump file. - RLS policy - Queues * - Library -- Alter Function -- Alter Package -- Alter Type - Indextype - - \* Even though EDB Postgres Advanced Server provides support for Queue tables, Migration Portal does not currently support it. Queue tables in the source DDL are not uploaded as source and target DDL objects. + \* Even though EDB Postgres Advanced Server provides support for Queue tables, Migration Portal does not currently support it. Queue tables in the source DDL are not uploaded as source and target DDL objects. ## Wrapped objects From df50c58f3b89197df4720d08bb4ac9be5b1075d5 Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Wed, 10 Aug 2022 16:58:01 +0530 Subject: [PATCH 5/6] Changed structure and added a separate page as suggested by Dee Dee --- .../01_data_pump_utility.mdx | 10 +---- .../01_mp_schema_extraction/index.mdx | 40 +++++------------ .../known_issues_notes.mdx | 44 +++++++++++++++++++ .../02_mp_schema_assessment.mdx | 2 +- 4 files changed, 59 insertions(+), 37 deletions(-) create mode 100644 product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index 32c9e25fc1d..f071699c9f6 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -61,7 +61,7 @@ Perform either of the following procedures: ``` -See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. +See [file encoding](known_issues_notes/#file-encoding) for information about the file encoding format expected by the Migration Portal. ## Extract all schemas in a database @@ -113,10 +113,4 @@ See an important [note](../01_mp_schema_extraction/#about-file-encoding) about t ```shell impdp @ DIRECTORY=DMPDIR TRANSFORM=OID:n,SEGMENT_ATTRIBUTES:n SQLFILE=YourSchemas.sql DUMPFILE=schemas_metadata.dump parfile=import.par ``` -See an important [note](../01_mp_schema_extraction/#about-file-encoding) about the file encoding format expected by the Migration Portal. - -## Known issues and additional notes - -- Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator; for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password; for example, `IDENTIFIED BY my_password`. - -- The DDL generated by Oracle’s Data Pump utility might contain ALTER STATEMENTS such as ALTER FUNCTION, ALTER PACKAGE, and ALTER TYPE. Migration Portal does not process these statements. +See [file encoding](known_issues_notes/#file-encoding) for information about the file encoding format expected by the Migration Portal. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index 3ea6924c8de..0e76b0cdfd4 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -8,14 +8,20 @@ legacyRedirectsGenerated: redirects: - ../01_whats_new/ +navigation: + - "01_data_pump_utility" + - "known_issues_notes" + --- You can perform a schema extraction using either of the following methods. EDB recommends using the EDB DDL extractor to extract your schemas. - - [EDB DDL extractor](#extracting-schemas-using-the-edb-ddl-extractor) (recommended method) + - [EDB DDL Extractor](#extracting-schemas-using-the-edb-ddl-extractor) (recommended method) - [Oracle’s Data Pump utility](01_data_pump_utility/) +For more information, see [Known issues and additional notes](known_issues_notes/). + ## Extracting schemas using the EDB DDL Extractor Download the latest EDB DDL Extractor script from the Migration Portal Projects page. @@ -25,7 +31,7 @@ Download the latest EDB DDL Extractor script from the Migration Portal Projects ### Prerequisites -You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses Oracle’s `DBMS_METADATA` built-in package to extract DDLs for different objects under schemas (specified while running the script). The EDB DDL extractor creates the DDL file uploaded to the portal and analyzed for EDB Postgres Advanced Server compatibility. +You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses Oracle’s `DBMS_METADATA` built-in package to extract DDLs for different objects under schemas (specified while running the script). The EDB DDL Extractor creates the DDL file uploaded to the portal and analyzed for EDB Postgres Advanced Server compatibility. !!! Note You must have `CONNECT` and `SELECT_CATALOG_ROLE` roles and `CREATE TABLE` privilege. @@ -93,20 +99,12 @@ Output of the DDL Extractor run appears in the Script Output tab. The name of th The script then iterates through the object types in the source database. Once the task is completed, the `.SQL` output is stored at the location you entered (e.g., `c:\Users\Example\Desktop\`). -See an important [note](#about-file-encoding) about the file encoding format expected by Migration Portal. +See [file encoding](known_issues_notes/#file-encoding) for information about the file encoding format expected by Migration Portal. -### Additional notes - -- The EDB DDL Extractor script doesn't extract objects restored using `Flashback` that still have names like `BIN$b54+4XlEYwPgUAB/AQBWwA==$0`. If you want to extract these objects, you must change the names of the objects and rerun the extraction process. -- The EDB DDL Extractor extracts `nologging` tables as normal tables. Once these tables are migrated to EDB Postgres Advanced Server, WAL log files are created. -- The EDB DDL Extractor extracts objects only with VALID status. For any objects that have INVALID status that you want Migration Portal to assess, first update them to VALID. -- The EDB DDL Extractor doesn't extract objects that were obfuscated using the Oracle wrap feature. As such, these objects aren't included in the set of DDL assessed by the Migration Portal. If you want to assess these objects and migrate them to EDB Postgres Advanced Server, replace the wrapped versions of the objects with nonwrapped versions. See [Wrapped objects](#wrapped-objects) for more information. -- 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. ## Schemas and objects support -The lists and tables that follow show supported and unsupported schemas and objects. +The lists and tables that follow show supported and unsupported schemas and objects in Migration Portal. ### Unsupported schemas @@ -148,8 +146,7 @@ Exclude these Oracle systems schemas while generating the SQL dump file. - Packages !!! Note - - COMMENTS on columns, tables, and materialized views are also supported. - - Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any other ALTER statement in the DDL. + COMMENTS on columns, tables, and materialized views are also supported. ### Unsupported object types @@ -168,17 +165,4 @@ Exclude these Oracle systems schemas while generating the SQL dump file. - Library - Indextype - \* Even though EDB Postgres Advanced Server provides support for Queue tables, Migration Portal does not currently support it. Queue tables in the source DDL are not uploaded as source and target DDL objects. - -## Wrapped objects - -Migration Portal can't assess wrapped objects. If you include them in the extracted DDL, they aren't loaded into Migration Portal and aren't included in the count of objects that are assessed. If you want to assess wrapped objects and migrate them to EDB Postgres Advanced Server, include unwrapped versions of the objects in the DDL file that you upload to Migration Portal. The recommended way of doing this is to replace the wrapped versions in the Oracle database with clear-text versions before performing the schema extraction. After performing the schema extraction, you can replace the objects with the wrapped versions. - -## About file encoding - -Migration Portal recommends the `.SQL` output file be in the UTF-8 encoding format. If you upload a `.SQL` file with non-UTF-8 encoding, all the characters that aren't compatible with UTF-8 are converted to the replacement character ‘�’ in the output DDL. - -!!! Tip - You can manually convert the extracted file to the UTF-8 format by using the iconv utility on Linux or the LibIconv utility on Windows. For example, if your database character set is in Latin-1 (ISO-8859-1), you can convert the extracted file to the UTF-8 format, as follows: - - `iconv -f iso-8859-1 -t UTF-8 sample.sql > sample_utf8.sql` +\* Even though EDB Postgres Advanced Server provides support for Queue tables, Migration Portal does not currently support it. Queue tables in the source DDL are not uploaded as source and target DDL objects. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx new file mode 100644 index 00000000000..d5e4afec484 --- /dev/null +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx @@ -0,0 +1,44 @@ +--- +title: "Known issues and additional notes" + +--- + +This page lists known issues and additional notes for: + + - [Migration Portal](#migration-portal) + - [EDB DDL Extractor](#edb-ddl-extractor) + - [Data pump utility](#data-pump-utility) + +## Migration Portal + +### Wrapped objects + +Migration Portal can't assess wrapped objects. If you include them in the extracted DDL, they aren't loaded into Migration Portal and aren't included in the count of objects that are assessed. If you want to assess wrapped objects and migrate them to EDB Postgres Advanced Server, include unwrapped versions of the objects in the DDL file that you upload to Migration Portal. The recommended way of doing this is to replace the wrapped versions in the Oracle database with clear-text versions before performing the schema extraction. After performing the schema extraction, you can replace the objects with the wrapped versions. + +### File encoding + +Migration Portal recommends the `.SQL` output file be in the UTF-8 encoding format. If you upload a `.SQL` file with non-UTF-8 encoding, all the characters that aren't compatible with UTF-8 are converted to the replacement character ‘�’ in the output DDL. + +!!! Tip + You can manually convert the extracted file to the UTF-8 format by using the iconv utility on Linux or the LibIconv utility on Windows. For example, if your database character set is in Latin-1 (ISO-8859-1), you can convert the extracted file to the UTF-8 format, as follows: + + `iconv -f iso-8859-1 -t UTF-8 sample.sql > sample_utf8.sql` + +### ALTER statements + +Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any other ALTER statements in the DDL. + +## EDB DDL Extractor + +- The EDB DDL Extractor script doesn't extract objects restored using `Flashback` that still have names like `BIN$b54+4XlEYwPgUAB/AQBWwA==$0`. If you want to extract these objects, you must change the names of the objects and rerun the extraction process. +- The EDB DDL Extractor extracts `nologging` tables as normal tables. Once these tables are migrated to EDB Postgres Advanced Server, WAL log files are created. +- The EDB DDL Extractor extracts objects only with VALID status. For any objects that have INVALID status that you want Migration Portal to assess, first update them to VALID. +- The EDB DDL Extractor doesn't extract objects that were obfuscated using the Oracle wrap feature. As such, these objects aren't included in the set of DDL assessed by the Migration Portal. If you want to assess these objects and migrate them to EDB Postgres Advanced Server, replace the wrapped versions of the objects with nonwrapped versions. See [Wrapped objects](#wrapped-objects) for more information. +- 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. + +## Data pump utility + +- Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator; for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password; for example, `IDENTIFIED BY my_password`. + +- The DDL generated by Oracle’s Data Pump utility might contain ALTER STATEMENTS such as ALTER FUNCTION, ALTER PACKAGE, and ALTER TYPE, which are not processed by Migration Portal. \ No newline at end of file diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx index 215461fe1f9..d863672c634 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx @@ -84,7 +84,7 @@ You can optionally select **Generate PDF** to save the report in PDF format. You !!! Note Migration Portal doesn't assess sensitive PL/SQL source code hidden in Oracle wrapped objects. These wrapped objects aren't included in the assessed objects count, and therefore the true value of compatibility percentage might be different from the value calculated in the assessment report. -See the note in [Performing a schema extraction](01_mp_schema_extraction#wrapped-objects) for more information about wrapped objects. +See the note in [Known issues and notes](01_mp_schema_extraction/known_issues_notes#wrapped-objects) for more information about wrapped objects. ## Evaluate an assessment report From e54ba410d1c31b6749985f0fd325b2f2abe0166e Mon Sep 17 00:00:00 2001 From: Moiz Nalwalla Date: Thu, 11 Aug 2022 16:53:05 +0530 Subject: [PATCH 6/6] Incorporated feedback from Matt --- .../01_mp_schema_extraction/01_data_pump_utility.mdx | 2 +- .../01_mp_schema_extraction/index.mdx | 4 ++-- .../01_mp_schema_extraction/known_issues_notes.mdx | 10 +++++----- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx index f071699c9f6..c9ae4e098f7 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx @@ -1,5 +1,5 @@ --- -title: "Extracting schemas using data pump utility" +title: "Extracting schemas using Oracle Data Pump utilities" --- diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index 0e76b0cdfd4..acf42d85720 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -18,9 +18,9 @@ navigation: You can perform a schema extraction using either of the following methods. EDB recommends using the EDB DDL extractor to extract your schemas. - [EDB DDL Extractor](#extracting-schemas-using-the-edb-ddl-extractor) (recommended method) - - [Oracle’s Data Pump utility](01_data_pump_utility/) + - [Oracle Data Pump utilities](01_data_pump_utility/) -For more information, see [Known issues and additional notes](known_issues_notes/). +For more information, see [Known issues, limitations, and notes](known_issues_notes/). ## Extracting schemas using the EDB DDL Extractor diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx index d5e4afec484..4538866f826 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes.mdx @@ -1,13 +1,13 @@ --- -title: "Known issues and additional notes" +title: "Known issues, limitations, and notes" --- -This page lists known issues and additional notes for: +This page lists known issues, limitations, and notes for: - [Migration Portal](#migration-portal) - [EDB DDL Extractor](#edb-ddl-extractor) - - [Data pump utility](#data-pump-utility) + - [Oracle Data Pump utilities](#oracle-data-pump-utilities) ## Migration Portal @@ -37,8 +37,8 @@ Except for ALTER TABLE and ALTER TRIGGER, Migration Portal does not process any - 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. -## Data pump utility +## Oracle Data Pump utilities - Migration Portal might fail to parse your SQL file if you create a database link using the IDENTIFIED BY clause with Oracle's quote operator; for example, `IDENTIFIED BY VALUES q'[:1]'`. To parse your file successfully, try using an actual password; for example, `IDENTIFIED BY my_password`. -- The DDL generated by Oracle’s Data Pump utility might contain ALTER STATEMENTS such as ALTER FUNCTION, ALTER PACKAGE, and ALTER TYPE, which are not processed by Migration Portal. \ No newline at end of file +- 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. \ No newline at end of file