OCP V3.1.2

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 active session information for databases, aiding users in tenant performance diagnostics. The backup and restore feature now supports secondary backups. Additionally, the visualization content for users with different permissions in OCP has been optimized to ensure a more intuitive user experience. The new feature for taking over OBProxy ensures a complete takeover process. Other features have also been optimized and enhanced, with the addition of an export function in the SQL diagnostics section for convenient problem analysis.

Version information

• Version: V3.1.2

• Previous version: V3.1.1

• Version release date: September 29, 2021

• Supported upgrade path: You can directly upgrade OCP V2.3.x and later to this version. If you are using OCP V2.3.0 or earlier, you must first upgrade to V2.3.x before upgrading 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 SQL, session, wait event, and system statistics to provide users with historical active session information. For more information, see Manage active session history reports.

• You can perform secondary backup.

  Secondary backup allows you to archive backup files, including baseline data and archived logs, to other locations. This feature reduces the storage pressure on backup files. For more information, see the following topics:

  • Overview of backup and restore for information about Second Backup.

  • Create a backup strategy for information about how to use secondary backup.

• The visibility of different users with different permissions is optimized.

  The entry is hidden for users without the corresponding permissions. This simplifies the product path visible to users and reduces 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.

  Multi-zone mode allows you to control the priority of accessing targets within the same zone when OceanBase Database, OCP, or OBProxy is deployed across IDCs or cities. This mode reduces latency and bandwidth costs across IDCs or cities. For more information, see Overview of multi-zone mode.

  OCP supports the following operations in multi-zone mode:

  • View the details of each zone, including the IDCs in each zone and the corresponding OCP. For more information, see View multi-zone information.

  • View or modify multi-zone parameters. For more information, see Manage multi-zone parameters.

Feature enhancements

• The SQL diagnostics feature is optimized. You can now export TopSQL, suspicious SQL, and SlowSQL.

• The cluster and tenant performance monitoring features are optimized. You can now disable the collection of cluster and tenant performance metrics.

• The memory usage of monitoring data collection is optimized. This ensures the performance of OCP as the number of hosts it manages increases.

Fixed issues

OceanBase Cloud V3.1.2 fixes the following issues:

• The statistics of remote plans and distributed plans in the SQL diagnostics feature are inaccurate.

• The ob_host_log_disk_percent_over_threshold alert is automatically recovered after a period of time without being continuously reported when the issue is not resolved.

• The downloaded logs that contain OBProxy logs cannot be decompressed.

• After OCP is upgraded, the creation time of a tenant is reset to the time when OCP is upgraded.

• The TopSQL feature contains data without SQL text.

• When you modify the parameters of an OBProxy cluster by using OCP, some parameters cannot be modified or cannot be modified to certain values.

• When you modify the recyclebin parameter of a tenant to ON by using OCP, the modification does not take effect.

• For a partitioned table with two datetime fields, only one field is partitioned. The System Management > Inspection feature cannot inspect this table.

• After a primary-standby disaster recovery switch is performed for 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

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:

OCP-Agent consumes very few resources and has no special requirements for the hardware resources of the installation node.

Operating system requirements

The following table lists the operating systems supported for installing OCP-Server and OCP-Agent.

Client requirements

General users access OCP through a web browser. The following table lists the minimum browser versions required.

If you want to access OCP from an iOS device, the minimum operating system version is as follows:

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