Recently, the OceanBase Migration Service (OMS) released V3.1.0.
In this article, we will take a look at OMS V3.1.0, in addition to the new support for OBServer V3.1.0, which has been added and improved.
Improve data migration services
Starting from this version, the OMS supports data migration from the Oracle 12C to 19C pluggable databases (PDB) to the OceanBase Oracle database. Improved the supported data migration application scenarios, enabling smooth migration of applications to the OceanBase database.
Improve data synchronization services
OMS V3.1.0 supports data synchronization from MySQL database to DataHub
DataHub is a streaming data processing platform that provides publishing, subscription and distribution of streaming data. With OMS V3.1.0, in addition to OceanBase database and Oracle database, you can also synchronize the storage and increment data in MySQL database to DataHub, helping you quickly realize real-time data analysis using big data products such as stream computing.
2) Improve the convergence and synchronization function of logical tables
Added Real-time synchronization between logical tables and physical tables to help you quickly build enterprise internal BI, interactive query, and real-time report systems.
Support to import objects through text
OceanBase supports text import when data is synchronized to message queue data terminals.
After you enter the object to be migrated and click To check the validity, the OMS automatically checks the validity of the added object to quickly add the migrated object.
Improve the high availability features
High availability (HA) The HIGH availability function is an effective solution to ensure service continuity. To maximize the stability and availability of synchronous links, the OMS designs a cluster high availability architecture that can be switched over in seconds.
Earlier than OMS V3.1.0, the OMS HA function supports only automatic log pull components. Starting from OMS V3.1.0, the HA function automatically protects the synchronization write component of the OMS. When the synchronization service becomes unavailable due to a single point of failure of the OMS, the HA service automatically switches the incremental traffic of the faulty node to other available resource nodes in the OMS cluster. The synchronization link is not affected. Meanwhile, the HA function of this version also fully supports the application scenario of MySQL master/standby switchover.
Starting from OMS V3.1.0, you can modify HA configuration parameters on the OMS console based on actual service scenarios and environments. On the System Management > System Parameter page, you can modify the SYSTEM configuration of the HA function by editing the ha.config item.
For more information about the OMS, visit the OceanBase website.