OceanBase Cloud supports the following OceanBase Database versions:
- OceanBase Database Enterprise Edition V4.4.1
- OceanBase Database Enterprise Edition V4.4.0
- OceanBase Database Enterprise Edition V4.3.5
- OceanBase Database Enterprise Edition V4.2.5
- OceanBase Database Enterprise Edition V4.2.1
Note
Some database versions are available only to specific customers. If you want to use them, contact OceanBase Technical Support.
V4.4.1
OceanBase Database V4.4.1 is the second LDS version of the Shared Storage Architecture. It significantly improves in multiple dimensions. In the Shared Storage Architecture, it enhances the log service capabilities and supports horizontal scaling to handle a large number of log streams. The SYS tenant supports single-replica deployment, solving the problem of additional resource occupation while simplifying operations and maintenance. It also adds support for Azure Blob, expanding multi-cloud deployment capabilities. OBKV-HBase is also optimized for the shared storage mode.
V4.4.1 also upgrades the vector retrieval capabilities, supporting hybrid search to improve recall effectiveness. It adds AI function capabilities, allowing SQL to access large models. Additionally, it improves vector retrieval performance through adaptations for ARM architecture, optimization of tables without primary keys, and optimization of IVF indexes. It also adds views to display vector index memory usage and asynchronous task status, enhancing usability.
V4.4.1 comprehensively optimizes the performance of external table queries, direct load, storage layer read/write operations, PL hard parsing, UDF execution, SQL hard parsing, batch DML, and DDL operations. It reduces PL hard parsing time by 14%, improves UDF performance by 15%-26%, and significantly enhances direct load efficiency through the upgrade of sorting algorithms.
In terms of compatibility, V4.4.1 introduces Python UDFs in MySQL tenant mode and supports the UTL_HTTP and DBMS_PLSQL_CODE_COVERAGE system packages in Oracle-compatible tenant mode. In terms of security, it supports RPC transmission encryption with national encryption standards and TLS password-free login capabilities.
V4.4.1 supports manual backup data cleanup, setting the node range for backup tasks, and adapting to strong archive scenarios for archived log consumption. It also supports HMS Catalog, OBCDC synchronization for standby tenants, output of LOB large object pre-images, JDBC plugin support for external tables, flashback access to new primary databases for standby databases, SQL keyword throttling, aggregation of user tables under database, and adaptive arbitration based on I/O load.
V4.4.0
OceanBase Database V4.4.0 is a major architectural upgrade for the multi-cloud and AI era, supporting both Shared Nothing and Shared Storage architectures. In the Shared Storage Architecture, the computing nodes and data storage are completely separated, allowing storage to be purchased as needed and computing nodes to be flexibly scaled, achieving optimal resource elasticity and cost optimization, and supporting AP, TP, and KV product forms. Based on the Shared Storage Architecture, OceanBase Database innovatively implements an independent LogService, enabling both data and logs to be shared. The OBServer becomes a truly stateless computing engine, allowing for independent and rapid scaling. It also solves the problem of single-replica cross-AZ disaster recovery. In the Shared Storage Architecture, all modules are collaboratively optimized to support incremental data sharing, local data caching, Transfer, and columnar storage capabilities, ensuring equivalent functionality, performance, and higher availability compared to the Shared Nothing Architecture. Additionally, the new version supports full-text phrase exact matching, extends the Java UDF feature, provides a path for data archiving to HDFS, optimizes the performance of external table queries, UDF execution, and PS Cursor Fetch data, enhances CSV import diagnostic capabilities, and supports dynamic effect of RPC IO thread configuration items, improving system usability.
V4.3.5
View the complete content of the V4.3.5 Release Notes
OceanBase Database V4.3.5 is the first long-term support (LTS) version for analytical processing (AP) scenarios. Based on V4.3.4, this version enhances product capabilities by adding support for nested materialized views and improving full-text and vector index features. Additionally, data import and export capabilities have been enhanced: support for specifying partitions for direct load, reading ORC files from external tables, and exporting Parquet and ORC files using SELECT INTO OUTFILE. Optimizer enhancements include baseline-priority SPM evolution, improvements to the optimizer's row estimation system, optimization for recursive common table expressions (CTEs), and enhanced query range extraction.
In terms of compatibility, OceanBase Database now supports XA transactions in MySQL tenants, improved Latin1 character set support, and complex types in stored procedure remote calls between Oracle-compatible tenants, facilitating smooth migration of Oracle and MySQL workloads.
Performance optimizations in V4.3.5 include improvements in table-level recovery, direct load, DML, and DDL operations. The new version supports online conversion between row and column storage, fast intermediate column addition, and extended parallel DDL operations. Integration of statistics and CLOG logs into the resource isolation mechanism, along with IO-level isolation, further enhances resource isolation. Additionally, the new version supports SQL-level memory usage limits, optimizes memory usage for stored procedures, and reduces tenant memory resource consumption through shared thread pools, improving stability across various scenarios. Usability improvements include enhanced diagnostics for ASH and WR, support for parallel migration of log stream replicas, and monitoring views for log transmission chains, making OceanBase Database more user-friendly. The new version supports a richer set of ARRAY and XML expressions, optimizes memory usage during JSON/XML/GIS data processing, and enhances compatibility with OBKV-HBase and HBase, supporting P95/P99 metrics for OBKV.
V4.2.5
View the full content of V4.2.5 Release Notes
OceanBase Database V4.2.5 is an LST version designed for AP and TP scenarios. This version further enhances the product capabilities based on the V4.2.4 version, introduces features such as baseline-priority SPM evolution, partitioned table late materialization, and improvements to the optimizer's cost estimation system and CTE extraction/INLINE cost verification. Additionally, it supports features like strong archiving for consumption logs, active transaction migration during transfer, and adaptive arbitration based on I/O load, enhancing system stability and reliability.
In terms of compatibility, the MySQL compatible mode of OceanBase Database supports lock functions, invalid dates, and XA transactions, which help facilitate smooth migration from MySQL. The Oracle compatible mode of OceanBase Database enhances the DBMS_LOCK package and supports fast column deletion. It also enables remote procedure calls between Oracle compatible tenants with support for complex data types. The new version optimizes table-level recovery and upgrade performance, significantly reducing the time required for these operations. Additionally, by integrating statistics and clog logs into resource isolation and implementing DDL resource isolation, OceanBase Database further strengthens its resource isolation mechanisms. The new version introduces SQL-level memory usage limits and optimizes memory usage in stored procedures to improve stability in various scenarios.
A lot of work was also done to enhance usability. ASH diagnostic improvements such as row locking wait, retry wait, histogram, and log transmission link view enhance observability. The new version also supports parallel log replica migration, dynamic memory resource adjustment with real-time take effect, and the ./alert/alert.log log file, which logs information important to DBAs. These improvements make OceanBase Database more user-friendly. The new version also adds support for the OBKV-Redis model, enriching OceanBase Database's multi-model ecosystem. The new version also optimizes the OBKV-HBase model to resolve the excessive data version issue in the hot key scenario. ColumnPaginationFilter and Reverse Scan interfaces are also added for better HBase compatibility.
V4.2.1
Click here to view the full V4.2.1 Release Notes
OceanBase Database V4.2.1 is the first long-term supported (LTS) version of the V4.2.x series. It features MySQL-compatible capabilities such as the VALUES statement and JSON_TABLE expression, as well as Oracle-compatible capabilities such as DBLink package call and sequence reading. This version also introduces the WR data collection framework, enhanced end-to-end diagnostic capabilities, and optimized system resource usage. In addition, it offers table-level restore capabilities and supports the COS backup medium. We recommend that you use this version in cloud and on-premises production environments for ordinary businesses.
V4.3.5
View full content of the V4.3.5 Release Notes
OceanBase Database V4.3.5 is the first long-term support (LTS) version for analytical processing (AP) scenarios. Based on V4.3.4, this version enhances product capabilities by adding support for nested materialized views and improving full-text and vector index features. Additionally, data import and export capabilities have been enhanced: support for specifying partitions for direct load, reading ORC files from external tables, and exporting Parquet and ORC files using SELECT INTO OUTFILE. Optimizer enhancements include baseline-priority SPM evolution, improvements to the optimizer's row estimation system, optimization for recursive common table expressions (CTEs), and enhanced query range extraction.
In terms of compatibility, OceanBase Database now supports XA transactions in MySQL tenants, improved Latin1 character set support, and complex types in stored procedure remote calls between Oracle-compatible tenants, facilitating smooth migration of Oracle and MySQL workloads.
Performance optimizations in V4.3.5 include improvements in table-level recovery, direct load, DML, and DDL operations. The new version supports online conversion between row and column storage, fast intermediate column addition, and extended parallel DDL operations. Integration of statistics and CLOG logs into the resource isolation mechanism, along with IO-level isolation, further enhances resource isolation. Additionally, the new version supports SQL-level memory usage limits, optimizes memory usage for stored procedures, and reduces tenant memory resource consumption through shared thread pools, improving stability across various scenarios. Usability improvements include enhanced diagnostics for ASH and WR, support for parallel migration of log stream replicas, and monitoring views for log transmission chains, making OceanBase Database more user-friendly. The new version supports a richer set of ARRAY and XML expressions, optimizes memory usage during JSON/XML/GIS data processing, and enhances compatibility with OBKV-HBase and HBase, supporting P95/P99 metrics for OBKV.
V4.4.1
OceanBase Database V4.4.1 is the second LDS version of the Shared Storage Architecture. It significantly improves in multiple dimensions. In the shared storage architecture, it enhances the log service capabilities and supports horizontal scaling to handle a large number of log streams. The SYS tenant supports single-replica deployment, solving the problem of additional resource occupation while simplifying operations and maintenance. It also adds support for Azure Blob, expanding multi-cloud deployment capabilities. OBKV-HBase is also optimized for the shared storage mode.
V4.4.1 also upgrades the vector retrieval capabilities, supporting hybrid search to improve recall effectiveness. It adds AI function capabilities, allowing SQL to access large models. Additionally, it improves vector retrieval performance through adaptations for ARM architecture, optimization of tables without primary keys, and optimization of IVF indexes. It also adds views to display vector index memory usage and asynchronous task status, enhancing usability.
V4.4.1 comprehensively optimizes the performance of external table queries, direct load, storage layer read/write operations, PL hard parsing, UDF execution, SQL hard parsing, batch DML, and DDL operations. It reduces PL hard parsing time by 14%, improves UDF performance by 15%-26%, and significantly enhances direct load efficiency through the upgrade of sorting algorithms.
In terms of compatibility, V4.4.1 introduces Python UDFs in MySQL tenant mode and supports the UTL_HTTP and DBMS_PLSQL_CODE_COVERAGE system packages in Oracle-compatible tenant mode. In terms of security, it supports RPC transmission encryption with national encryption standards and TLS password-free login capabilities.
V4.4.1 supports manual backup data cleanup, setting the node range for backup tasks, and adapting to strong archive scenarios for archived log consumption. It also supports HMS Catalog, OBCDC synchronization for standby tenants, output of LOB large object pre-images, JDBC plugin support for external tables, flashback access to new primary databases for standby databases, SQL keyword throttling, aggregation of user tables under database, and adaptive arbitration based on I/O load.
V4.4.0
OceanBase Database V4.4.0 is a major architectural upgrade for the multi-cloud and AI era, supporting both Shared Nothing and Shared Storage architectures. In the Shared Storage Architecture, the computing nodes and data storage are completely separated, allowing storage to be purchased as needed and computing nodes to be flexibly scaled, achieving optimal resource elasticity and cost optimization, and supporting AP, TP, and KV product forms. Based on the Shared Storage Architecture, OceanBase Database innovatively implements an independent LogService, enabling both data and logs to be shared. The OBServer becomes a truly stateless computing engine, allowing for independent and rapid scaling. It also solves the problem of single-replica cross-AZ disaster recovery. In the Shared Storage Architecture, all modules are collaboratively optimized to support incremental data sharing, local data caching, Transfer, and columnar storage capabilities, ensuring equivalent functionality, performance, and higher availability compared to the Shared Nothing Architecture. Additionally, the new version supports full-text phrase exact matching, extends the Java UDF feature, provides a path for data archiving to HDFS, optimizes the performance of external table queries, UDF execution, and PS Cursor Fetch data, enhances CSV import diagnostic capabilities, and supports dynamic effect of RPC IO thread configuration items, improving system usability.
V4.3.5
View the complete content of V4.3.5 Release Notes
OceanBase Database V4.3.5 is the first long-term support (LTS) version for analytical processing (AP) scenarios. Based on V4.3.4, this version enhances product capabilities by adding support for nested materialized views and improving full-text and vector index features. Additionally, data import and export capabilities have been enhanced: support for specifying partitions for direct load, reading ORC files from external tables, and exporting Parquet and ORC files using SELECT INTO OUTFILE. Optimizer enhancements include baseline-priority SPM evolution, improvements to the optimizer's row estimation system, optimization for recursive common table expressions (CTEs), and enhanced query range extraction.
In terms of compatibility, OceanBase Database now supports XA transactions in MySQL tenants, improved Latin1 character set support, and complex types in stored procedure remote calls between Oracle-compatible tenants, facilitating smooth migration of Oracle and MySQL workloads.
Performance optimizations in V4.3.5 include improvements in table-level recovery, direct load, DML, and DDL operations. The new version supports online conversion between row and column storage, fast intermediate column addition, and extended parallel DDL operations. Integration of statistics and CLOG logs into the resource isolation mechanism, along with IO-level isolation, further enhances resource isolation. Additionally, the new version supports SQL-level memory usage limits, optimizes memory usage for stored procedures, and reduces tenant memory resource consumption through shared thread pools, improving stability across various scenarios. Usability improvements include enhanced diagnostics for ASH and WR, support for parallel migration of log stream replicas, and monitoring views for log transmission chains, making OceanBase Database more user-friendly. The new version supports a richer set of ARRAY and XML expressions, optimizes memory usage during JSON/XML/GIS data processing, and enhances compatibility with OBKV-HBase and HBase, supporting P95/P99 metrics for OBKV.
V4.2.5
View the complete content of the V4.2.5 Release Notes
OceanBase Database V4.2.5 is an LST version designed for AP and TP scenarios. This version further enhances the product capabilities based on the V4.2.4 version, introduces features such as baseline-priority SPM evolution, partitioned table late materialization, and improvements to the optimizer's cost estimation system and CTE extraction/INLINE cost verification. Additionally, it supports features like strong archiving for consumption logs, active transaction migration during transfer, and adaptive arbitration based on I/O load, enhancing system stability and reliability.
In terms of compatibility, the MySQL compatible mode of OceanBase Database supports lock functions, invalid dates, and XA transactions, which help facilitate smooth migration from MySQL. The Oracle compatible mode of OceanBase Database enhances the DBMS_LOCK package and supports fast column deletion. It also enables remote procedure calls between Oracle compatible tenants with support for complex data types. The new version optimizes table-level recovery and upgrade performance, significantly reducing the time required for these operations. Additionally, by integrating statistics and clog logs into resource isolation and implementing DDL resource isolation, OceanBase Database further strengthens its resource isolation mechanisms. The new version introduces SQL-level memory usage limits and optimizes memory usage in stored procedures to improve stability in various scenarios.
A lot of work was also done to enhance usability. ASH diagnostic improvements such as row locking wait, retry wait, histogram, and log transmission link view enhance observability. The new version also supports parallel log replica migration, dynamic memory resource adjustment with real-time take effect, and the ./alert/alert.log log file, which logs information important to DBAs. These improvements make OceanBase Database more user-friendly. The new version also adds support for the OBKV-Redis model, enriching OceanBase Database's multi-model ecosystem. The new version also optimizes the OBKV-HBase model to resolve the excessive data version issue in the hot key scenario. ColumnPaginationFilter and Reverse Scan interfaces are also added for better HBase compatibility.
V4.2.1
View the complete content of the V4.2.1 Release Notes
OceanBase Database V4.2.1 is the first long-term supported (LTS) version of the V4.2.x series. It features MySQL-compatible capabilities such as the VALUES statement and JSON_TABLE expression, as well as Oracle-compatible capabilities such as DBLink package call and sequence reading. This version also introduces the WR data collection framework, enhanced end-to-end diagnostic capabilities, and optimized system resource usage. In addition, it offers table-level restore capabilities and supports the COS backup medium. We recommend that you use this version in cloud and on-premises production environments for ordinary businesses.