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

OCP V3.3.4

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

#RNDate#2022-10-21

OceanBase Cloud Platform (OCP) has been upgraded to support more audit events and other features have been optimized.

Version information

Version: V3.3.4
Previous version: V3.3.3
Version 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, you must first upgrade to V2.3.x and then to this version.

OCP V3.3.4 supports the following OceanBase Database versions:

Operation audit: added audit events, including stopping a zone, starting a zone, restarting a zone, modifying the deadlock detection switch, deleting a software package, modifying the OceanBase cluster TopSQL switch, triggering an OceanBase cluster major compaction, clearing the OceanBase cluster major compaction failure status, and tenant unit maintenance (scaling in/out).
In the Suspicious SQL section of the diagnostics, a new judgment mode is added. If the value of PARTITION_CNT is greater than AffectRows, it is marked as Suspicious SQL.
Optimized the standby cluster creation process. The success flag of the primary and standby cluster creation is adjusted from the original add standby command success to snapshot access completed.
Optimized the test alert feature by adding default values for environment variables to improve the success rate of test alerts.
Optimized the pre-check logic for the secondary backup path to prohibit the existence of directories with the same cluster name under the backup path.

OCP V3.3.4 fixes 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 start when the flow control was disabled.
Fixed the issue where the host IP address description in an alert message was incorrect, and the tenant list description was incorrect.
Fixed the issue where some parameters that cannot be modified were displayed as modifiable in the frontend.
Optimized the performance of AWR report generation to reduce the frequency of report generation timeouts when the number of tenants exceeds 100.
Optimized internal table query statements to avoid abnormal cluster status display due to business pressure.
Optimized the fault tolerance of host maintenance operations.
Optimized the Grafana monitoring push logic to avoid situations where no data is displayed.
Optimized the NTP delay collection method for hosts to improve accuracy under high load conditions.

No.	Known issue	Workaround
1	After secondary backup, the source tenant information parsed during tenant recovery does not meet expectations.	N/A
2	The number of transaction logs is 0 in cluster performance monitoring.	N/A

OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports multi-node high availability deployment.

The minimum hardware requirements for OCP-Server nodes are as follows:

Hardware	Requirements
CPU	X86_64, 8 cores ARM aarch 64 architecture, 8 cores
Memory	16 GB of available memory
Network card	10 GbE

OCP-Agent consumes very few resources and has no special hardware requirements for the installation node.

The operating system requirements for installing OCP Server (including OCP-Agent) are as follows:

General users access OCP services through web browsers, so the client requirements are as follows:

If you need to access OCP services from an iOS device, the minimum operating system version is as follows:

Operating system	Minimum version
iOS	10

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