OCP V4.4.0

V4.4.0 BP3

Version information

• Version: V4.4.0 BP3

• Previous version: V4.4.0 BP2

• Release date: December 31, 2025

New features

• Added materialized view analysis capabilities. For regularly refreshed materialized views, a new web interface page is provided to display analysis of their refresh status, including refresh time and latency.
• Optimized the Cgroup configuration logic to ensure stable Cgroup operation and enhance alert notification capabilities in exceptional situations.
• Added adaptive compaction status control (_enable_adaptive_compaction) during cluster upgrade. It is automatically disabled during the upgrade and automatically re-enabled after the upgrade is complete.

Major bug fixes

• Fixed the issue where the ADMIN VIEW role could only view resources under the default organization.
• Fixed the issue of occasional business connection drops (lasting less than 1 minute).

Known issues

V4.4.0 BP2

Version information

• Version: V4.4.0 BP2

• Previous version: V4.4.0 BP1

• Release date: November 24, 2025

New features

• Added two materialized view alert rules: ob_tenant_mview_refresh_delay and ob_tenant_mview_refresh_error, to help users promptly detect materialized view refresh anomalies.
• Supports configuring the timeout period for subtasks of the OCP task engine.

Major bug fixes

Fixed several known issues.

Known issues

V4.4.0 BP1

Version information

• Version: V4.4.0 BP1

• Previous version: V4.4.0

• Release date: November 14, 2025

Major fixes

Fixed some known issues.

Known issues

V4.4.0

OCP V4.4.0 is now available! This release focuses on a comprehensive leap in intelligence, security hardening, and monitoring capabilities, fully empowering enterprise database operations and management.

• Real-time Monitoring

  Supports real-time end-to-end monitoring from OBProxy to OceanBase, then to tenants, hosts, and units, providing 3D visualization and tabular data display. Whether for precise issue localization or dynamic presentation on dashboards, it handles these tasks with ease, offering intuitive support for operational decisions.

• Intelligent Interpretation

  Leveraging a built-in knowledge base and AI assistant, it provides intelligent interpretation for scenarios such as OceanBase log alerts, task errors, and cluster/tenant anomalies. This significantly enhances fault resolution efficiency, helping users quickly locate and resolve issues, thereby reducing the risk of business interruptions.

• Security Capability Upgrade

  • Supports seamless integration with OceanBase TDE (Transparent Data Encryption) and Alibaba Cloud/Tencent Cloud KMS (Key Management Service), ensuring data security and compliance.
  • Supports persisting SQL Audit data to external storage (such as Elasticsearch or Alibaba Cloud SLS), enabling efficient management and analysis of audit logs and further strengthening security governance capabilities.
  • Upgrades underlying infrastructure and fixes over 20 security vulnerabilities.

• 30+ Feature Enhancements and Optimizations

  Conducts deep optimizations in modules such as monitoring and alerting, disaster recovery management, backup and recovery, and plan management, significantly improving operational convenience and ease of use, helping users effortlessly navigate the database operations workflow.

Version information

• Version: V4.4.0

• Previous version: V4.3.6 BP1

• Release date: October 31, 2025

• Supported upgrade path:

  • Currently, only direct upgrades from OCP V3.2.4 and later versions to the current version are supported.

  • For OCP V2.3.x and later, but earlier than V3.2.4, you must first upgrade to OCP V3.3.4.

  • For OCP versions earlier than V2.3.0, you must first upgrade to OCP V2.3.x, then to OCP V3.3.4.

Supported OceanBase Database versions

OCP V4.4.0 supports the following OceanBase Database versions:

• OceanBase V2.2.76 & OceanBase V2.2.77

• OceanBase V3.1.x

• OceanBase V3.2.x

• OceanBase V4.0.x

• OceanBase V4.1.x

• OceanBase V4.2.x

• OceanBase V4.3.x

• OceanBase V4.4.x

Key feature overview

Real-time monitoring

To address the complexity of end-to-end performance monitoring and fault location in distributed database environments, OCP introduces an innovative real-time monitoring solution that covers a five-tier monitoring system: OBProxy > OceanBase cluster > tenant > host > Unit. This solution reshapes the O&M experience through three core capabilities:

• 3D topology visualization, revealing the full architecture: Utilizing a dynamic 3D visualization engine, it presents the logical relationships and physical deployments between OBProxy and clusters, clusters and hosts, and tenants and OBServer nodes in a three-dimensional format. It supports topology hierarchy drilling down from the global architecture to individual Units, intuitively displaying resource distribution and dependencies, making the operational status of distributed architectures, which are often described as "black boxes," transparent.

• Multi-dimensional metric monitoring, second-level exception location: It collects real-time data on over 10 core performance metrics, including QPS, TPS, RT, connection count, CPU/memory usage, etc. Combined with trend analysis of performance monitoring data, it accurately identifies performance inflection points. You can directly view the number of associated alerts on the topology map or navigate to the alert center, enabling one-click tracing from metric anomalies to the root cause of faults, thereby improving fault location efficiency.

• Dual-mode data presentation, meeting multi-dimensional O&M scenarios: It provides structured tabular data views. By complementing graphical and numerical information, it meets managers' needs for global situational awareness while providing technical personnel with data support for in-depth analysis, effectively lowering the cognitive and management barriers for distributed systems.

With the end-to-end real-time monitoring solution, whether for routine O&M, troubleshooting, or dashboard display, users can better manage and optimize system performance, enhancing system stability and reliability.

KMS TDE

The TDE feature of OceanBase Database is a powerful data protection measure designed to ensure the security of data stored on disk. Through an imperceptible encryption mechanism, TDE automatically encrypts data during write operations to storage devices and decrypts it automatically during read operations. This process is completely transparent to users, effectively preventing hackers and malicious users from reading sensitive data from data files, database backups, or disks.

OceanBase's TDE feature uses a two-level key system for encryption and decryption. First, the minimum granularity for encryption is a table within a database, but the table must be located in an encrypted tablespace. A tablespace can be understood as a collection of tables and is a concept designed by OceanBase to be compatible with Oracle Database. The encryption unit of a tablespace means that each encrypted tablespace is configured with a specific encryption algorithm and corresponding data keys for encrypting the data within that tablespace. Furthermore, each tenant has a master key, which is used to encrypt the data keys of the tablespaces. To prevent unauthorized decryption, the master key is typically stored in a dedicated Keystore.

KMS supports a series of management functions for keys, including generation, storage, backup, recovery, and destruction. Through KMS, users can easily manage access permissions for their digital assets, ensuring that only authorized users can access specific data resources. Additionally, KMS helps users avoid security risks associated with key loss or forgetting.

To unify key management, OCP acts as a proxy for KMS services, providing a unified key management service and interface, thereby shielding OceanBase from differences between KMS services from different cloud vendors. Users only need to provide the access domain name, AK, SK, and master key ID from vendors such as Alibaba Cloud or Tencent Cloud to easily enable the KMS TDE feature for their tenant.

New features

Basic O&M

1. Cluster Management: During cluster upgrade, a prompt is automatically displayed if the dynamic partitioning feature is enabled, avoiding business impact or interruption due to DDL operation restrictions during the upgrade. Supported OceanBase versions: [V4.2.5 BP2, +∞).
2. Cluster Management: If a host is detected as not supporting the AVX instruction set during OceanBase installation, deployment, or upgrade, the related operation is automatically stopped to avoid potential compatibility issues. Supported OceanBase versions: [V4.2.5, V4.2.5 BP2), [4.3.5, 4.3.5 BP4).
3. Cluster Management: Displays primary/standby, major compaction, and data backup information at the tenant level, allowing users to quickly understand the current status of the cluster.
4. Tenant Management: Supports setting the ob_compatibility_control variable when creating a MySQL-compatible tenant. Supported OceanBase versions: [V4.2.3, V4.3.0), [V4.3.2, V4.3.5 BP3).
5. Tenant Management: Supports customizing the tenant connection string, facilitating access to the database from different domains.
6. Tenant Management: Grants users the Create routine privilege in MySQL-compatible tenants. Supported OceanBase versions: [V4.2.2, V4.3.0), [V4.3.1, +∞).

Monitoring and Alerts

1. Supports alerts for the Synchronization Status (SYNCHRONIZATION_STATUS) of primary/standby clusters in OceanBase V2.x/V3.x.
2. Added 8 tenant-level monitoring metrics: MemStore Read Lock Request Success Rate, MemStore Write Lock Request Success Rate, RPC Request Success Rate, GTS Requests, Transaction Rollback Ratio, Fuse Row Cache Hit Rate, Schema Cache Hit Rate, and Temporary Page Cache Hit Rate.
3. Added 2 cluster-level monitoring metrics: RPC Network Latency Within the Sampling Period and RPC Delivery Failure Within the Sampling Period.
4. Supports displaying the maximum value, average value, and current value of monitoring metrics within the OBProxy cluster monitoring time range.

Disaster Recovery Management

1. Standby tenants in disaster recovery scenarios such as one-primary-multiple-standbys and cascading support free switching of the synchronization source, facilitating users to conduct geo-failover drills.
2. When creating a standby tenant (with archiving-based primary/standby synchronization), the recovery point of the standby tenant can be controlled using the parameter ocp.standby.tenant_restore_advance.seconds (default value is the current time minus 60 seconds).
3. The tenant overview page supports displaying the primary/standby relationship of a tenant.

Plan Management

1. For a primary/standby tenant pair with the same service name, supports automatic traffic failover from the standby tenant to the primary tenant when the standby tenant's service fails.
2. Supports automatic restart of the Binlog Process (OBM) after a crash, effective only once within 30 minutes.

Binlog Management

Supports setting the Clog parsing start point via a timestamp when creating a Binlog instance, facilitating on-demand subscription by downstream systems.

Backup and Recovery

1. Supports enabling/disabling the dynamic partition feature during full recovery based on actual business conditions, preventing partition data loss caused by this feature. Supported OceanBase versions: [V4.3.5 BP2, +∞).
2. Supports quick tenant recovery: The recovered tenant is in read-only mode and does not support major compaction or data backup. Supported OceanBase versions: [V4.3.3, +∞).
3. Supports default skipping of locked tenants during backups under cluster-level backup policies.
4. Supports setting advanced options for object storage types compatible with the S3 protocol:
   • delete_mode=delete (default)/tagging, supported OceanBase versions: [V4.2.3.0, V4.2.5.0), [V4.3.0, +∞).
   • checksum_type=md5 (default)/crc32, supported OceanBase versions: [V4.2.1.6, V4.2.2.0), [V4.2.3.0, +∞).
   • addressing_model=virtual_hosted_style (default)/path_style, supported OceanBase versions: [V4.2.1.9, V4.2.2.0), [V4.2.5.1, V4.3.0.0), [V4.3.5.0, +∞).

Product Optimization

Cluster Management

1. Added visual displays for remaining CPU, memory, log disk, and data disk space on the Resource Management tab, helping users monitor resource usage in real time and improving operational efficiency.
2. When a Zone within a cluster has only one OBServer node and that node holds replicas, reinstallation of the OBServer node is not allowed.

Tenant Management

Tenant specifications now support search by unit specification name, addressing the query efficiency issue when there are many tenant specification names.

Host Management

The operation column in the host list supports viewing standardized host reports.

Backup and Recovery

1. The sys tenant, as a system management tenant, does not support the backup and recovery feature. Its backup and recovery page has been removed to avoid user confusion and misoperation. Supported OceanBase versions: [V4.0, +∞).
2. When recovering a tenant, users can now independently choose the operation path: they can either go to the Task Center to view task progress or stay on the recovery initiation page to continue operations.

Other

1. AI Assistant: In business scenarios where large language models are not configured, it provides general dialogue capabilities and implements document search functionality.
2. Removed the character limit for tag display on the cluster, tenant, OBProxy, and host detail pages.
3. Operation Audit: Supports displaying the client IP address used to access the database.

Product Behavior Changes

1. Changes in Tencent Cloud COS product behavior may cause abnormal database log backups. It is recommended to use the S3 protocol instead of COS. Supported OceanBase versions: [V4.2.1.9, V4.2.2), [V4.2.5.0, V4.3.0), [V4.3.3.0, V4.4.0). OceanBase V4.4.0 and later versions no longer support the COS protocol.
2. Removed the exclusive host restriction for the Binlog service, allowing multiple products to share the same host (only recommended for test environments), effectively reducing deployment and operational costs.

Major Bug Fixes

OCP V4.4.0 primarily fixes the following issues:

• Fixed the issue where the database username drop-down list was empty when a Metadb tenant was selected as the MetaDB and the tenant's credentials were entered during Binlog cluster creation.
• Fixed the issue where the parameter version of an OBProxy cluster was displayed incorrectly after a task to modify OBProxy cluster parameters failed and the task was successfully rolled back.
• Fixed the issue where viewing task details would redirect to the OCP homepage.
• Fixed the issue where an error indicating a full thread pool occurred when importing credentials.
• Optimized permission control for tenant read-only accounts in the statistics module.
• Fixed the issue where a user credential could not be recreated after being deleted on the GUI.
• Fixed the issue where the inspection result for the "NFS mount parameter check" item was inaccurate during a basic inspection.
• Fixed the issue where some tenants reported the "OB_TENANT_NOT_EXIST" error during OCP spot-check recovery.
• Fixed the issue where pagination was unavailable for link queries.
• Fixed the issue where a gap in the primary/standby OCP upgrade process affected data table connections.

Known issues

Version usage limitations

Hardware requirements

OCP-Server can be installed on a physical server or run in a Docker container. OCP-Server supports high-availability deployment across multiple nodes.

The minimum hardware requirements for an OCP-Server node are listed in the following table.

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

Operating system requirements

The operating system requirements for installing the OCP server (including OCP-Agent) are listed in the following table.

Client requirements

Users typically access OCP services through a web browser. The client requirements are as follows.

If you need to access OCP from a device running iOS, the version requirements are listed in the following table.

For the best user experience, we recommend using a display with a resolution greater than 1440 × 810.