The new version of OceanBase Cloud Platform (OCP) primarily upgrades the SQL diagnostics feature and introduces rich capabilities such as primary/standby database decoupling, while also optimizing other features in detail.
V3.3.1
Version information
Version: V3.3.1
Previous version: V3.3.0
Release date: May 24, 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.
Supported OceanBase Database versions
OCP V3.3.1 supports the OceanBase Database versions listed in the following table.
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
VPC feature on the web interface
Added the ECS host type. You can select ECS as the host type when viewing the host list, importing hosts, or creating and scaling OceanBase/OBProxy instances.
The frontend page now displays network attributes for hosts, OceanBase clusters, OBProxy clusters, and other scenarios.
In OceanBase cluster operations and OBProxy cluster operations, you can filter hosts by network type.
Multi-condition alert feature
You can configure alert expressions for multiple monitoring metrics on the command line, supporting the AND and OR relational operators.
The alert details page for multiple monitoring metrics supports displaying charts for those metrics.
When modifying alerts for multiple monitoring metrics on the GUI, a "Cannot edit" message is displayed.
Built-in OAS alert items facilitate seamless integration with OAS.
OAS data query capabilities
Enhanced monitoring query functionality to better support OAS. Supports the following multi-condition expressions and the round function.
= (equal to:)
!
=~ (regular expression match)
!~ (non-regular expression match)
Added kern.log collection for the log trace feature.
Added several monitoring data collections, including io_await and partition_iutil, to meet OAS requirements.
Internationalization documentation
Supports Simplified Chinese and English languages and adapts display effects for different language environments to ensure an international user experience.
Fixed issues
OCP V3.3.1 fixes the following issues:
Fixed the issue where FullGC occurred under high load (20,000 QPS).
Fixed the issue where an error was reported after successfully deleting a sampling strategy during backup recovery.
Fixed the issue where an error was reported during the agent upgrade step when upgrading OCP from V3.2.3 to a higher version on ARM architecture.
Fixed the issue where an error was reported when upgrading ob2230 to ob3230 via OCP V3.3.0.
Fixed the issue where tenant replicas could be modified in a read-only cluster.
Fixed the issue where the NTP service falsely alarmed in a container environment.
Fixed the issue where tenant Primary Zone information was not updated synchronously.
Fixed the issue where a tenant could not be created on ob1479 via OCP.
Fixed the issue where Python alert script templates were outdated.
Fixed the issue where the sys tenant had persistent SlowSQL alerts.
Fixed the issue with alert redirection logic.
Fixed the issue where the sum of response percentages in SQL diagnostics was not 100%.
Fixed some usage issues with SQL diagnostics, monitoring, and alerts under specific circumstances.
Fixed several frontend page interaction issues.
Known Issues
Number |
Known issues |
Workaround |
|---|---|---|
| 1 | The task to create an Oracle tenant failed when the nls_comp parameter was set to ANSI. | This parameter does not affect your business operations temporarily. We recommend that you do not use this parameter when creating a tenant. |
| 2 | During OCP upgrade, the agent was successfully reinstalled, but an error still occurred during the upgrade process. | If your business is not currently affected, you may not need to take any action. |
| 3 | After stopping the observer process in a topology diagram, there is no option to restart it. | If your business is not currently affected, you may not need to take any action. |
Version Limitations
- 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 listed in the following table.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | Available Memory: 16 GB |
| NIC | 10 Gbit/s NIC |
OCP-Agent consumes very few resources and has no specific hardware requirements for the installation node.
- Operating System Requirements
The operating system requirements for installing the OCP server (including OCP-Agent) are listed in the following table.
Server Type |
Operating System |
Supported Versions |
|---|---|---|
| x86_64 | RHEL | 7.2 and later |
| x86_64 | CentOS | 7.2 and later |
| x86_64 | AliOS | 7.2 and later |
| x86_64 | openSUSE | 12 SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
- Client Requirements
Users typically access OCP services through a web browser. The client requirements are as follows.
Browser |
Minimum Version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
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.
V3.3.1 BP
Version Information
Version: V3.3.1 BP
Previous Version: V3.3.1
Release Date: July 8, 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.
New features
The session management page now displays the client port information.
IO statistics are displayed in AWR reports.
Fixed issues
The OCP V3.3.1 BP version fixes the following issues:
The SSH latency information is displayed as undefinedms in the host time during cluster health inspection.
False positive alert for high server CPU system usage.
Query slowdown caused by a large number of SQL IDs generated on the SQL diagnostics page.
The OCP V3.3.1 pom file omitted the ocp-obcloud-service module.
Init timeout caused by the single-thread initialization of OBConnector.