Migrate data from Oracle to Azure Cosmos DB Cassandra API account using Arcion
APPLIES TO: Cassandra API
Cassandra API in Azure Cosmos DB has become a great choice for enterprise workloads that are running on Oracle for reasons such as:
Better scalability and availability: It eliminates single points of failure, better scalability, and availability for your applications.
Significant cost savings: You can save cost with Azure Cosmos DB, which includes the cost of VM’s, bandwidth, and any applicable Oracle licenses. Additionally, you don’t have to manage the data centers, servers, SSD storage, networking, and electricity costs.
No overhead of managing and monitoring: As a fully managed cloud service, Azure Cosmos DB removes the overhead of managing and monitoring a myriad of settings.
There are various ways to migrate database workloads from one platform to another. Arcion is a tool that offers a secure and reliable way to perform zero downtime migration from other databases to Azure Cosmos DB. This article describes the steps required to migrate data from Oracle database to Azure Cosmos DB Cassandra API using Arcion.
This offering from Arcion is currently in beta. For more information, please contact them at Arcion Support
Benefits using Arcion for migration
Arcion’s migration solution follows a step by step approach to migrate complex operational workloads. The following are some of the key aspects of Arcion’s zero-downtime migration plan:
It offers automatic migration of business logic (tables, indexes, views) from Oracle database to Azure Cosmos DB. You don’t have to create schemas manually.
Arcion offers high-volume and parallel database replication. It enables both the source and target platforms to be in-sync during the migration by using a technique called Change-Data-Capture (CDC). By using CDC, Arcion continuously pulls a stream of changes from the source database(Oracle) and applies it to the destination database(Azure Cosmos DB).
It's fault-tolerant and guarantees exactly once delivery of data even during a hardware or software failure in the system.
It secures the data during transit using security methodologies like TLS/SSL, encryption.
It offers services to convert complex business logic written in PL/SQL to equivalent business logic in Azure Cosmos DB.
Steps to migrate data
This section describes the steps required to setup Arcion and migrates data from Oracle database to Azure Cosmos DB.
From the computer where you plan to install the Arcion replicant, add a security certificate. This certificate is required by the Arcion replicant to establish a TLS connection with the specified Azure Cosmos DB account. You can add the certificate with the following steps:
wget https://cacert.omniroot.com/bc2025.crt mv bc2025.crt bc2025.cer keytool -keystore $JAVA_HOME/lib/security/cacerts -importcert -alias bc2025ca -file bc2025.cer
From the CLI terminal, set up the source database configuration. Open the configuration file using
vi conf/conn/oracle.ymlcommand and add a comma-separated list of IP addresses of the oracle nodes, port number, username, password, and any other required details. The following code shows an example configuration file:
type: ORACLE host: localhost port: 53546 service-name: IO username: '<Username of your Oracle database>' password: '<Password of your Oracle database>' conn-cnt: 30 use-ssl: false
After filling out the configuration details, save and close the file.
Optionally, you can set up the source database filter file. The filter file specifies which schemas or tables to migrate. Open the configuration file using
vi filter/oracle_filter.ymlcommand and enter the following configuration details:
allow: - schema: “io_arcion” Types: [TABLE]
After filling out the database filter details, save and close the file.
Next you will set up the configuration of the destination database. Before you define the configuration, create an Azure Cosmos DB Cassandra API account. Choose the right partition key from your data and then create a Keyspace, and a table to store the migrated data.
Before migrating the data, increase the container throughput to the amount required for your application to migrate quickly. For example, you can increase the throughput to 100000 RUs. Scaling the throughput before starting the migration will help you to migrate your data in less time.
You must decrease the throughput after the migration is complete. Based on the amount of data stored and RUs required for each operation, you can estimate the throughput required after data migration. To learn more on how to estimate the RUs required, see Provision throughput on containers and databases and Estimate RU/s using the Azure Cosmos DB capacity planner articles.
Get the Contact Point, Port, Username, and Primary Password of your Azure Cosmos account from the Connection String pane. You will use these values in the configuration file.
From the CLI terminal, set up the destination database configuration. Open the configuration file using
vi conf/conn/cosmosdb.ymlcommand and add a comma-separated list of host URI, port number, username, password, and other required parameters. The following is an example of contents in the configuration file:
type: COSMOSDB host: `<Azure Cosmos account’s Contact point>` port: 10350 username: 'arciondemo' password: `<Your Azure Cosmos account’s primary password>' max-connections: 30 use-ssl: false
Next migrate the data using Arcion. You can run the Arcion replicant in full or snapshot mode:
Full mode – In this mode, the replicant continues to run after migration and it listens for any changes on the source Oracle system. If it detects any changes, they're replicated on the target Azure Cosmos account in real time.
Snapshot mode – In this mode, you can perform schema migration and one-time data replication. Real-time replication isn’t supported with this option.
By using the above two modes, migration can be performed with zero downtime.
To migrate data, from the Arcion replicant CLI terminal, run the following command:
./bin/replicant full conf/conn/oracle.yaml conf/conn/cosmosdb.yaml --filter filter/oracle_filter.yaml --replace-existing
The replicant UI shows the replication progress. Once the schema migration and snapshot operation are done, the progress shows 100%. After the migration is complete, you can validate the data on the target Azure Cosmos database.
Because you have used full mode for migration, you can perform operations such as insert, update, or delete data on the source Oracle database. Later you can validate that they're replicated real time on the target Azure Cosmos database. After the migration, make sure to decrease the throughput configured for your Azure Cosmos container.
You can stop the replicant any point and restart it with --resume switch. The replication resumes from the point it has stopped without compromising on data consistency. The following command shows how to use the resume switch.
./bin/replicant full conf/conn/oracle.yaml conf/conn/cosmosdb.yaml --filter filter/oracle_filter.yaml --replace-existing --resume
To learn more on the data migration to destination, real-time migration, see the Arcion replicant demo.
Submit and view feedback for