Version information
Version: V4.0.2
Previous version: V4.0.1
Version release date: April 24, 2023
Supported upgrade versions:
Versions earlier than OMS V3.2.1 require an upgrade to V3.2.1 first.
OMS V3.2.1 and later versions can be directly upgraded to OMS V4.0.2.
We recommend that you use oblogproxy V2.1.0 or later.
Supported versions of data terminals
Notice
OceanBase Database V4.0.0 in the MySQL compatible mode is supported only for migrating data to.
| Feature | OceanBase Database version | Other data terminal 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, 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, V3.2.4, 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, V3.2.4 |
|
|
New features
Data migration and synchronization
OMS allows you to specify the IP address and port number of oblogproxy to solve the problem of inability to synchronize incremental data in network isolation scenarios.
Note
In network isolation scenarios, the OMs and OceanBase Servers are in different networks, and oblogproxy is deployed in the network where OceanBase Servers are located to forward incremental logs of OceanBase Servers.
Bug fixes
| Ticket | Introduced in version |
|---|---|
| Fixed the issue where the specified modeNum does not take effect in the tenant-level synchronization store configuration synchronization project | OMS 4.0.1 |
| Fixed the issue where no real-time traffic metrics such as those for the full migration step are displayed when the full migration takes a short time | OMS 3.4.0 |
| Fixed the issue where an incremental synchronization error is reported due to the removal of table indexes during full migration in index-physical-matching data migration projects | OMS 4.0.1 |
| Modified the issue where the estimated completion time is not displayed for full migration | OMS 4.0.1 |
Known issues
| Ticket | Introduced in version |
|---|---|
| Fixed the issue where an error is reported when the TIMESTAMP type is specified as CURRENT_TIMESTAMP in the incremental DDL operations of a data migration project from a DB2 LUW database to the MySQL compatible mode database of OceanBase Database | OMS 3.3.0 |
| Fixed the issue where a null pointer exception is thrown when an incremental connector is configured for data synchronization from the MySQL compatible mode of OceanBase Database to a Kafka data source in an extraction, transformation, and loading (ETL) project | OMS 3.3.1 |
| Fixed the issue where search in the alert list does not take effect | OMS 4.0.1 |
Component versions (x86)
oboms-connector-v2-3.0.31-20230331205516.noarch
oboms-supervisor-2.1.9-20230412113712.noarch
oboms-xlog-store-5.4.4-20230411194602.alios7
ant-light-checker-1.2.60-20221115184619.noarch
oboms-verifier-1.0.11-20230417204129.noarch
oboms-cm-1.1.50-20230414142147.alios7.noarch
dbcat-1.9.0-SANPSHOT
ob2store 2.x deps: oceanbase-devel 2.2.77-20221025172724.el7 @taobao.7.x86_64.current
ob2store 3.x deps: oceanbase-devel 3.2.4.2-20230327143056.el7 @taobao.7.x86_64.current
ob2store 4.x deps: oceanbase-cdc 4.0.0.0-10000112022110216.el7 @taobao.7.x86_64.current
Feature updates and guides
Added the system parameter
oceanbase.logproxy.poolto set the IP address and port number of oblogproxy. This parameter is mainly used to synchronize incremental data in scenarios with network isolation.In a typical three-layer network architecture, OMs is located at the second layer as the application server, and OceanBase Database and oblogproxy are located at the third layer. oblogproxy serves as the proxy for forwarding incremental data.
Upgrade limitations
If you are using oblogproxy with OMS of a version earlier than 3.2.1, you must upgrade OMS to version 4.0.2 and create a new project.