Multicloud

Your Options to Migrate Data Into Autonomous Database on Oracle Database@Azure

Introduction

Customers can deploy Oracle Autonomous Database Serverless (ADB-S) on Oracle Database@Azure to benefit from Autonomous Database features in the Azure’s data center, next to their Azure applications, ensuring low latency and high performance.

This blog post highlights the options to migrate your data from an Oracle database on-premises to ADB-S on Oracle Database@Azure.

Option 1: Using Oracle Cloud (OCI)

Your ADB-S on Oracle Database@Azure is accessible through the OCI network. If you have network connectivity from on-premises to OCI and can provision OCI resources for the migration, then just consider it as any other ADB-S on OCI. All migration methods you know from OCI work seamlessly.

You can migrate manually using Data Pump and OCI Object Storage or automate the process with OCI Database Migration Service (DMS) and Oracle Zero Downtime Migration (ZDM). The automated way is recommended, especially for fleet migrations.

For more information, see:

Option 2: Using Azure Files NFS

Azure Files enables you to create an NFS share that can be mounted on ADB-S on Oracle Database@Azure and be used to store and access your Data Pump dump files.

You can migrate manually using Data Pump and NFS share or automate the process with Oracle Zero Downtime Migration (ZDM). The automated way is recommended, especially for fleet migrations.

For more information, see:

Option 3: Using Database Link

You can create a Database Link in ADB-S pointing to your on-premises Oracle database and import the data directly without an intermediate storage location. This option might be feasible for “small” databases, depending on your requirements.

You can migrate manually using Data Pump over Network Link (database link) or automate the process with Oracle Zero Downtime Migration (ZDM). The automated way is recommended, especially for fleet migrations.

For more information, see:

Option 4: Using Azure Blob Storage

You can create credentials in the Oracle Autonomous Database to access Azure Blob Storage and use Data Pump to import your dump files. However, due to restrictions in the Azure delegated subnet, where the Autonomous Database resides, the Azure storage account needs to be enabled for access from everywhere (over the public internet). You can still use Data Pump encryption (requires the Advanced Security Option) while loading the data if this is a feasible solution for you.

For more information, see:

Conclusion

Loading data into Oracle Autonomous Database@Azure through Oracle Cloud works the same way for any other Oracle Autonomous Database, including using OCI Object Storage, OCI GoldenGate marketplace image, OCI DMS, and Oracle ZDM to automate and simplify the migration process.

For migrations through the Azure cloud, you can use Azure Files NFS or database links. Both require adding the storage account FQDN or the target database hostname and IPs to the OCI DNS resolver for the Autonomous Database to be able to resolve the hostnames.

Furthermore, you can use Azure Blob Storage to upload the data using Oracle Data Pump if the Azure storage account allows access over the public network.

Further Reading

Would you like to get notified when the next post is published?