Release objectives
To better assist users in operating and maintaining OceanBase products, OAT V4.5.1 focuses on enhancing the management capabilities for multiple product components and network compatibility. It introduces management features for DataPilot and OMA, supports the separated mode of OMS, and IPv6 network deployment, further improving system flexibility, stability, and operational efficiency. Additionally, it optimizes deployment restrictions and cluster configuration processes, providing more efficient and reliable support for users to build and manage the OceanBase ecosystem in complex environments.
Release overview
- Release date: June 18, 2026
- Previous version: V4.5.0
- Version number: V4.5.1
New features
Added management for the DataPilot product, including:
- Install DataPilot
- Uninstall DataPilot
- DataPilot container operations
Added a separated mode for the OMS product (management and components use different images), including:
- Install OMS in separated mode
- Upgrade OMS in separated mode
- Data refresh
- Resource changes
- Container operations
- Uninstall
OAT deployment and O&M of OMS now support IPv6 networks, including:
- Supports deploying OMS using an IPv6 MetaDB.
- Supports deploying influxdb and OMS on servers with IPv6 addresses.
- When deploying the OMS container on an IPv6 server, all configuration file addresses can use IPv6.
- Supports configuring IPv6 load balancing for OMS.
Added management for the OMA tool, including:
- Install OMA
- Resource changes
- Uninstall OMA
Feature enhancements
- Added restrictions on MetaDB versions when deploying OMS. Specifically, when using OAT V4.5.1 to deploy OMS V4.3.2 or later, you cannot use MetaDB V2.2.77.
- Supports automated deployment of multi-cluster OCP: when deploying an OCP standby cluster, you can select to Associate with the primary OCP cluster.
- Added a Add button to the Basic Information section on the Add Server page: when the Initialize the configuration and disk initialization fields are the same, you can add multiple servers in bulk.
Considerations
If you deploy OMS with IPv6, ensure that MetaDB, InfluxDB, and OMS all use IPv6 addresses.
When deploying OMS in split mode, note the following:
- In a multi-region deployment, each region must have both a management container and a component container.
- The console (8089) and CM (8088) services reside in the management container. When configuring load balancing, follow the deployment pattern of the management container, setting up one load balancing rule per region.
- You can set a primary region for the management container: after setting a primary region, only the first management node in the primary region starts the console and CM services; other management container nodes start only the CM service.