Detailed view v1.3

When you select a database from the Estate page > Migrations tab, a detailed view opens. This detailed view includes functionality that you can leverage to perform migrations from external databases.

Status

Use the status dropdown selector next to the database's name to manage and track your migration workflow. This selector allows you to update the current state of a database migration, providing clarity for both you and your team members.

You can select from the following statuses:

• Assessing (default)
• Planning
• Decided Not To Migrate
• In Progress
• Done

Schemas

The Schemas tab offers an overview of the schemas found in your connected database. Here, you'll find summary metrics for the database, along with a list of schemas where you have granted SELECT access on at least one table. Only schemas containing at least one table are displayed.

This information can help you scope your migration effort and effectively plan the migration of your schemas. Additionally, for Oracle databases, the Schemas tab allows you to create new Migration Portal projects directly from the extracted schemas.

Summary cards

• Total schemas for the selected database.

• Total tables for the selected database.

• Total objects for the selected database.

• Complexity overview for all schemas, color-coded by complexity (very easy, easy, medium, hard, very hard). Available for Oracle databases only.

• Migration level of effort, color-coded by day ranges (0-5, 6-15, 16-25, 26-40, 40+ days), defined by 8-hours working days. Available for Oracle databases only.

Schema table

• Name: Name of the schema.

• Latest Assessment: Available for Oracle databases only. Status of the latest assessment. Possible values are Not started, In progress, Complete and Error.

• Last Assessed: Available for Oracle databases only. Timestamp corresponding to the last time the schema was assessed. The assessment will be automatically regenerated or updated if the HM Agent discovers that a new schema is available or if an existing one has been updated.

• # of Tables: Number of tables in the assessed schema.

• # of Objects: Number of objects in the assessed schema.

• Complexity: Available for Oracle databases only. Indicates how challenging it will be to convert a specific 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: Available for Oracle databases only. Indicates how many days it will take to migrate a specific schema, in 8-hour working days, based on a detailed, object-level analysis.

• Dependencies: Available for Oracle databases only. The name of the schema that the current schema depends on. We recommend migrating schemas with their dependencies in the same batch (using the same Migration Portal project) to ensure that all objects referenced by the schema exist in the destination database.

• MP Project: Available for Oracle databases only. Use the integrated Migration Portal to convert an Oracle schema to EDB Postgres Advanced Server. Select the plus sign to open a window where you can provide details to start a new schema migration project with the Migration Portal project-scoped workspace. After you provide the details, the Hybrid Manager creates a Migration Portal project in the background. You can access this project at a later time through the Migration tab.

Assessment

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.

Assessment Details: summarizes key analysis results and assessment metadata.

Compatibility Summary: Available for Oracle databases only. Summarizes database features and schema objects as well as other factors that contribute to the overall migration complexity and level of effort. The complexity is assigned depending on a scoring system that analyses several factors. Some of the factors include database size, large object usage, used partition types, Oracle database features, procedural database objects and whether they are EPAS compatible. Each of the analyzed object gets a 1-5 score (very easy to very hard). The max complexity value is displayed here.

Oracle PL/SQL features used: Available for Oracle databases only. Lists all PL/SQL objects that contain Oracle built-in features. To understand the migration impact of the Oracle PL/SQL feature, see the object count, the occurrence count, whether they are EPAS-compatible and the results of the migration complexity assessment.

If all calls of a specific feature have equivalent EDB Postgres Advanced Server implementations, the feature is marked as EPAS Compatible. If no equivalent is detected, the feature is marked as incompatible.

Oracle database features used: Available for Oracle databases only. Lists all Oracle database features in use within the database.

Incompatible PL/SQL features in objects: Available for Oracle databases only. Lists all Oracle and non-Oracle incompatible PL/SQL features while displaying the schema they are in, the object type (procedure, function, etc.), the object name, the incompatible feature name, how often the feature appear and the migration complexity.

Migration

Helps you perform migration-related tasks.

Create a Destination: allows you to create a new cluster that will serve as a destination for your migration. See Creating a database cluster for more guidance.

Migrate Schema(s):

• for Oracle databases, this option lets you create a project in the built-in Migration Portal (project-scoped workspace) that you can use to convert the Oracle schema to be compatible with EDB Postgres Advanced Server. After you resolve any incompatibilities, the Migration Portal service also let's you connect to the destination cluster to import the converted schema.

• for Postgres databases, this option provides information on how to use external tooling like Migration Toolkit or pg_dump among other tools to migrate Postgres schemas.

Migrate Data: leverages the Hybrid Manager's Data Migration Service to perform data migrations with CDC technology. Before you perform data migrations with this function, ensure you have prepared your database, migrated your schema, installed and configured the EDB DMS Agent. See Choose your migration for end-to-end examples of how to perform a complete database migration.