OMS V4.0.1

Version information

• Version number: V4.0.1

• Previous version: V3.4.0

• Version release date: February 26, 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 can be directly upgraded to V4.0.1.

Supported versions of data terminals

New features

Data migration and synchronization

• Added support for migrating data from a MySQL database to MySQL compatible mode of OceanBase Database V4.0.0, including schema migration, full migration, incremental synchronization, and full verification.

• Added support for RocketMQ instances of commercial edition V4.x and V5.x.

• Added full synchronization feature from OceanBase Database to RocketMQ.

• Added the capability to select incremental synchronization (excluding full migration scenarios) and choose the incremental synchronization timestamp.

• Added support for the synchronization DDL feature from OceanBase database to Kafka, allowing users to promptly perceive Schema changes and simplify the docking solution.

• Added support for Debezium JSON format for synchronization to Kafka, DataHub (Blob type), and RocketMQ, facilitating easy integration with downstream big data ecosystems.

• Added the ability for users to freely set cluster_id, facilitating processing based on actual situations. Commonly used in business scenarios such as data cleansing and historical databases.

• Added support for mapping multiple selection objects to a single target object using matching rules. This facilitates database migration from products like MyCat and TDDL.

• Added self-service throttling and rate limiting based on RPS and IOPS. Users can enable this feature during peak hours at the source or target to minimize impact on online business.

Feature updates and optimizations

Enhanced user interaction experience

• Provides process guidance and feature introduction to facilitate project creation.

• Provides 35 standardized error codes (total 110+), enhancing users' self-maintenance capabilities.

• Optimized rule matching and display logic to improve processing efficiency in scenarios with multiple matching rules.

• Added documentation creation, project renaming, and three selection object functionality scope descriptions during project creation.

• Standardized component names for data migration and synchronization to Store/Incr-Sync/Full-Import/Full-Verification, and unified optimization of underlying technical logic to reduce user learning curve and facilitate autonomous maintenance.

Feature upgrades

• Supports ROOT/ADMIN/USER three-layer permission model and read-only roles, with permission control by department, enhancing system permission management granularity.

• Supports SSO (OAuth2 protocol) & ASO (Alicloud Private Cloud) single sign-on for unified management and improved work efficiency.

• Provides object removal functionality during precheck, facilitating easy project creation and enhancing product usability.

• Added account lock logic after 5 consecutive failed login attempts, increasing the difficulty of brute force attacks and enhancing product security.

• Supports dynamic project name changes for easier project management.

• Added heartbeat table support for DB2 LUW data sources to address high latency in source systems with no business writes.

• Optimized OMS & OCP alert display information and logic for easier alert handling.

• Provide standard performance indicators for full-volume import and incremental synchronization, facilitating users in resource planning and project duration estimation during the early stage of a project.

Bug fixes

Known issues

Product behavior changes

• The system parameter perceiveStoreClientCheckpoint specified in the ha.config parameter is enabled by default.

  This parameter is mainly intended to resolve issues where the project fails during incremental synchronization due to the target point written by the Incr-Sync component being later than the earliest point that can be pulled by the Store component in scenarios such as upgrades or write exceptions in the target. Starting from this version, OMS automatically starts an appropriate store to respond to point requests from downstream systems, enhancing the ease of use of the product.

• The serialization formats Default and DefaultExtendColumnType are extended to include TransID.

  In an OceanBase database, TransID is a transaction ID. inc is an incremental number, addr is the address of the coordinator, ts is the time when the transaction ID is generated, and hash is the hash value of the three preceding items. If the transaction is incomplete, TransID is null. In a MySQL or Oracle database, TransID is a checkpoint.

  Downstream systems can use this value for transactional delivery to ensure the integrity of transactions.

• The serialization formats Default and DefaultExtendColumnType are extended to include Cluster_ID.

  In an OceanBase database, ob_org_cluster_id specifies the cluster ID for a session and is persisted in the transaction log. You can set this parameter by user or transaction, and downstream systems perform corresponding business processing based on the value of this parameter. This feature is often used in business scenarios such as data cleansing and historical databases.

Feature updates and guides

• Component name changes

  OMS V4.0.1 standardizes component names at the product layer to improve usability. The following table describes the corresponding relationships between new and old component names.

  Old component name	New component name
  Store (log pull component)	Store (incremental pull component)
  JDBCWriter (real-time sync component) or Connector (synchronization write component)	Incr-Sync (incremental synchronization component)
  Connector (full synchronization component) or Checker-Full (full migration component)	Full-Import (full import component)
  Checker-Verify (full verification component)	Full-Verification (full verification component)

• How to set throttling and speed limits

  The throttleRps parameter in the coordinator section of the Full-Import or Incr-Sync component limits the Records Per Second (RPS), and the throttleIOPS parameter limits the I/O Per Second (IOPS). Set related parameters as needed to reduce the impact of data synchronization on the source or target and effectively prevent business losses. For more information, see How to set throttling and speed limits.

• Upgrade of role-based privilege model

  OMS V4.0.1 now supports the three-layer privilege model with levels ROOT, ADMIN, and USER, and provides department-based privilege isolation for ADMIN and USER privileges. It also supports read/write splitting for ROOT and ADMIN privileges, meeting the privilege management requirements of enterprise customers.

• How to set password expiration policies

  OMS V4.0.1 provides role-based password expiration policies, which are disabled by default. To change the settings, go to System Management > System Parameters and modify the value of oms.user.password.expiration.date.config. This meets the password management requirements of enterprise customers.

• Parameter changes of components

  The parameters of Full-Import and Incr-Sync components in OMS V4.0.1 are significantly different from those in earlier versions. For more information, see Component parameters.

• How to enable SSO (third-party login)

  If you use SSO for logging in to OMS, you need to integrate with the OIDC protocol and add new parameters to the config.yaml template file. For more information, see Integrate OMS with OIDC for SSO.