The data migration service is a service provided by OceanBase Database that integrates data migration and incremental data synchronization. It offers a centralized management platform with a visual interface, allowing you to easily configure and migrate data between MySQL/Oracle databases on AWS, Huawei Cloud, Alibaba Cloud, and OceanBase Database. Additionally, it supports data migration between different tenant types within OceanBase Database.
Migrations aims to help you achieve secure, stable, and efficient real-time data migration between a MySQL or Oracle database and OceanBase Database at low costs and risks. Project members are categorized into the roles of Project Owner, Project Admin, Instance Admin, Project Member, Data Read/Write, and Data Services Admin. Project Admin and Data Services Admin have read-write access to the menus and data resources within the project's data services modules. Members with other roles only have read-only access to the menus and all data within the project's data services modules. You can set project roles on the Manage Organization page. For more information, see Manage organization and project access.
Features and benefits
Real-time data migration without interrupting or affecting applications
You can use Migrations to seamlessly migrate data to OceanBase Database without interrupting your applications. Migrations minimizes the risks of business migration and helps enterprises build business with high availability and reliability.
High-performance, secure, and reliable data migration
Migrations can replicate large amounts of data in real time with seconds-level latency. It allows you to migrate data without affecting or interrupting your business applications, ensuring data integrity and transaction consistency.
All-in-one interaction
Migrations allows you to manage data migration throughout its whole lifecycle. You can create, configure, and monitor data migration tasks in the console.
Easy data migration to OceanBase Database
Migrations supports the features of every version of OceanBase Database. It collects and converts database objects and supports data migration without interrupting the services of the source database.
Data migration process
To create and manage a data migration task, perform the following steps:
Prepare for data migration to make sure that the following conditions are met:
Create a MySQL or Oracle database instance.
Create an OceanBase instance and a tenant. For more information, see Create an instance and Create a tenant.
Create dedicated database users for data migration in the source and target, and grant required privileges to the users. For more information, see User privileges.
For data migration between a MySQL or Oracle database and OceanBase Database:
If you want to select Endpoint as the connection type when you create a data migration task, you need to first add the account ID displayed on the page to the whitelist of your endpoint service, to allow the endpoint of the account to connect to the endpoint service. For more information, see Connect via private network.
If you want to select Public IP as the connection type when you create the data migration task, you need to first add the data source IP address displayed on the page to the whitelist of the MySQL/Oracle database instance to ensure connectivity. For more information, see Connect via public network.
Create a data migration task.
Configure the source, target, migration type, and objects to migrate for the data migration task based on your business needs. For more information, see the corresponding topic under Migrate data.
View details of the data migration task.
After the data migration task is started, it will be executed based on the selected migration types. For more information, see View details of a data migration task.
Optional: Delete the data migration task.
After the data migration task is completed, if data no longer needs to be synchronized from the source database to the target database, you can release the current data migration task. For more information, see Delete a data migration task.
Supported migration types
| Data migration task | Schema migration | Full migration | Incremental DML | Incremental DDL | Tables without primary keys |
|---|---|---|---|---|---|
| MySQL -> OB_MySQL | Supported | Supported | Supported | Supported | Supported |
| OB_MySQL -> OB_MySQL | Supported | Supported | Supported | Supported | Supported |
| OB_MySQL -> MySQL | Supported | Supported | Supported | Supported | Supported |
| Oracle -> OB_Oracle | Supported | Supported | Supported | Supported | Supported |
| OB_Oracle -> OB_Oracle | Supported | Supported | Supported | Supported | Supported |
| OB_Oracle -> Oracle | Supported | Supported | Supported | Supported | Supported |
| OB_MySQL -> Kafka | Not supported | Supported | Supported | Supported | Supported |
| OB_Oracle -> Kafka | Not supported | Supported | Supported | Supported | Supported |
| PostgreSQL -> OB_MySQL | Supported | Supported | Supported | Supported | Supported |
| PostgreSQL -> OB_Oracle | Supported | Supported | Supported | Supported | Supported |
| OB_MySQL -> PostgreSQL | Supported | Supported | Supported | Supported | Supported |
| OB_Oracle -> PostgreSQL | Supported | Supported | Supported | Supported | Supported |
| TiDB -> OB_MySQL | Supported | Supported | Supported | Not supported | Supported |
| OB_MySQL -> TiDB | Supported | Supported | Supported | Not supported | Supported |