OCP V3.1.2

#RNDate#2021-07-13

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. In this version, backup and restore support secondary backups. Additionally, the visualization content for users with different permissions in OCP has been optimized to ensure a more intuitive user experience. A new feature for taking over OBProxy has been added, ensuring the completeness of the takeover process. Other features have also been optimized and enhanced, including the addition of an export function in the SQL diagnostics section, making it easier for you to download and analyze issues.

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 OCP 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, as part of the tenant performance diagnostics feature, samples data from views such as SQL, session, wait event, and system statistics to help you view historical active session information of the database. For more information, see Manage an active session history report.

• You can perform secondary backup.

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

  • What is secondary backup? for more information about secondary backup.

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

• You can optimize the visibility of different users with different permissions in OCP.

  This feature hides the entry for users without the required permissions and simplifies the product path visible to users, reducing 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.

• You can manage multi-zone deployment in OCP.

  In multi-zone deployment, you can control the priority of accessing targets within the same zone when OceanBase, OCP, or OBProxy is deployed across IDCs or cities. This feature reduces network latency and bandwidth costs across IDCs or cities. For more information, see Overview.

  OCP supports the following multi-zone management features:

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

  • You can 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 slow SQL.

• The cluster and tenant performance monitoring features are 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 as the number of hosts it manages increases.

Fixed issues

OceanBase Cloud V3.1.2 fixes the following issues:

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

• The ob_host_log_disk_percent_over_threshold alert is automatically resolved 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 upgrade time.

• The TopSQL feature contains data without SQL text.

• Some OBProxy parameters cannot be modified or cannot be modified to certain values in OCP.

• The recyclebin parameter of a tenant cannot be set to ON in OCP.

• For a partitioned table with two datetime fields, only one of the fields is partitioned. The System Management page's Inspection feature cannot inspect this table.

• After the primary-standby disaster recovery of an OceanBase cluster is switched, 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 high availability deployment across multiple nodes.

The following table lists the minimum hardware requirements for OCP-Server nodes.

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

Operating system requirements

The following table lists the operating systems that are supported for installing OCP Server (including OCP-Agent).

Client requirements

General users usually access OCP services through a Web browser. Therefore, the following table lists the client requirements.

If you need to access OCP services on an iOS device, the following table lists the requirements on the operating system.

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