Merge pull request #6281 from EnterpriseDB/release/2024-11-22a

Release/2024-11-22a
EnterpriseDB · Nov 22, 2024 · c094c7e · c094c7e · github-actions · Nov 22, 2024
2 parents 87566fa + c09dfda
commit c094c7e
Show file tree

Hide file tree

Showing 53 changed files with 2,759 additions and 304 deletions.
diff --git a/...tal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx b/...tal/4/04_mp_migrating_database/01_mp_schema_extraction/01_data_pump_utility.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Extracting schemas using Oracle Data Pump utilities"
-
+navTitle: Using Oracle Data Pump
 ---
 
 Migration Portal requires only the metadata in the SQL dump file to assess the extracted schemas.

diff --git a/...portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx b/...portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx
@@ -0,0 +1,111 @@
+---
+title: "Extracting schemas using the EDB DDL Extractor"
+navTitle: Using EDB DDL Extractor
+---
+
+
+Download the latest EDB DDL Extractor script from the Migration Portal Projects page.
+
+!!! Note
+    Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size.
+
+## 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.
+
+!!! Note
+    You must have `CONNECT` and `SELECT_CATALOG_ROLE` roles and `CREATE TABLE` privilege.
+
+### For SQL\*Plus
+
+1.  Connect to SQL\*Plus and run this command:
+
+    ```sql
+    @edb_ddl_extractor.sql
+    ```
+
+1.  When prompted, if the Oracle user that is running the script has the required privileges, press **Enter** to continue running the script. 
+
+1.  When prompted, provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter.
+
+ !!! Note
+     If you want to extract all the user schemas from the current database, don't mention any schema names while extracting. However, we recommend mentioning the schema names that you want to extract.
+
+1.  When prompted, enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command.
+
+1.  When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas.
+
+1.  When prompted, enter `yes`or `no` depending on whether you want to extract grant statements from other schemas.
+
+## Example
+
+1. Run the extractor script:
+
+   ```text
+   @edb_ddl_extractor.sql
+   ```
+
+1. Press **Enter**.
+
+1. Specify three schemas by separating them with commas:
+
+   ```text
+   Enter a comma separated list of schemas to be extracted (Default all schemas): HR, SCOTT, FINANCE
+   ```
+
+1. Enter a path for the output file:
+
+   On Linux, you might use:
+
+   ```text
+   Location for output file (Default current location) : /home/oracle/extracted_ddls/
+   ```
+
+   Similarly on Windows:
+
+   ```text
+   Location for output file (Default current location) : c:\Users\Example\Desktop\
+   ```
+
+1. Enter `yes` to extract dependent objects in other schemas:
+
+   ```text
+   WARNING:
+
+   Given schema(s) list may contain objects which are dependent on objects 
+   from other schema(s), not mentioned in the list.` `Assessment may fail 
+   for such objects. It is suggested to extract all dependent objects 
+   together.
+   Extract dependent object from other schemas?(yes/no) (Default no / Ignored for all schemas option): yes
+   ```
+
+1. Enter `yes` to extract grant statements:
+
+   ```text
+   Extract GRANT statements?(yes/no) (Default no): yes
+   ```
+
+### For SQL Developer
+
+After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecting to the source Oracle database, run the script. As the script executes, respond to the prompts.
+
+1.  If the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script.
+
+2.  Enter a comma-separated list of schemas, and select **OK**. 
+
+3.  Enter the path for the output file, and select **OK**. The default is the location of the DDL Extractor script.
+
+4.  Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is to not extract dependent objects. 
+
+5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default setting is not to extract grant statements.
+
+Output of the DDL Extractor run appears in the Script Output tab. The name of the output file appears after the `Extraction Completed` message in the script output.
+
+!!! Note
+    You can also enter single schema name in both SQL\*Plus and SQL Developer.
+
+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 [file encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format expected by Migration Portal.
+
+
diff --git a/...s/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/...s/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx
@@ -7,126 +7,27 @@ legacyRedirectsGenerated:
 
 redirects:
   - ../01_whats_new/
-
+deepToC: true
 navigation:
- - "01_data_pump_utility"
-
+ - edb_ddl_extractor
+ - 01_data_pump_utility
 ---
 
-<div id="mp_schema_extraction" class="registered_link"></div>
-
-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 Data Pump utilities](01_data_pump_utility/) 
-
-For more information, see [Known issues, limitations, and notes](/migration_portal/latest/known_issues_notes/). 
-
-## Extracting schemas using the EDB DDL Extractor
-
-Download the latest EDB DDL Extractor script from the Migration Portal Projects page.
-
-!!! Note
-    Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size.
-
-### 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.
-
-!!! Note
-    You must have `CONNECT` and `SELECT_CATALOG_ROLE` roles and `CREATE TABLE` privilege.
-
-#### For SQL\*Plus
-
-1.  Connect to SQL\*Plus and run this command:
-
-    ```sql
-    @edb_ddl_extractor.sql
-    ```
-
-2.  When prompted, if the Oracle user that is running the script has the required privileges, press **Enter** to continue running the script. 
-
-3.  When prompted, provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter.
-
- !!! Note
-     If you want to extract all the user schemas from the current database, don't mention any schema names while extracting. However, we recommend mentioning the schema names that you want to extract.
-
-4.  When prompted, enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command.
-
-5.  When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas.
-
-6.  When prompted, enter `yes`or `no` depending on whether you want to extract grant statements from other schemas.
-
-For example:
-
-1. Run the extractor script:
+## Schema extraction methods
 
-   ```text
-   @edb_ddl_extractor.sql
-   ```
+You can perform a schema extraction using the EDB or Oracle extraction tools.Select one of the following for instructions and examples:
 
-2. Press **Enter**
-
-3. Specify three schemas by separating them with commas:
-
-   ```text
-   Enter a comma separated list of schemas to be extracted (Default all schemas): HR, SCOTT, FINANCE
-   ```
-
-4. Enter a path for the output file:
-
-   On Linux, you might use:
-
-   ```text
-   Location for output file (Default current location) : /home/oracle/extracted_ddls/
-   ```
-
-   Similarly on Windows:
-
-   ```text
-   Location for output file (Default current location) : c:\Users\Example\Desktop\
-   ```
-
-5. Enter `yes` to extract dependent objects in other schemas:
-
-   ```text
-   WARNING:
-
-   Given schema(s) list may contain objects which are dependent on objects 
-   from other schema(s), not mentioned in the list.` `Assessment may fail 
-   for such objects. It is suggested to extract all dependent objects 
-   together.
-   Extract dependent object from other schemas?(yes/no) (Default no / Ignored for all schemas option): yes
-   ```
-
-6. Enter `yes` to extract grant statements:
-
-   ```text
-   Extract GRANT statements?(yes/no) (Default no): yes
-   ```
-
-#### For SQL Developer
-
-After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecting to the source Oracle database, run the script. As the script executes, respond to the prompts.
-
-1.  If the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script.
-
-2.  Enter a comma-separated list of schemas, and select **OK**. 
-
-3.  Enter the path for the output file, and select **OK**. The default is the location of the DDL Extractor script.
-
-4.  Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is to not extract dependent objects. 
-
-5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default setting is not to extract grant statements.
-
-Output of the DDL Extractor run appears in the Script Output tab. The name of the output file appears after the `Extraction Completed` message in the script output.
-
-!!! Note
-    You can also enter single schema name in both SQL\*Plus and SQL Developer.
+ -  [EDB DDL Extractor](edb_ddl_extractor) (recommended method)
+ -  [Oracle Data Pump utilities](01_data_pump_utility/) 
 
-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\`).
+EDB recommends using the EDB DDL extractor to extract your schemas.
+Alternatively, you can use Oracle’s Data Pump (IMPDP/EXPDP) tool to export schemas from an Oracle database. 
 
-See [file encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format expected by Migration Portal.
+!!!warning 
+   If you choose to extract schemas using a different method and then upload the DDL file to Migration Portal, the portal may not be able to assess the file correctly.
+!!!
 
+For more information, see [Known issues, limitations, and notes](/migration_portal/latest/known_issues_notes/). 
 
 ## Schemas and objects support
 

diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/index.mdx
@@ -11,7 +11,7 @@ legacyRedirectsGenerated:
 
 To migrate a database, you must complete the following steps:
 
-1.  Perform a [schema extraction](01_mp_schema_extraction/#mp_schema_extraction).
+1.  Perform a [schema extraction](01_mp_schema_extraction).
 2.  Perform a [schema assessment](02_mp_schema_assessment/#mp_schema_assessment).
 3.  Perform a [schema migration](03_mp_schema_migration/#mp_schema_migration).
 4.  Perform a [data migration](04_mp_data_migration/#mp_data_migration).

diff --git a/product_docs/docs/net_connector/8.0.5.1/01_release_notes.mdx b/product_docs/docs/net_connector/8.0.5.1/01_release_notes.mdx
@@ -0,0 +1,17 @@
+---
+title: "Release notes"
+---
+
+Released: 22 Nov 2024
+
+The EDB .NET Connector provides connectivity between a .NET client application and an EDB Postgres Advanced Server database server.
+
+New features, enhancements, bug fixes, and other changes in the EDB .NET Connector `8.0.5.1` include:
+
+| Type           | Description                                                                                                                                                                                                                                        | Addresses |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| Upstream merge | Merged with community .NET driver version 8.0.5 and EF Core Driver 8.0.10. See [release notes](https://www.npgsql.org/doc/release-notes/8.0.html) for more information about merge updates.                                                        |           |
+| Bug fix        | Fixed a performance issue. Performance is now improved when reading data while targeting .NET Framework 4.7.2, 4.8, and 4.8.1.                                                                                                                     | #41979    |
+| Enhancement    | Added support for EDB Postgres Advanced Server 17.2.                                                                                                                                                                                               |           |
+| Enhancement    | Added support for `IS TABLE OF`. EDB Postgres Advanced Server supports Oracle nested table collection types created with `CREATE TYPE ... AS TABLE OF` statements. See [Using nested tables](./using_nested_table_types.mdx) for more information. |           |
+| Deprecation    | Removed .NET5, .NET6, and .NET7 targets as they have reached end of support.                                                                                                                                                                       |           |
diff --git a/product_docs/docs/net_connector/8.0.5.1/02_requirements_overview.mdx b/product_docs/docs/net_connector/8.0.5.1/02_requirements_overview.mdx
@@ -0,0 +1,20 @@
+---
+title: "Product compatibility"
+---
+
+<div id="requirements_overview" class="registered_link"></div>
+
+These are the supported versions and platforms for the EDB .NET Connector.
+
+The EDB .NET Connector is certified with EDB Postgres Advanced Server version 11 and later.
+
+The EDB .NET Connector graphical installers are supported on the following Windows platforms:
+
+64-bit Windows:
+
+-   Windows Server 2019 and 2022
+-   Windows 10 and 11
+
+32-bit Windows:
+
+-   Windows 10
diff --git a/...cs/docs/net_connector/8.0.5.1/03_the_advanced_server_net_connector_overview.mdx b/...cs/docs/net_connector/8.0.5.1/03_the_advanced_server_net_connector_overview.mdx
@@ -0,0 +1,39 @@
+---
+title: "EDB .NET Connector overview"
+
+---
+
+<div id="the_advanced_server_net_connector_overview" class="registered_link"></div>
+
+EDB .NET Connector is a .NET data provider that allows a client application to connect to a database stored on an EDB Postgres Advanced Server host. The .NET Connector accesses the data directly, allowing the client application optimal performance, a broad spectrum of functionality, and access to EDB Postgres Advanced Server features.
+
+The .NET Connector supports the following frameworks:
+
+-   .NET 8.0
+-   .NET Framework 4.7.2, 4.8, and 4.8.1
+-   .NET Standard 2.0 and 2.1
+
+
+## The .NET class hierarchy
+
+The .NET class hierarchy contains classes that you can use to create objects that control a connection to the EDB Postgres Advanced Server database and manipulate the data stored on the server. The following are a few of the most commonly used object classes.
+
+`EDBDataSource`
+
+ `EDBDataSource` is the entry point for all the connections made to the database. It's responsible for issuing connections to the server and efficiently managing them. Starting with EDB .NET Connector 7.0.4.1, you no longer need direct instantiation of `EDBConnection`. Instantiate `EDBDataSource` and use the method provided to create commands or execute queries.
+
+`EDBConnection`
+
+ The `EDBConnection` class represents a connection to EDB Postgres Advanced Server. An `EDBConnection` object contains a `ConnectionString` that tells the .NET client how to connect to an EDB Postgres Advanced Server database. Obtain `EDBConnection` from an `EDBDataSource` instance, and use it directly only in specific scenarios, such as transactions.
+
+`EDBCommand`
+
+ An `EDBCommand` object contains a SQL command that the client executes against EDB Postgres Advanced Server. Before you can execute an `EDBCommand` object, you must link it to an `EDBConnection` object.
+
+`EDBDataReader`
+
+ An `EDBDataReader` object provides a way to read an EDB Postgres Advanced Server result set. You can use an `EDBDataReader` object to step through one row at a time, forward only.
+
+`EDBDataAdapter`
+
+ An `EDBDataAdapter` object links a result set to the EDB Postgres Advanced Server database. You can modify values and use the `EDBDataAdapter` class to update the data stored in an EDB Postgres Advanced Server database.