OCP V4.3.6

V4.3.6 BP2

Version information

• Version number: V4.3.6 BP2
• Previous version: V4.3.6 BP1
• Version release date: January 26, 2026

Product optimization

This iteration adds two new Agent backup feature configuration items:

• Agent backup timeout (backup.dump.physical.file.timeout): controls the timeout for physical backup file dumping.
• S3 storage path style (backup.storage.s3.use.path.style): configures the path access method for S3 buckets.

You can set or adjust these settings on the Overview > O&M Configuration page of the cluster.

Major bug fixes

Fixed the issue where OCP could not initiate a restore when the object storage only supported the Virtual Host Style method.

Known issues

V4.3.6 BP1

Version information

• Version: V4.3.6 BP1

• Previous version: V4.3.6

• Version release date: August 11, 2025

New features

• OceanBase Database Enterprise Edition (Standalone) supports viewing, importing, and expiration alerts for licenses.
• OceanBase Database Enterprise Edition (Standalone) can be upgraded to a distributed cluster.
• OceanBase Database Enterprise Edition (Standalone) can be upgraded to a higher database version.

Product optimization

• If the host operating system kernel version is lower than 5.1.0, the cluster Cgroup configuration is disabled by default.
• If the OBProxy version is lower than V4.3.1, hot upgrade to V4.3.4 is not supported.
• If no specific alert object is specified, automatic elimination can be disabled to prevent the corresponding alert from automatically recovering.
• In standalone scenarios, certain O&M operations are restricted, such as restarting OBServer or stopping a zone.

V4.3.6

OceanBase Cloud V4.3.6 is released! This upgrade focuses on Intelligence, Security Enhancement, and Core Capabilities Leap, comprehensively empowering enterprise database operations and management.

• Intelligent Operations Assistant: OceanBase AI Assistant is launched, deeply integrating large models with native database capabilities to provide intelligent Q&A services across the OceanBase ecosystem, enabling efficient and accurate resolution of operational issues.
• Security Capabilities Upgrade: New features include OceanBase TDE (Transparent Data Encryption) and end-to-end SSL encryption, ensuring comprehensive protection from data storage to transmission, strengthening the database security defense.
• Network Architecture Adaptation: Supports full IPv6 deployment scenarios, enabling end-to-end management of IPv6 address OceanBase clusters, meeting compliance requirements and network evolution needs.
• 30+ Feature Optimizations: Core modules such as performance monitoring, primary-standby database management, backup and restore, alert center, and inspection services are deeply optimized, significantly improving operational convenience and management efficiency, empowering users to effortlessly manage database workflows.

Version information

• Version: V4.3.6

• Previous version: V4.3.5 BP4

• Version release date: June 21, 2025

• Supported upgrade path:

  • You can directly upgrade from OCP V3.2.4 and later to the current version.

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

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

Supported OceanBase Database versions

OCP V4.3.6 supports the following OceanBase Database versions:

• OceanBase V2.2.76 and 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

New features

Basic O&M

• Cluster management: IPv6 is fully supported. You can manage IPv6 addresses in a cluster. IPv6 network environments are seamlessly adapted to meet the strict cybersecurity regulatory requirements of industries such as government and finance.
  • Supported OceanBase Database versions: [V4.2.5 BP3 Hotfix3, V4.3.0) and [4.3.5 BP2 Hotfix1, +∞).
  • Supported OBClient versions: [V2.2.9, +∞).
  • Supported OBProxy versions: [V4.3.4, +∞).
• Cluster management: Transparent data encryption (TDE) can be configured to prevent attackers from directly reading sensitive information from the storage layer and bypassing the database, ensuring user data security. Supported OceanBase Database versions: [V4.0.0, +∞).
• Cluster management: Secure Sockets Layer (SSL) link encryption (TCP and RPC) can be configured to prevent communication data from being tampered with during transmission, enhancing system security. Supported OceanBase Database versions: [V4.0.0, +∞).
• OBProxy: SSL link encryption (TCP and RPC) can be configured to prevent communication data from being tampered with during transmission, enhancing system security. Supported OBProxy versions: [V2.0.0, +∞).
• Tenant management: You can batch lock and unlock general users, improving user O&M efficiency in scenarios such as data migration and data import and export.
• Tenant management: You can build a standby tenant by replicating the backup set of the primary tenant. This improves disaster recovery management.
• Host management: You can manage regions, IDCs, and server types, but you cannot delete objects associated with existing hosts.

Monitoring and alerting

• You can view the maximum value (max), average value (avg), and current value (current) of monitoring metrics within the specified time range.
• You can add Commit and Rollback monitoring items to queries per second (QPS) and response time. Supported OceanBase Database versions: [V4.2.5 BP3, V4.3.0) and [V4.3.5 BP2, +∞).
• You can monitor hardware by querying the /var/log/messages file, helping you promptly identify hardware-related faults.

Inspection service

You can inspect the clock source settings of OBServer nodes in the same cluster to avoid merge exceptions caused by inconsistent clock source settings.

Binlog management

• When you enable the Binlog service, you can specify the number of instance replicas. The Binlog service automatically distributes instance replicas based on the number of Binlog servers in the cluster.
• You can add instance replicas to a Binlog instance. A business tenant can have up to 5 instance replicas.
• You can manage Binlog standby instances, including starting, stopping, throttling, restarting, deleting, and switching the primary instance.
• You can delete a Binlog primary instance.
• You can receive a prompt that prevents you from performing O&M operations on the MetaDB of the Binlog service, avoiding exceptions caused by misoperations.

Backup and restore

• You can set the backup attributes of zones, regions, and IDCs to reduce cross-region or cross-IDC network traffic in multi-region or multi-IDC deployment scenarios and improve backup speed.
• When you restore a tenant, you can set the zone priority to Random.

Platform features

• AI assistant: Based on large language models (LLMs), PowerRAG, and the built-in OceanBase knowledge base, it provides intelligent Q&A services about OceanBase and its related products.
• O&M management: The report center supports creating and downloading reports about OceanBase clusters, tenants, OBProxy clusters, hosts, Binlog services, and arbitration services. You can modify the report retention period by using the ocp.report.center.report.retention.days parameter.
• Parameter templates: You can import and export parameter templates of OceanBase clusters, tenants, OBProxy clusters, and Binlog services in the YAML format.
• Cluster management > O&M configuration: Five new collection metric switches are added to control whether to collect information such as wait events, cache hit rate, and partition count.

Product optimization

Cluster management

• Only clusters in the Stopped, Unavailable, Abandoned, or Migrated state can be directly deleted.
• When you perform unit migration, you can pre-check whether sufficient resources such as CPU, memory, log disk, and data disk are available to avoid migration exceptions caused by insufficient resources.
• You can enable or disable Cgroups without restarting the cluster. Supported OceanBase Database versions: [V4.2.5 BP2, V4.3.0) and [V4.3.5, +∞).

Tenant management

• The merge management feature supports displaying the usage of MEMStore, MEMStore size, CPU usage, and memory usage as monitoring metrics by unit. This helps you observe resource consumption during merges.
• The statistics management feature is optimized. The data statistics logic of the Top 10 Tables feature is changed. Supported OceanBase Database versions: [V4.2.5 BP2, V4.3.0) and [V4.3.5, +∞).
• Only primary tenants in the Locked state can be directly deleted. This avoids misoperations.
• When you create a user, you can group permissions by type, such as General and Administrator. This helps you quickly create database users.
• You can batch set role permissions for an Oracle tenant.

OBProxy management

Only primary clusters in the Stopped, Unavailable, or Empty state can be directly deleted to avoid misoperations.

Others

• Platform features: You can set the password validity period and the number of times a password can be reused by using the system parameters ocp.iam.password.validity.period.days and ocp.iam.password.reuse.times, respectively. This ensures password security.
• Platform features: On Debian 11 and later, you can use the system parameter ocp.agent.home.path.prefix to customize the installation directory of ocp_agent.
• Alert Center: You can view the monitoring metrics data at the time of alert recovery in the alert recovery details.
• Alert Center: You can click an alert rule on the alert details page to go to a new page.

Behavior changes

Container-type hosts are no longer supported during host management and cluster takeover.

Key features

AI assistant (Experimental feature)

The OceanBase AI assistant integrates large language models (LLMs), retrieval-augmented generation (RAG) technology, and the built-in OceanBase knowledge base with native vector and full-text indexing capabilities to create an intelligent question-answering engine. Based on the multi-turn retrieval mechanism of PowerRAG, the LLM can accurately call the technical documentation, best practices, and failure cases stored in the knowledge base to provide systematic and professional solutions for core database operations such as system configuration optimization, fault diagnosis and repair, and performance bottleneck analysis.

In terms of large model configuration, OCP allows users to flexibly access third-party large model services such as Qwen from Alibaba Cloud, DouBan from ByteDance, and DeepSeek through the System Management > External Integration > AI Models module, or deploy their own large models. Users can independently configure LLMs, embedding models, and reranking models (optional) to quickly activate the AI assistant. Additionally, OCP supports importing enterprise-specific best practices and standard operating procedures (SOPs) to continuously expand the knowledge base's industry adaptability.

Secure Sockets Layer (SSL) link encryption

As digital transformation accelerates, data transmission security has become a core requirement. OBProxy and OceanBase support SSL link encryption, which establishes an encrypted communication channel at the transport layer to provide end-to-end protection for network connections. This effectively mitigates risks of data theft and tampering, ensuring the confidentiality and integrity of communication processes, thereby strengthening the data transmission security foundation from the bottom up.

As the central hub for end-to-end operations and management, OCP (OceanBase Cloud Platform) provides comprehensive management capabilities covering the entire certificate lifecycle:

• Convenient certificate operations: Supports one-click upload and deletion of certificates, simplifying certificate management.
• Deep security configuration: Integrates SSL encryption configuration features for OBProxy and OceanBase, supporting custom certificate update strategies to ensure the continuous effectiveness of encrypted links.
• Support for multiple certificate formats: Provides standard format certificates such as p7b, PEM, and JKS for business application access, meeting diverse security access requirements across different technology stacks.

Through OCP's unified management, users can easily deploy and monitor secure communication across the entire business application > OBProxy > OBServer chain and secure RPC communication between OBServers, ensuring secure data transmission at critical stages such as business access, proxy forwarding, and node interaction, building a comprehensive security barrier for stable database operation.

Fixed issues

OCP V4.3.6 fixes the following issues:

• Fixed the issue where transaction data collection was incomplete when there were many concurrent transactions.
• Fixed the issue where OBServer replacement was not possible when an OBServer failed.
• Fixed the issue where disaster recovery switching could not be performed immediately in a multi-cluster mode.
• Optimized the input box for the front end to reduce lag.

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 following table lists the minimum hardware requirements for OCP-Server nodes.

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 system requirements for installing OCP-Server and OCP-Agent.

Client requirements

General users access OCP services through a Web browser. The following table lists the requirements for the client.

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

For the best experience, we recommend that you use a display with a resolution of 1440 x 810 or higher.