Version information
Version: V4.0.2
Previous version: V4.0.1
Release date: April 24, 2023
Upgrade path:
OceanBase Migration Service (OMS) of a version earlier than V3.2.1 must be upgraded to V3.2.1 first.
OMS V3.2.1 and later can be directly upgraded to OMS V4.0.2.
Compatible database versions
Notice
A MySQL tenant of OceanBase Database V4.0.0 can only be the destination of data migration from MySQL Database.
| Feature | OceanBase Database version | Other database versions | OCP version |
|---|---|---|---|
| Data migration | V1.4.79, V2.1.1, V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70,V 2.2.72, V2.2.74, V2.2.75, V2.2.76, V2.2.76BP1, V2.2.77, V3.1.0, V3.1.1, V3.1.2, V3.2.1, V3.2.2, V3.2.3, V3.2.4, and V4.0.0 |
|
|
| Data synchronization | V2.2.20, V2.2.30, V2.2.50, V2.2.52, V2.2.70, V2.2.72, V2.2.74, V2.2.75, V2.2.76, V2.2.76BP1, V2.2.77, V3.1.0, V3.1.1, V3.1.2, V3.2.1, V3.2.2, V3.2.3, and V3.2.4 |
|
|
New features
Data migration and synchronization
OMS allows you to specify the IP address and port number of oblogproxy to synchronize incremental data across isolated networks.
Feature changes and guidance
New system parameter: The
oceanbase.logproxy.poolparameter is provided for specifying the IP address and port number of oblogproxy to synchronize incremental data in the following two typical cross-network scenarios:Typical three-layer network architecture: OMS is deployed at Layer 2 as an application server. OceanBase Database and oblogproxy are deployed at Layer 3. oblogproxy serves as a proxy for forwarding incremental data.