OceanBase Cloud Platform (OCP) is upgraded to support SQL diagnostics and provides features such as decoupling of primary and standby databases. Other features are also optimized.
V3.3.1
Version information
Version: V3.3.1
Previous version: V3.3.0
Version release date: May 24, 2022
Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. For OCP versions earlier than 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 following OceanBase Database versions:
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
GUI VPC feature
Added the ECS type to the host type. You can select the ECS type for hosts in the host list, when you import a host, or when you create or scale out an OceanBase cluster or an OBProxy cluster.
Added the network attribute to the frontend page in scenarios such as host, OceanBase cluster, and OBProxy cluster.
Added the ability to filter hosts by network type in the maintenance of an OceanBase cluster or an OBProxy cluster.
Multi-condition alert feature
You can configure multiple alert expressions for multiple monitoring metrics on the CLI. The expressions support the and and or operators.
You can display multiple monitoring metric charts on the details page of an alert for multiple monitoring metrics.
When you modify an alert for multiple monitoring metrics on the GUI, a prompt is displayed indicating that the alert cannot be modified.
The OAS alert items are integrated into OCP. This makes it easy to seamlessly integrate OAS with OCP.
OAS data query capability
Enhanced the monitoring query feature to better support OAS. The following multi-condition expressions and the round function are supported:
= (equivalent to:)
!=
=~ (regular expression match)
!~ (non-regular expression match)
Added the collection of kern.log logs to the log trace feature.
Added the collection of several monitoring data items, including io_await and partition_iutil, to meet the requirements of OAS.
Internationalization
OCP supports Chinese and English. It is adapted to different language environments to ensure an internationalization experience.
Fixed issues
OCP V3.3.1 fixes the following issues:
The FullGC issue occurs under high pressure (20000 QPS).
The error is reported after the sampling strategy is deleted during backup and restore.
The agent upgrade step fails when OCP V3.2.3 is upgraded to a later version on an ARM server.
The error is reported when OCP V3.3.0 is used to upgrade ob2230 to ob3230.
The issue that the read-only cluster can modify tenant replicas.
Fixed the false alert issue of the NTP service in a container environment.
Fixed the issue that the Primary Zone information of a tenant is not updated.
Fixed the issue that a tenant cannot be created on ob1479 through OCP.
Fixed the issue that the Python alert script template is outdated.
Fixed the issue that the SlowSQL alert of the sys tenant exists for a long time.
Fixed the issue that the alert redirection logic is incorrect.
Fixed the issue that the sum of the response ratios in SQL diagnostics is not 100%.
Fixed other issues in SQL diagnostics, monitoring, and alerts under specific conditions.
Fixed some frontend page interaction issues.
Known issues
No. |
Known issue |
Workaround |
|---|---|---|
| 1 | The task to create an Oracle tenant fails when the nls_comp parameter is set to A NSI. | This issue does not affect business operations. We recommend that you do not use this parameter when you create a tenant. |
| 2 | The agent is reinstalled during OCP upgrade, but the upgrade process still reports an error. | This issue does not affect business operations. You can ignore it. |
| 3 | After you stop the observer process in the topology, no option is provided to restart the process. | This issue does not affect business operations. You can ignore it. |
Limitations
- Hardware requirements
OCP-Server can be installed on a physical server or in a Docker container. OCP-Server supports multi-node high availability deployment.
The following table describes the minimum hardware requirements for OCP-Server.
Hardware |
Requirements |
|---|---|
| CPU | |
| Memory | 16 GB available memory |
| NIC | 10 GbE NIC |
OCP-Agent consumes little resources and has no special hardware requirements.
- Operating system requirements
The following table describes the operating system requirements for installing OCP (including OCP-Agent).
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 | 12SP3 and later |
| ARM aarch64 | AliOS | 7.2 and later |
| ARM aarch64 | NeoKylin | 7.6 |
| ARM aarch64 | Huawei EulerOS | 2.0 SP8 |
- Client requirements
Most users access OCP through a web browser. The following table describes the browser requirements.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you want to access OCP on an iOS device, the following table describes the operating system requirements.
Operating system |
Minimum version |
|---|---|
| iOS | 10 |
We recommend that you use a display with a resolution greater than 1440 x 810 for the best experience.
V3.3.1 BP
Version information
Version: V3.3.1 BP
Previous version: V3.3.1
Version release date: July 8, 2022
Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. For OCP versions earlier than V2.3.0, you must first upgrade to V2.3.x and then to this version.
New features
Added the client port information to the session management page.
Added the I/O statistics to the AWR report.
Fixed issues
OCP V3.3.1 BP fixes the following issues:
The SSH latency information is displayed as undefinedms in the host time of the cluster health check.
The false alert issue of the high system CPU usage rate.
The issue that a large number of SQL IDs are generated on the SQL diagnostics page, causing slow queries.
The issue that the ocp-obcloud-service module is missing in the pom file of OCP V3.3.1.
The issue that the init timeout is caused by the single-threaded initialization of OBConnector.