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

OCP V3.3.4

Last Updated：2026-08-03 08:11:18 Updated

The new version of OceanBase Cloud Platform (OCP) introduces several audit events and provides enhancements and optimizations for other features.

Version information

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

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

Operation auditing: Added audit events for stopping a zone, starting a zone, restarting a zone, modifying the deadlock detection switch, deleting a software package, modifying the TopSQL switch for an OceanBase cluster, triggering a major compaction for an OceanBase cluster, clearing the failed major compaction status for an OceanBase cluster, and tenant unit O&M (scaling).
Added a new judgment mode for Suspicious SQL in diagnostics. When PARTITION_CNT is greater than AffectRows, it is listed as Suspicious SQL.
Optimized the standby cluster creation process. The success flag for creating primary and standby clusters has been changed from add standy command successful to Snapshot Access Completed.
Optimized the test alert feature by adding default values for environment variables, improving the success rate of test alerts.
Optimized the pre-check logic for the secondary backup path, prohibiting directories with the same cluster name from existing under the backup path.

OCP V3.3.4 fixes the following issues:

Fixed the typo where the unit for the system variable connect_timeout was incorrectly written as Microseconds instead of Seconds.
Fixed the issue where OCP could not start when flow control was disabled.
Fixed incorrect description of the host IP address in certain alert messages, as well as incorrect descriptions in the tenant list.
Fixed the issue where some unmodifiable parameters were displayed as modifiable in the frontend.
Optimized AWR report generation performance to reduce the frequency of report generation timeouts for tenants with a large number of instances (100+).
Optimized internal table query statements to avoid abnormal cluster status display due to business load.
Improved the fault tolerance of host maintenance operations.
Optimized the Grafana monitoring push logic to avoid data absence.
Optimized the host NTP latency collection method to improve accuracy under high host load conditions.

Number	Known issues	Workaround
1	After backing up data for the second time, the parsed source tenant information does not match expectations when restoring the tenant.	None.
2	The number of transaction logs is 0 in cluster performance monitoring.	None.

OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports multi-node high-availability deployment.

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

Hardware	Requirements
CPU	x86_64, 8-core ARM AArch64 architecture, 8-core
Memory	Available Memory: 16 GB
NIC	10 Gbit/s NIC

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

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

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 listed in the following table.

Operating System	Minimum Version
iOS	10

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