Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes limitations and answers common questions about migrating Oracle data to Azure Database for PostgreSQL flexible server by using Azure Database Migration Service (DMS).
For the architecture and migration process, see the data migration overview.
Migration limitations
| Area | Limitation | What to do |
|---|---|---|
| Migration mode | Offline migration only. Changes made to Oracle after the migration snapshot aren't synchronized to the target. | Stop applications and modifying jobs before copying. Plan downtime for copying, validation, and switching applications. |
| Migration scope | DMS copies table data, not schema objects. | Complete the schema and data migration, and test the converted application before switching it to the target database. |
| Object selection | Selection is at schema level. Individual-table selection isn't available. | Review all tables in each schema you want to migrate. |
| Destination mapping | A migration can include multiple Oracle schemas but writes to a single PostgreSQL database. | Create separate migrations for migrating to different destination databases. |
| Authentication | Source and target migration connections use username and password. | Use accounts with the required privileges. Migration using Microsoft Entra authentication, managed identities, or wallet-based authentication isn't currently supported. |
| Table matching | Source and destination table names must match. Matching is case-insensitive. | Deploy compatible destination tables and verify schema mappings before starting. |
| Concurrent migrations | Only one active migration can run against a given flexible server instance at a time. | To migrate data to multiple databases on the same PostgreSQL server, create a separate migration for each destination database and run the migrations sequentially. |
| Resume | The workflow doesn't provide resume capability. | Review error messages and failures before starting a fresh migration. |
| Data validation | Azure DMS doesn't currently provide built-in data validation. | Perform independent data and application validation before switching. |
Unsupported and partially supported objects
Azure DMS doesn't support the following Oracle data types:
| Data type or feature | Description |
|---|---|
| Nested tables | Oracle nested-table collections. |
| ADT inheritance | Object types that use inheritance. |
| Nested or composed ADTs | Object types containing other ADTs. |
| ADTs with LOB attributes | Object types containing large object attributes. |
ANYDATA |
Oracle values stored using the ANYDATA type. |
BFILE |
References to binary files stored outside the database. |
VECTOR |
Oracle vector values. |
Important
DMS copies NULL into destination columns corresponding to unsupported Oracle data types instead of copying their source values. Plan a separate migration approach to populate these columns, and validate their contents before switching applications.
Frequently asked questions
Does Azure DMS migrate both schema and data?
Azure DMS for Oracle to Azure Database for PostgreSQL Flexible Server or Azure HorizonDB handles data movement only. Use the Oracle schema conversion tool in the PostgreSQL extension for Visual Studio Code to convert the schema and deploy the destination objects before starting the data migration.
How do I get started?
Follow the data migration tutorial. It covers source and target preparation, database permissions, connectivity, the Azure portal workflow, monitoring, and validation.
Do I need to install migration software?
No. For the Azure portal workflow, DMS provisions and manages the migration infrastructure. You don't need to install migration software or deploy a migration VM.
Will my application need downtime?
Yes. Currently Azure DMS only supports offline migrations for Oracle. Stop applications and scheduled jobs that modify the data you want to migrate before starting the copy. Keep the Oracle database and listener running so DMS can read the snapshot.
Applications remain unavailable until copying, validation, and the switch to PostgreSQL are complete.
How should I estimate the production migration window?
Start with a nonproduction rehearsal, then test with a representative dataset and network configuration. Use the results to plan time for data copying, validation, application switching, and contingency.
With the default DMS configuration, copying 1 TB of data takes approximately three hours. Actual migration time varies with workload and environment conditions
What happens to source changes made after the snapshot?
They aren't copied to the target. Offline migration doesn't provide ongoing replication or change synchronization.
Can I migrate a multiterabyte database?
Yes. DMS supports multiterabyte data migrations. Migration time depends on data volume, distribution across tables, network throughput, and source and target capacity. Test with representative data to estimate the time required for your production migration.
Can I migrate multiple schemas to different databases?
You can include multiple Oracle schemas in one migration, but all must map to schemas within a single target PostgreSQL database. To migrate to multiple databases on the same target server, create a separate migration for each database and run the migrations sequentially.
What permissions do the migration accounts need?
- The Oracle account needs access to the schemas you want to migrate and the required snapshot-read permissions. Learn more
- The PostgreSQL account needs the access required to load the prepared destination tables. Learn more
Can I use private connectivity?
Yes. Azure DMS supports public and private connectivity. For private access, configure the required virtual networks, DNS resolution, routes, and firewall access. Depending on the environment, connectivity can involve virtual network peering, private endpoints, or VPN or ExpressRoute for Oracle sources outside Azure.
Is data encrypted during migration?
Connections to Azure Database for PostgreSQL Flexible server and Azure HorizonDB from DMS are encrypted using TLS.
For the Oracle server, Azure DMS supports TCP and TCPS connections. TCPS uses TLS to encrypt the connection and is recommended. TCP doesn't encrypt the connection.
Does migration data stay in one Azure region?
Data follows the source-to-DMS-to-target path. If these resources are in different regions, the migration can transfer data across regions.
Choose the Azure DMS and target locations to meet your organization's residency requirements and minimize unnecessary cross-region transfers.
How do I validate the migrated data?
Azure DMS doesn't currently provide built-in source-to-target data validation. After the migration completes, you're responsible for validating the migrated data:
- Compare row counts for every table included in the migration.
- Test application queries and APIs against the target, and verify that the returned data matches the results from the source.
Is there a charge for the migration service?
There are no charges for using Azure DMS to copy data from Oracle to Azure Database for PostgreSQL or Azure HorizonDB.
Can I use a larger SKU for migration?
The default migration runtime configuration that Azure DMS provisions meets most migration needs. Increasing the runtime SKU alone doesn't guarantee higher throughput or a shorter migration time. If throughput is lower than expected, submit a support request for help assessing performance and determining whether a higher-capacity runtime is appropriate.
What impact does offline migration have on the Oracle source server?
Offline migration isn't expected to significantly affect Oracle source performance. Azure DMS uses parallel connections to read source data. These reads might introduce some overhead, so rehearse the migration to confirm the impact in your environment.