Migrate your Oracle database to an HM-managed database Innovation Release

These are the tasks involved in an end-to-end migration from an Oracle database to a database cluster managed by Hybrid Manager (HM).

Prepare your source database

Preparing your source database for schema ingestion, migration assessment, and subsequent data migration involves creating a dedicated user for both the EDB Postgres AI agent and DMS agent and altering the database configuration to enable replication features.

  1. Prepare your source for schema ingestion.

  2. Prepare the source for data migration.

Ingest source schema and assess the database

Install and configure the EDB Postgres AI agent with your Oracle database. This process performs a migration assessment to help you scope the effort, complexity, and time required for the migration. Also, the EDB Postgres AI agent extracts schema DDL that you can use to perform schema migrations with the built-in Migration Portal.

  1. Create a machine user for registration with the EDB Postgres AI agent.

  2. Install the EDB Postgres AI agent.

  3. Configure the EDB Postgres AI agent to register your Oracle database.

  4. Run the EDB Postgres AI agent.

  5. Run the EDB Postgres AI agent as a service.

  6. Verify the EDB Postgres AI agent has registered your Oracle database and view the migration assessment results.

Create a destination database

Create a cluster in the HM instance to host the destination database.

  1. Create a destination database in HM.

Migrate your schema

Use the Migration Portal integration to handle incompatibilities and transfer your schemas.

  1. Handle constraints for schema migration.

  2. Migrate schemas using the Migration Portal integration.

Migrate your data

Execute the data transfer and complete the final cleanup steps.

  1. Create project credentials for the data migration.

  2. Configure the DMS agent in reader mode for a data migration.

  3. Verify your source database appears in the HM console.

  4. Create and perform the data migration.

  5. Monitor your data migration.

  6. Finalize the migration (for streaming migrations only).

  7. Apply excluded constraints.