OceanBase Cloud Platform (OCP) V3.1.2 introduces the Active Session History (ASH) report, a new feature in the Performance Diagnostics module. This feature provides historical information about active database sessions, aiding users in diagnosing tenant performance. The backup and restore feature now supports secondary backups. Additionally, the visual content for users with different permissions in OCP has been optimized to ensure a more intuitive experience. The system also includes the ability to take over OBProxy, ensuring the completeness of the takeover process. Other features have been optimized and enhanced, with the SQL diagnostics section now offering an export function for easier issue analysis.
Version information
Version: V3.1.2
Previous version: V3.1.1
Version release date: September 29, 2021
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.
Supported OceanBase Database versions
OceanBase Cloud V3.1.2 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
You can generate and download an active session history report.
An active session history report is part of the tenant performance diagnostics feature. It samples data from views such as those related to SQL, sessions, wait events, and system statistics to provide historical active session information. For more information, see Manage an active session history report.
You can perform a secondary backup.
A secondary backup allows you to archive backup files to other locations. The backup files include baseline data and archived logs. Performing a secondary backup reduces the storage pressure on backup files. For more information, see the following topics:
The visibility of different users with different privileges is optimized.
The entry is hidden for users without the corresponding privileges to simplify the product path visible to users and reduce invalid clicks.
You can take over an OBProxy cluster.
This feature improves the takeover process. After you take over an OceanBase cluster, you can also take over the corresponding OBProxy cluster to OCP. For more information, see Take over an OBProxy cluster.
In multi-zone mode, OCP supports GUI-based management.
In multi-zone mode, you can control the priority of accessing targets within the same zone when OceanBase Database, OCP, or OBProxy is deployed across IDCs or cities. Multi-zone mode reduces the latency of links and the bandwidth costs across IDCs or cities. For more information, see Overview.
OCP supports the following operations in multi-zone mode:
View details about each zone, including the IDCs in the zone and the corresponding OCP. For more information, see View details about zones.
View or modify multi-zone parameters. For more information, see Manage multi-zone parameters.
Feature enhancements
The SQL diagnostics feature is optimized. You can export TopSQL, suspicious SQL, and SlowSQL.
The cluster and tenant performance monitoring feature is optimized. You can disable the collection of cluster and tenant performance metrics.
The memory usage of monitoring data collection is optimized. This ensures the performance of OCP when the number of hosts managed by OCP increases.
Fixed issues
OceanBase Cloud V3.1.2 fixes the following issues:
The statistics of remote plans and distributed plans are inaccurate in the SQL diagnostics feature.
After the ob_host_log_disk_percent_over_threshold alarm is reported, it automatically recovers without continuous reporting if the issue is not resolved.
The downloaded logs of an OBProxy cluster cannot be decompressed when you download them through OCP.
After OCP is upgraded, the creation time of a tenant is reset to the time when OCP is upgraded.
TopSQL contains data without SQL text.
When you modify OBProxy parameters through OCP, some parameters cannot be modified or cannot be modified to values in a specific range.
When you modify the recyclebin parameter of a tenant to ON through OCP, the modification does not take effect.
For a partitioned table with two datetime fields, if only one field is used for partitioning, the System Management page's Inspection feature cannot inspect the table.
After a primary-standby disaster recovery switch of an OceanBase cluster, the primary-standby relationship no longer exists, but the cluster is still displayed as a primary-standby cluster in the cluster list.
Known issues
No. |
Known issue |
Workaround |
|---|---|---|
| 1 | An error "Exception occurs during backup file parsing" is returned when you restore a backup. | Set the system parameter ocp.backup.restore-time-pre-check.enabled to false. |
| 2 | After OceanBase standby cluster creation fails across OCPs and the rollback succeeds, the Cluster page of OCP still displays the information about the failed OceanBase standby cluster. | This does not affect the usage. No workaround is required. |
| 3 | When you filter by inspection object on the Scheduling History of Data Backup tab of System Management > Inspection, the filter does not take effect. | Currently, the only inspection object is cluster. No filter is required. |
| 4 | Physical backup is displayed as completed on the Scheduling History of Data Backup page, but the Backup & Recovery page of the cluster displays the Pending Backup Scheduling status. | This issue occurs only during the first physical backup. Subsequent backup scheduling is normal, and does not affect the business. |
| 5 | The final directory is not created for the storage path of the secondary backup of the OSS type on the OBServer node, but the Test test on OCP is performed on the full path. | The secondary backup storage path in OCP does not support the OSS type in this release. |
| 6 | When you initiate a major compaction on OceanBase V1.4.7x in OCP, the Frozen Version and Broadcasted Version displayed on the Compaction Management page are inconsistent. | OceanBase V1.4.7x is not supported in this version. It will be supported in later versions. |
| 7 | After a subtask succeeds in cross-OCP primary-standby database upgrade, the parent task keeps waiting until it times out and fails. | Retry the parent task. |
| 8 | When you take over an OceanBase primary cluster with the same name that is being created in OCP, no pre-check is performed. | Manually check whether an OceanBase primary cluster with the same name is being created before taking over. |
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 minimum hardware requirements for OCP-Server nodes are as follows:
Hardware |
Requirement |
|---|---|
| CPU | |
| Memory | 16 GB available memory |
| NIC | 10 Gbps NIC |
OCP-Agent consumes very little resources and has no special hardware requirements.
Operating system requirements
The following table lists the operating system requirements for installing OCP-Server (including OCP-Agent).
Server type |
Operating system |
Supported version |
|---|---|---|
| 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
General users access OCP through a web browser. The following table lists the client requirements.
Browser |
Minimum version |
|---|---|
| Chrome | 81 |
| Firefox | 64 |
| Safari | 10 |
| Edge | 13 |
If you need to access OCP 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 that you use a display with a resolution greater than 1440 x 810.