Oracle Zero Downtime Migration is a widely used automated solution for migrating Oracle Databases into any Oracle-owned infrastructure, including Exadata Database Machine on-premises, Exadata Cloud@Customer, and Oracle Cloud Infrastructure (OCI), including Oracle Database@Azure, Oracle Database@Google Cloud, and Oracle Database@AWS.
Migrate on-premises databases to Oracle Cloud Infrastructure
Oracle Zero Downtime Migration is Oracle’s recommended solution to migrate Oracle Databases to OCI using Oracle Maximum Availability Architecture (MAA).
Learn more about migrating your on-premises databases to Oracle Cloud (PDF)
Migrate on-premises Oracle Databases to Oracle Exadata
Oracle Zero Downtime Migration migrates your database to Oracle Exadata, leveraging the same automation and orchestration available for cloud migration.
Learn more about migrating your on-premises databases to Oracle Exadata
Migrate Oracle Databases on AWS RDS to Oracle Cloud Infrastructure
Migrate your Oracle databases on AWS RDS to Oracle Database using ZDM's automation and orchestration, free of charge.
Learn more about migrating your Oracle Database on AWS RDS to Oracle Cloud
Oracle Zero Downtime Migration-supported sources include Oracle Databases on-premises, on Oracle Cloud Infrastructure, and on Amazon Web Services RDS for Oracle.
Oracle ZDM supports the following source database versions:
Oracle ZDM supports the following source configurations:
Oracle Database on Oracle Cloud is available in a range of configurations, according to your needs. Oracle Zero Downtime Migration supports different target Oracle Database Cloud Services.
| Exadata On-Premises | Base Database Service | Oracle Exadata Database Service on Dedicated Infrastructure* | Oracle Exadata Database Service on Cloud@Customer | Oracle Autonomous Database Serverless* | Oracle Autonomous Database on Dedicated Exadata Infrastructure | |
|---|---|---|---|---|---|---|
| Physical Online Migration | yes |
yes |
yes |
yes |
no |
no |
| Physical Offline Migration | yes |
yes |
yes |
yes |
no |
no |
| Logical Online Migration | yes |
yes |
yes |
yes |
yes |
yes |
| Logical Offline Migration | yes |
yes |
yes |
yes |
yes |
yes |
| Hybrid Offline Migration | yes |
yes |
yes |
yes |
no |
no |
*OCI and Oracle Database@Hyperscaler
Get hands-on experience with Oracle Always Free Services
Find out how Oracle Zero Downtime Migration can help you.
Diagram of physical offline migration, showing all required components with user applications pointing to the on-premises source database. The source database is connected to a backup location via https, the same way the backup location is connected to the target database.
Diagram of physical online migration with backup location, showing all required components with user applications pointing to the on-premises source database. The source database is connected to a backup location via https, the same way the backup location is connected to the target database. Then, ZDM is connected to both source and target via SSH, and the source database is connected to the target database via SQLnet.
Diagram of physical online migration with direct data transfer, showing all required components with user applications pointing to the on-premises source database. ZDM is connected to both source and target via SSH, and the source database is connected to the target database via SQLnet.
Diagram of logical offline migration, showing all required components with user applications pointing to the on-premises source database. The source database is connected to a backup location via https, the same way the backup location is connected to the target database. Data Pump flows for export from the source and import from the target. Then, ZDM is connected to both source and target via SSH.
Diagram of Logical Online Migration, showing all required components, user applications pointing to the on-premises source database. The source database connected to a Backup Location via https, same way the backup location is connected to the target database. Data Pump flows for export from the source and import from the target. Then, ZDM is connected to both source and target via SSH, and a GoldenGate hub with two microservices (a replicate and an extract) are connected respectively to the source and the target.
