OceanBase Cloud Platform (OCP) V3.1.2 introduces the Active Session History report, a new feature in the Performance Diagnostics module. It provides historical active session information for the database to assist users in tenant performance diagnostics. This version also supports secondary backup for backup and recovery operations. Additionally, the visual content for users with different permissions in OCP has been optimized to achieve what you see is what you get. The feature to take over OBProxy has been added, ensuring the integrity of the takeover link. Furthermore, other features have been optimized and strengthened. An export function has been added to the SQL diagnostics section, making it convenient for you to download and analyze issues.
Version information
Version: V3.1.2
Previous version: V3.1.1
Release date: September 29, 2021
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 upgrade to this version.
Supported OceanBase Database versions
OceanBase Cloud Platform V3.1.2 supports the following versions of OceanBase Database:
OceanBase V1.4.x
OceanBase V2.1.x
OceanBase V2.2.x
OceanBase V3.1.x
OceanBase V3.2.x
New features
Supports generating and downloading the Active Session History report.
As part of the tenant performance diagnostics feature, the Active Session History report samples data from related views such as SQL, sessions, wait events, and system statistics to help users view historical active session information for the database.
Backup and recovery now supports secondary backup.
Secondary backup provides the ability to archive backup files to other locations, including baseline data and archived logs. Supporting secondary backup reduces storage pressure on backup files.
Optimized the visibility for users with different permissions in OCP.
Blocked the entry for users without the permission, simplified the visible product path, and reduced unnecessary clicks for users.
Supports taking over OBProxy.
This feature improves the takeover process to some extent. After taking over an OceanBase cluster, you can also take over its corresponding OBProxy cluster in OCP.
For multi-zone mode, OCP supports GUI-based management.
Multi-zone mode is designed for OceanBase, OCP, or OBProxy deployments across data centers or cities, allowing priority access to targets within the current zone. It effectively reduces latency and lowers cross-IDC or cross-city bandwidth costs.
OCP management of multi-zones supports:
Viewing detailed information about each zone, including the IDCs it contains and the OCP instance corresponding to each zone.
Viewing or modifying multi-zone parameters.
Feature enhancements
Optimized the SQL diagnostics feature by adding the ability to export TopSQL, suspicious SQL, and SlowSQL.
Optimized the cluster and tenant performance monitoring features by adding prompts when the collection of cluster or tenant performance metrics is disabled.
Optimized memory usage for monitoring collection, ensuring OCP maintains performance as it manages more hosts.
Bug fixes
OceanBase Cloud Platform V3.1.2 fixes the following issues:
Inaccurate statistics for remote plans and distributed plans in the SQL diagnostics feature.
The ob_host_log_disk_percent_over_threshold alert automatically recovered after being reported for a period without resolving the issue, failing to continue alerting.
Logs containing the OBProxy type could not be decompressed when downloaded through OCP.
After OCP upgrade, a tenant's creation time was reset to the OCP upgrade time.
TopSQL contained data without SQL text.
When modifying OBProxy parameters via OCP, some parameters could not be modified or could not be set to certain value ranges.
Setting the tenant parameter recyclebin to ON via OCP did not take effect.
For a partitioned table with two DATETIME fields, if only one field was used for primary partitioning, the Inspection option under System Management could not find this table.
After a primary/standby disaster recovery switchover in an OceanBase cluster, the primary/standby relationship no longer existed, but it was still displayed as such in the cluster list.
Known issues
Number |
Known issues |
Workaround |
|---|---|---|
| 1 | An error "Exception occurred while parsing the backup file" is reported during backup and restore. | Set the system parameter ocp.backup_restore-time-pre-check.enabled to false. |
| 2 | After a rollback is performed following a failed cross-OCP creation of an OceanBase standby cluster, the rollback succeeds, but the information about the failed-to-create OceanBase standby cluster still appears on the Clusters page of OCP. | This does not affect usage and is not being circumvented for now. |
| 3 | On the Inspection Script tab of the System Management > Inspection page, filtering by inspection object does not take effect. | Currently, the inspection object is only the cluster. No filtering or avoidance of inspection objects is required. |
| 4 | A physical backup may appear as completed in the Data Backup Scheduling History section, but its status in the Backup and Recovery section of the cluster dashboard still shows Waiting for Backup Scheduling. | This issue only occurs on the first physical backup. Subsequent backups are scheduled normally and do not affect business operations temporarily, so it may not be necessary to avoid it. |
| 5 | On the OBServer node side, the final directory for the secondary backup storage path of the OSS type is not created. However, the Test test in OCP verifies the full path. | The secondary backup storage path for this release of OCP is temporarily set to not support the OSS type. |
| 6 | A major compaction is initiated for OceanBase Database V1.4.7x in OCP, but the Frozen Version and Broadcast Version displayed on the Compaction Management page are inconsistent. | The current version is not compatible with OceanBase Database V1.4.7x. Compatibility will be provided in later versions. |
| 7 | During a cross-OCP primary-standby database upgrade, the parent task waits indefinitely until it times out and fails after all subtasks have succeeded. | Retry in the parent task. |
| 8 | The OceanBase primary cluster in OCP is being created. Taking over an OceanBase primary cluster with the same name was not detected during the precheck. | Before taking over, manually check whether an OceanBase primary cluster with the same name is being created. |
Version usage restrictions
Hardware requirements
OCP-Server can be installed on physical servers or run in Docker containers. OCP-Server supports high-availability deployment with multiple nodes.
The following table describes the minimum hardware requirements for an OCP-Server node.
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 following table describes the operating system requirements for installing the OCP server (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 | 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 as follows.
Operating System |
Minimum Version |
|---|---|
| iOS | 10 |
For the best user experience, we recommend using a display with a resolution greater than 1440 × 810.