Merge pull request #1298 from EnterpriseDB/gvv/feedback_db_details_page

Feedback on migration database details page

Author: gvasquezvargas

product_docs/docs/edb-postgres-ai/1.4/hybrid-manager/using_hybrid_manager/migration/migrations/migration_database_details_view.mdx

@@ -20,7 +20,7 @@ You can select from the following statuses:
 
 ## Schemas
 
-The **Schemas** tab offers an overview of the schemas found in your connected database. It displays summary metrics for the database, along with a list of schemas where you granted `SELECT` access on at least one table. Only schemas containing at least one table are displayed.
+The **Schemas** tab offers an overview of the schemas found in your connected database. It displays summary metrics for the database, along with a list of discovered schemas. System schemas are excluded.
 
 This information can help you scope your migration effort and effectively plan the migration of your schemas.
 
@@ -46,9 +46,9 @@ This information can help you scope your migration effort and effectively plan t
 
 Selecting a row expands it to show the following:
 
-**Schema Compatibility Summary:** Shows the compatibility status of schema objects as reported by the Migration Portal, including the count of failed, system-repaired, user-repaired, and passed objects, along with the total object count and passed percentage.
+**Schema Compatibility Summary:** Shows the status of schema objects as processed by the Migration Portal. This summary is only available after a Migration Portal project has been created for the schema. For Postgres sources, compatibility assessment is skipped — schemas are passed through as-is, so failed, system-repaired, and user-repaired counts are always 0.
 
-**Migration Portal project table:** Lists the Migration Portal project associated with the schema, including the project name, target EDB Postgres Advanced Server (EPAS) version, creation date, and available actions.
+**Migration Portal project table:** Lists the Migration Portal project associated with the schema, including the project name, target database version, creation date, and available actions.
 
 </Tab>
 <Tab title="Oracle">
@@ -67,7 +67,7 @@ Selecting a row expands it to show the following:
 - **Latest Assessment:** Status of the latest assessment. Possible values are Not Started, In Progress, Complete, and Error.
 - **Last Assessed:** Timestamp of the last assessment. The assessment is regenerated or updated if the EDB Postgres AI agent discovers a new schema or an update to an existing one.
 - **# of Tables:** Number of tables in the schema.
-- **# of Objects:** Number of objects in the schema.
+- **# of Objects:** Number of assessed PL/SQL objects. In other words, packages, procedures, functions, and triggers that contain references to Oracle built-in packages or subprograms.
 - **Complexity:** Indicates how challenging it will be to convert the schema to EDB Postgres Advanced Server, based on a detailed, object-level analysis. Possible values are Very Easy, Easy, Medium, Hard, and Very Hard. A single schema's complexity may be higher than the overall database complexity, as schema-level analysis is more granular.
 - **Migration LoE:** Indicates how many days it will take to migrate the schema, in 8-hour working days, based on a detailed, object-level analysis.
 - **Dependencies:** The names of any schemas the current schema depends on. Migrate schemas with their dependencies in the same batch (using the same Migration Portal project) to ensure that all referenced objects exist in the destination database.
@@ -86,7 +86,7 @@ Selecting a row expands it to show the following:
 
 The **Assessment** tab provides a migration assessment of your connected database, offering insights to help you scope the effort and plan the migration of your database objects. This section contains a summary of the assessment, including key metrics and detailed breakdowns of the factors that contribute to the generated analysis.
 
-To export the assessment results in `.json` formatting, select **Download Report**.
+To export the assessment results in `.json` formatting, select **Download Report**. For Postgres databases, the report also includes [additional fields not shown in the HM console](#downloaded-report-fields).
 
 **Assessment Details:** Shows a high-level migration assessment summary of the database and the key information used in the assessment. For Postgres databases, this includes database name, engine, version, size, object count, table count, and schema count. For Oracle databases, it also includes migration complexity, Oracle database features used, Oracle PL/SQL features used, database migration LoE, number of CPUs, number of schemas assessed, assessment type, and last assessment timestamp.
 
@@ -112,7 +112,7 @@ To export the assessment results in `.json` formatting, select **Download Report
 
 **Compatibility Summary:** Shows a high-level compatibility summary of database features and schema objects, along with other factors that contribute to the overall migration complexity and level of effort assessment. Metrics include total schemas, total assessed PL/SQL objects, compatible objects, incompatible objects and occurrences with known workarounds, incompatible objects and occurrences that need further analysis, Oracle database features used, database size, PL/SQL lines, large objects usage, partition types used, aggregate queries, and SQL count.
 
-**Oracle PL/SQL Features Used:** Lists all PL/SQL objects that contain Oracle built-in features. For each feature, the table shows the object count, occurrence count, whether it's EPAS compatible (Yes/No), and migration complexity.
+**Oracle PL/SQL Features Used:** Lists all PL/SQL objects that contain Oracle built-in database package calls. For each feature, the table shows the object count, occurrence count, whether it's EPAS compatible (Yes/No), and migration complexity.
 
 **Oracle Database Features Used:** Lists all Oracle database features in use in the database, including their migration complexity and migration level of effort (LoE) in days.
 
@@ -121,6 +121,17 @@ To export the assessment results in `.json` formatting, select **Download Report
 </Tab>
 </TabContainer>
 
+### Downloaded report fields
+
+For Postgres databases, the downloaded `.json` report includes the following additional fields that aren't shown in the HM console:
+
+- `dbzUnsupportedTypes`: Column data types that Debezium doesn't support. Tables with these types can't use the Data Migration Service (DMS) streaming path.
+- `dbzKeyRisks`: A list of tables with factors for assessing data migration feasibility, including total table size in bytes, key availability (whether the table has a primary key), replica identity configuration, migration status, and TOAST status.
+- `largeObjectsCount`: Count of large object (LO) module objects in the database. Large objects aren't yet supported for migration via the DMS.
+- `distinctDataTypesCount`: Count of distinct data types in use across the database.
+- `objectTypeCounts`: Count of each object type in the database, broken down by schema.
+- `columnDataTypeCounts`: Count of distinct column data types per schema.
+
 ## Migration
 
 The **Migration** tab helps you perform migration-related tasks for the selected database.