Getting Started with the Migration Utility

The Oracle Exadata Cloud Infrastructure Migration Utility streamlines and automates migrations across Exadata Cloud Infrastructure environments.

The utility simplifies hardware refreshes, shape migrations, and cross-service transitions while ensuring accuracy and complete OCI auditability.

About the Migration Utility

Oracle Exadata Cloud Infrastructure Migration Utility is a lightweight Linux-based tool that uses OCI APIs to discover source infrastructure configurations, generate and validate migration templates, provision target Exadata infrastructure and VM clusters, and migrate databases and PDBs. It supports ExaDB-D and ExaDB-C@C migrations across supported infrastructure models, including cross-type migrations, hardware refreshes, system retirement, database redistribution, and PDB relocation. Key benefits include pre-execution validation, parallel and selective migrations, no-downtime database migration through Data Guard standby creation and switchover or failover, OCI auditing, and migration monitoring.

Migration Utility Prerequisites

The utility requires OCI authentication through API keys, instance principals, or resource principals, with appropriate users, groups or dynamic groups, matching rules, and IAM policies for database, networking, infrastructure, VM cluster, DNS, work request, and PDB operations; target-compartment permissions are also required when applicable. ExaDB-D and ExaDB-C@C use different infrastructure-management policies. ExaDB-D migrations additionally require suitable VCN capacity, security rules, and source-target VCN connectivity or peering for Data Guard. The client must be a Linux x86-64 machine running Oracle Linux 7, 8, or 9, with sufficient OCI service limits and outbound HTTPS access through port 443.

Prepare to Use the Migration Utility

Preparation involves downloading the latest Linux x86-64 utility patch from My Oracle Support, copying and extracting it on the client as an appropriate user, and configuring proxy variables when required. Set authentication, OCI configuration-file, and profile environment variables when using instance principals, resource principals, custom configuration locations, or nondefault profiles. Before execution, collect the source Exadata Infrastructure OCID, VM Cluster OCID, and, for PDB relocation, the source Database OCID from the OCI Console for the relevant ExaDB-D or ExaDB-C@C resources.
Read More: Prepare to Use the Migration Utility