OCP V4.5.0

OCP V4.5.0 is officially released! This upgrade focuses on the capability building of OceanBase AI: it adds support for OceanBase AI clusters (with shared storage architecture) and builds the foundational capabilities they rely on—Object Storage External Integration and Full Lifecycle Management for LogService components—to help users centrally manage and maintain databases and their supporting components in AI scenarios on OCP.

Key features:

• OceanBase AI version compatibility: Adds full lifecycle support for creating, operating, and monitoring OceanBase AI clusters (with shared storage architecture and kernel version 4.6.2.0 or later).

• Object storage external integration: Adds the "External Integration - Object Storage" management capability to uniformly maintain connection information and credentials for object storage (such as S3) relied upon by AI and LogService clusters. Supports connectivity verification and AK/SK rotation.

• LogService component management: Adds full lifecycle management capabilities for LogService (log service) clusters, including creation, start-stop-restart, scaling (Zone/Server), and AK rotation.

Version information

• Version number: V4.5.0

• Previous version: V4.4.2-BP2

• Version release date: August 3, 2026

• Supported upgrade path:

  • Currently, only direct upgrades from OCP V3.2.4 and later versions are supported.

  • For OCP V2.3.x and later, but before V3.2.4, you must first upgrade to OCP V3.3.4.

  • For OCP versions earlier than V2.3.0, you must first upgrade to OCP V2.3.x, then to OCP V3.3.4.

Supported OceanBase Database versions

OCP V4.5.0 supports the OceanBase Database versions listed in the following table.

• OceanBase V2.2.76 & OceanBase V2.2.77

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.0.x

• OceanBase V4.1.x

• OceanBase V4.2.x

• OceanBase V4.3.x

• OceanBase V4.4.x

• OceanBase V4.5.x

• OceanBase V4.6.x

Key feature overview

OceanBase AI version adaptation and compatibility

To enable users to manage both traditional OceanBase clusters and AI version (shared storage architecture) clusters on OCP, this release introduces new adaptations for AI clusters:

• Version requirement: The minimum supported OceanBase kernel version for AI clusters is now 4.6.2.0. Clusters with a lower version will be intercepted during creation or verification with a prompt.

• O&M capabilities: Supports creating AI clusters, automatic issuance of instructions to bind object storage during zone scaling, unit specification O&M, and installation and uninstallation of dedicated AI software packages.

• Monitoring adaptation: Distinguishes collection items and chart units for the shared storage (SS) mode, and fixes the display issue of monitoring charts when there is no data.

• Limitations (The following capabilities are currently not supported in AI clusters. Clear prompts will be displayed during operations):

  • Creating Oracle-compatible tenants is not supported.

  • Creating primary/standby (Standby) tenants is not supported. Disaster recovery is temporarily unavailable.

  • Cluster takeover (Takeover) is not supported.

  • Stopping a single zone is not supported.

Object storage external integration (New, dependent service for AI clusters/LogService)

Both OceanBase AI clusters and LogService clusters rely on object storage (such as S3) to store data. This release adds unified object storage management capabilities under "External Integration":

• Supports adding, editing, and deleting object storage integration configurations, maintaining connection information such as Endpoint, Bucket, AK/SK uniformly.

• Supports object storage connectivity verification (including Endpoint format verification) to detect configuration issues in advance.

• Supports viewing object storage reference relationships by user (AI cluster / LogService cluster).

• Supports replacing object storage AK/SK and adapts to kernel key rotation SQL rules, automatically completing synchronization on the cluster side during the rotation process.

LogService (Log Service) component lifecycle management (New)

Adds comprehensive management capabilities for LogService clusters and merges the three component categories—OBProxy, Binlog, and LogService—into a unified "Components" menu in the main menu:

• Cluster management: Create, delete, start, stop, restart, and synchronize status.

• Elastic scaling: Batch add/delete/start/stop/restart zones, batch add/delete/start/stop/restart servers.

• Parameter management: Metadata, creation/editing/deletion of parameter templates, and online modification of cluster parameters.

• Security: Pre-verification and rotation of object storage AK/SK, and management of organizational permissions (multi-level organization visibility).

• Observability: Dedicated monitoring metric collection, alert rules, and log query for the Log Service.

Product optimization

Cluster management

• Operations that are not supported for AI clusters (such as creating Oracle or primary/standby tenants, taking over, and stopping a single zone) are now uniformly consolidated into clear error messages to reduce the risk of misoperation.

• Monitoring metric collection and chart display have been adapted and optimized for shared storage mode to avoid abnormal empty data display in charts.

• The LogService cluster supports organization permission management. In a multi-level organizational structure, visibility can be restricted based on permissions.

Product behavior changes

• Main menu structure adjustment: OBProxy, Binlog, and LogService have been merged from separate menus into the "Components" menu.

• The original "Log Service" feature has been renamed "Log Service" due to a naming conflict with the Logservice component.

• The runtime Python version has been upgraded from 2.7 to 3.8. If you use custom alert channel scripts based on Python 2.7 syntax or dependencies, execution failure or behavior changes may occur after the upgrade.

Major bug fixes

OCP V4.5.0 mainly fixes the following issues:

• Fixed the issue where the list does not display after OCP successfully uploads a software package.

• Fixed the issue where monitoring data collection fails due to an abnormal ob_agent process in an OCP task.

• Fixed the issue where OCP cannot recognize an OB software package.

Known issues

None.

Upgrade method

For upgrade methods, refer to Upgrade documentation.

Version usage restrictions

Hardware requirements

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports high-availability deployment across multiple nodes.

The minimum hardware requirements for an OCP-Server node are shown in the following table.

OCP-Agent consumes very few resources and does not have specific hardware requirement for the installation node.

Operating system requirements

The operating system requirements for installing the OCP server (including OCP-Agent) are shown in the following table.

Client requirements

Users typically access OCP services through a web browser. The client requirements are as follows.

If you need to access OCP from a device running iOS, the version requirements are shown in the following table.

For the best user experience, it is recommended to use a display with a resolution greater than 1440 x 810.