Migrate Oracle Databases to Autonomous Database

Oracle provides options to migrate your database to Autonomous Database.

You can choose one of these options depending on the amount of data you want to migrate, downtime requirements during the migration, network bandwidth between your source database and your Oracle Cloud Infrastructure region, and whether you want manual control over the migration.

Migration Prerequisites

Before starting your migration, it is recommended to run the Cloud Premigration Advisor Tool (CPAT), which helps you evaluate your source database for compatibility with the Autonomous Database.

CPAT identifies potential actions you may need to take before or during the migration, prioritizing their importance and suggesting resolutions. Some migration tools and services automatically run this advisor.

See Cloud Premigration Advisor Tool for more information.

Recommended Migration Methods

Following are the recommended migration methods to migrate your database into an Autonomous Database.

Online Migration

If your source database needs to be always online and you can only take minimal downtime for the migration, you can use one of the online migration services and tools below, independent of your database size. Note that both options require the source database to be on version 11.2.0.4 or later. If your source database is using an older version, you need to upgrade it first if you want to use one of the online migration methods.

Following are the online migration methods:

  • OCI Database Migration: OCI Database Migration, a managed cloud service, provides validated, cross-version, fault-tolerant, and incremental Oracle Database migrations for online and offline use cases. You can choose this option if you want a fully managed cloud service that handles the migration for you.

    See OCI Database Migration for more information.

  • Zero Downtime Migration (ZDM): Zero Downtime Migration (ZDM) is a tool with a command line interface that you install and run on a host you provision. Zero Downtime Migration provides online and offline migration options. You can use this option if you want more control over the migration.

    See Zero Downtime Migration for more information.

    Note:

    These methods also run the Cloud Premigration Advisor Tool (CPAT) to check your source database for compatibility with the Autonomous Database and use Oracle Data Pump and Oracle GoldenGate to carry out the migration for you.

Offline Migration

If you can take your source database offline for the migration, you can use one of the following migration options in addition to OCI Database Migration and Zero Downtime Migration (ZDM).

Note:

This is a manual method; you must orchestrate the export/import manually.

Following is the offline migration method:

  • Oracle Data Pump: Oracle Data Pump technology enables very high-speed movement of data and metadata from one database to another. You can export your source database or individual schemas as dump files and import them into the Autonomous Database. You can store the dump files on the Object Store or a network filesystem (NFS) that you can attach to your source database and to your Autonomous Database.

    See Overview of Oracle Data Pump for the product documentation for Oracle Data Pump.

    See Import Data Using Oracle Data Pump on Autonomous Database for more information about how to export and import your source schemas into the Autonomous Database.

Other Migration Methods

In addition to the recommended migration tools and services, you can use the following offline data migration methods:

Note:

These methods require more manual steps, coding, and advanced knowledge of each method. You must also migrate your source schema metadata using your own DDL scripts or tools such as Oracle Data Pump before initiating the data load using these methods. These options may be preferable for small data sets for which you want to avoid installing additional tools or using cloud migration services.

Following are the other offline migration methods:

  • Database Links: You can create database links from your Autonomous Database to your source database and insert data into your tables by running queries over the database link. You can use multiple sessions to load multiple tables concurrently to improve the performance of the data load.

    See Create Database Links from Autonomous Database to Another Autonomous Database for more information about creating database links from your Autonomous Database to your source databases.

  • Unload and Load Using Files: You can unload data from your source database into files and load those files into your target tables in your Autonomous Database. Autonomous Database supports loading data from different file formats including CSV, JSON, Parquet, and more. You can place the files on the Object Store or a network filesystem (NFS) attached to your Autonomous Database.

    See Load Data from Files in the Cloud for more information about how to load data from files in the object store.

    See Attach Network File System to Autonomous Database for attaching NFS directories to your Autonomous Database.

    See Load Data or Query Data from Files in a Directory for more information about loading data from files on a filesystem.

  • Materialized Views: Using database links from your Autonomous Database to your source database, you can also create materialized views in your target database. As changes happen on your source tables, you can refresh the materialized views to keep them updated during the migration.

    See Managing Read-Only Materialized Views for more information about using materialized views to replicate data.

Note:

Deciding the migration tool or service depends on multiple factors such as your source database, source data format, data volume, and complexity. To help you identify the most optimal solution for migrating your data to the Autonomous Database, Oracle provides an advisory utility called Oracle Cloud Migration Advisor. See Migrate Oracle Databases to OCI for more information about this utility.