OCP V3.3.4|V4.3.6|OceanBase Cloud Platform|docs|OceanBase Documentations

OCP V3.3.4

Last Updated：2026-09-04 02:16:36 Updated

OceanBase Cloud Platform (OCP) introduces new audit events and enhances existing features in this release.

Version information

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

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

In operation audit: Added audit events, including stopping a zone, starting a zone, restarting a zone, modifying the dead lock detection switch, deleting a software package, modifying the OceanBase cluster's TopSQL switch, triggering OceanBase cluster compaction, clearing the failed state of OceanBase cluster compaction, and tenant unit maintenance (scale-in/scale-out).
In diagnostics, Suspicious SQL increases a new judgment mode, which lists Suspicious SQL when the PARTITION_CNT is greater than AffectRows.
Optimized the secondary backup creation process, changing the success flag from "add standby command success" to "snapshot access complete".
Optimized the test alert feature, adding default values to environment variables to improve test alert success rates.
Optimized the secondary backup path pre-check logic, prohibiting the backup path from containing directories with the same cluster name.

OCP V3.3.4 fixes the following issues:

Fixed the error in the unit of the system variable connect_timeout Seconds mistakenly written as Microseconds.
Fixed the issue where OCP fails to start when the traffic control is disabled.
Fixed the errors in the host IP description and tenant list description for a specific alert message.
Fixed the issue where some parameters that cannot be modified are 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 the internal table query statements to avoid abnormal cluster status display caused by business pressure.
Optimized the fault tolerance of host maintenance operations.
Optimized the Grafana monitoring push logic to avoid situations with no data.
Optimized the NTP delay collection method for hosts to improve accuracy under high load.

Issue ID	Description	Resolution
1	After a secondary backup, the information of the original tenant parsed during tenant restoration is inconsistent with expectations.	No solution available.
2	The number of transaction logs in the cluster performance monitoring is 0.	No solution available.

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

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

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

OCP-Agent consumes minimal resources and does not have specific hardware requirements.

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

General users access OCP through web browsers. The client requirements are as follows:

For iOS-based devices, the minimum operating system requirements are as follows:

Operating system	Minimum version
iOS	10

For optimal performance, it is recommended to use a display with a resolution greater than 1440 x 810.