Data transmission is a feature that supports data interaction between a homogeneous or heterogeneous database and OceanBase Database. The data transmission feature provides the capabilities for online migration of inventory data and real-time synchronization of incremental data.
Features
The data transmission feature provides a visualized and centralized management platform. You can migrate data in real time with simple configurations. The data transmission feature aims to help you achieve real-time data migration and synchronization from a homogeneous or heterogeneous database to OceanBase Database with low risk, low cost, and high efficiency.
Data migration: one-time operation. After a data migration project is completed, resources occupied by the project are released. You can create a data migration project to migrate data between homogeneous or heterogeneous data sources in various business scenarios, such as database upgrade, cross-instance data migration, database splitting, and database scaling.
A data migration project is the basic unit of the data migration feature. When you create a data migration project, you can specify the migration level, which ranges from table to database. For more information, see Data migration.
Data synchronization: continuous operation. After a data synchronization project is created, data will be synchronized all the time to maintain the data consistency between the source and destination databases and to achieve the real-time flow of key business data. You can create a data synchronization project to synchronize data between data sources in real time in various business scenarios, such as multi-site high availability, remote disaster recovery, data aggregation, and real-time data warehousing. For more information, see Data synchronization.
Supported migration types
Acronyms and abbreviations
Instance type | Acronym or abbreviation |
Self-managed database in VPC | VPC |
Database gateway | DG |
Self-managed database with public IP address | Public network |
MySQL tenant of OceanBase Database | OB_MySQL |
Oracle tenant of OceanBase Database | OB_Oracle |
Data migration
At present, it is not allowed to migrate data from an Oracle data source to a MySQL tenant of OceanBase Database, or from a MySQL data source to an Oracle tenant of OceanBase Database.
Direction | Schema migration | Full migration | Incremental migration | Full verification | Reverse incremental migration | Table without a primary key |
MySQL (RDS) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Supported | Supported |
MySQL (PolarDB) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Supported | Supported |
MySQL (public network) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Supported | Supported |
MySQL (VPC) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Supported | Supported |
MySQL (DG) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Supported | Supported |
Oracle (DG) -> OB_Oracle (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
Oracle (public network) -> OB_Oracle (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
Oracle (VPC) -> OB_Oracle (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
OB_MySQL (Alibaba Cloud instance) -> MySQL (RDS) | Supported | Supported | Supported | Supported | Supported | Supported |
OB_MySQL (Alibaba Cloud instance) -> MySQL (PolarDB) | Supported | Supported | Supported | Supported | Supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> MySQL (public network) | Supported | Supported | Supported | Supported | Supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> MySQL (VPC) | Supported | Supported | Supported | Supported | Supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> MySQL (DG) | Supported | Supported | Supported | Supported | Supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
OB_MySQL (VPC) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
OB_Oracle (Alibaba Cloud instance) -> OB_Oracle (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
OB_Oracle (VPC) -> OB_Oracle (Alibaba Cloud instance) | Supported | Supported | Supported | Supported | Not supported | Supported |
Data synchronization
Direction | Schema synchronization | Full synchronization | Incremental synchronization | Data verification | Table without a primary key |
OB_MySQL (Alibaba Cloud instance) -> OB_MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> OB_MySQL (VPC) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> AnalyticDB for MySQL (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> DataHub (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> DataHub (VPC) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> DataHub (public network) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> DataHub (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> DataHub (VPC) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> DataHub (public network) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> Kafka (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> Kafka (VPC) | Supported | Supported | Supported | Not supported | Not supported |
OB_MySQL (Alibaba Cloud instance) -> Kafka (public network) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> Kafka (Alibaba Cloud instance) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> Kafka (VPC) | Supported | Supported | Supported | Not supported | Not supported |
OB_Oracle (Alibaba Cloud instance) -> Kafka (public network) | Supported | Supported | Supported | Not supported | Not supported |
Supported database versions
Feature | OBServer version | Other database versions |
Data migration | V1.4.79, V2.2.30, V2.2.52, V2.2.76, V2.2.77, V3.1.x, V3.2.x, and V4.0 Important At present, a MySQL tenant of OceanBase Database V4.0 can only be the destination of data migration from MySQL Database. |
|
Data synchronization | V2.2.30, V2.2.52, V2.2.76, V2.2.77, V3.1.x, and V3.2.x |
|