OCP V3.3.4|V4.3.5|OceanBase Cloud Platform|OCP docs|Distributed Database

OCP V3.3.4

Last Updated：2026-08-05 09:46:02 Updated

#RNDate#2022-10-21

OceanBase Cloud Platform (OCP) of this version has added audit events and optimized the other features.

Version information

Version number: V3.3.4
Previous version: V3.3.3
Release date: October 21, 2022
Supported upgrade path: OCP V2.3.x and later versions can be directly upgraded to this version. For OCP versions earlier than V2.3.0, first upgrade to V2.3.x and then to this version.

OCP V3.3.4 supports OceanBase Database of the following versions:

Added audit events for operation auditing: stop zone, start zone, restart zone, modify deadlock detection switch, delete software package, modify OceanBase cluster Top SQL switch, trigger OceanBase cluster merge, clear OceanBase cluster merge failure state, tenant unit operation (expansion/shrinkage).
Added a new judgment mode for Suspicious SQL in diagnosis. When the value of PARTITION_CNT is greater than that of AffectRows, it is marked as Suspicious SQL.
Optimized the process for creating a standby cluster. The success indicator changed from the original add standy command success to snapshot access completed.
Optimized the test alert feature by adding default values for environment variables to improve test alert success rate.
Optimized the pre-check logic for the backup path to prohibit the existence of directories with the same cluster name.

OCP V3.3.4 fixed the following issues:

Fixed the issue where the unit of the system variable connect_timeout was incorrectly written as Microseconds instead of Seconds.
Fixed the issue where OCP could not be started when traffic control is disabled.
Fixed the issue where the host IP address was incorrectly described in the alert message and the tenant list was incorrectly described.
Fixed the issue where certain unmodifiable parameters were displayed as modifiable on the frontend.
Optimized the performance of AWR report generation to reduce the frequency of timeout when the number of tenants exceeds 100.
Optimized internal table query statements to prevent cluster status from being displayed abnormally due to business pressure.
Enhanced the fault tolerance of host operations.
Optimized the logic for pushing monitoring data in Grafana to avoid cases where no data is displayed.
Optimized the NTP delay collection method for hosts to improve accuracy under high load.

ID	Known issue	Workaround
1	After a secondary backup, the source tenant information parsed during tenant restore does not match expectations.	None.
2	The number of transaction logs is 0 in cluster performance monitoring.	None.

OCP-Server can be installed on a physical server or in a Docker container and supports a multi-node highly available deployment model.

The minimum hardware requirements for an OCP-Server node are as follows.

Hardware	Requirements
CPU	X86_64, 8-core ARM aarch 64 architecture, 8-core
Memory	16 GB of available memory
NIC	10 Gigabit Ethernet interface

OCP-Agent has minimal resource requirements and does not impose special hardware requirements on the installation node.

The operating systems supported for installing the OCP service end (including OCP-Agent) are as follows:

General users typically access OCP service through a web browser. The client requirements are as follows.

If you need to access OCP from iOS devices, the supported versions are as follows.

Operating system	Minimum version
iOS	10

For the best user experience, we recommend using a monitor with a resolution greater than 1440 x 810.