To migrate an Oracle schema in Hybrid Manager (HM), start by resolving compatibility issues in your Migration Portal project. From there, choose how to import the converted schema to the destination database — automatically as part of the data migration (Simplified), or manually beforehand (Manual).
Prerequisites
- Register your Oracle database with HM via the EDB Postgres AI agent. HM creates a Migration Portal project automatically once the agent finishes loading the schema — see Managing Migration Portal projects for details, including how to create a project manually if automatic creation didn't happen.
Resolving compatibility issues
Use the AI Copilot or QuickHelp in Migration Portal to resolve any compatibility issues found during schema assessment. After fixing an object, select Reassess — repeat until your schema reaches 100% compatibility.
Migration Portal in HM also tries to fix failed objects automatically with AI DDL repair, if your HM administrator enabled the AI Copilot and you accepted its terms of use.
Performing a schema assessment covers this process in more detail, but it's written for the EDB-hosted Migration Portal, where you create a project and upload a DDL file manually. In HM, your project already exists and the schema is already loaded, so skip straight to reviewing and fixing the flagged objects.
See Evaluate an assessment report to understand the compatibility categories in your results.
Importing the schema
After resolving all compatibility issues, choose how to import the schema to the destination database:
Once your schema passes assessment, you're done in Migration Portal — there's nothing to export or import manually. Leave Migration Portal and continue to configuring the EDB Data Migration Service (DMS) agent. When you create the migration, select Schema and data as the scope: HM automatically retrieves the converted schema from Migration Portal, applies constraints in the correct order, and reapplies deferred constraints after data migration completes. See Configuring the EDB DMS agent.
Import the schema into the destination database directly from Migration Portal, then manage constraint ordering yourself.
Select Migrate to.
Select the Online migration option — recommended, since Migration Portal connects directly to the destination and imports the schema for you. Select Offline migration instead if you'd rather download a SQL script to review or edit — for example, to comment out specific objects — before applying it to the destination yourself.
Select the schemas you want to migrate, but clear Constraints from the list of objects underneath the database. Select Next.
Note
See Importing schema to learn more about why constraints must be disabled and other considerations.
In the Connect to your cluster page, enter the host name of the database cluster you want to use as a destination.
Note
If you're migrating to an HM-managed database cluster, you can find the read/write host and other connection data from the Clusters page. Select your cluster, and then select Connect.
Select Next and wait until the schemas were imported successfully.
Connect to the target database cluster and ensure the schemas were migrated.