Release notes
This page provides the release notes for ApsaraDB for OceanBase.
February 25, 2025
Feature name | Feature description | References |
New data synchronization tasks | Added support for real-time data synchronization between OB_MySQL and OB_Oracle tenants. This feature enables schema, full data, and incremental DML/DDL synchronization between different OceanBase database tenants. This helps you build a unified data platform more easily. | Data synchronization between different tenants of an OceanBase database |
Added support for data synchronization from OB_Oracle tenants to Serverless-Oracle instances. This feature enables schema, full data, and incremental DML/DDL synchronization. This helps you use Serverless instances to support your business and reduce costs. | Data synchronization between the same tenants of an OceanBase database | |
New features | When you migrate data from a PostgreSQL database to an OceanBase database Oracle tenant, you can now dynamically modify migration and synchronization objects. This includes adding or removing objects and modifying matching rules. This feature lets you manage more objects in a single data migration or synchronization task and reduces task maintenance costs. | Migrate data from an RDS PostgreSQL instance to an OceanBase database Oracle tenant |
Usability improvements | For frequently-used data migration tasks between OceanBase, Oracle, and MySQL databases, incremental DDL synchronization is now selected by default. This reduces task interruptions that occur when this option is not selected. | Migrate data from a MySQL database to an OceanBase database in MySQL compatibility mode |
When you create a MySQL, Oracle, or TiDB data source, the option to configure Database Name/Schema Name is removed. This prevents issues where you cannot select other databases or schemas in a data migration or synchronization task due to misconfiguration. | ||
When you create a data source for a self-managed database instance in a VPC, a fuzzy search feature for the VPC Name is added. This makes it more convenient to configure data sources. | ||
The user interface for releasing data migration tasks is adjusted. It now displays information about the current task, such as the task ID/name, instance ID, specifications, and billing method. This improves the security of the release operation and helps prevent accidental operations. |
December 11, 2024
Feature name | Feature description | References |
New features | Added support for data migration from PolarDB-O databases to OceanBase database Oracle tenants. You can use the data migration feature to quickly migrate the schema, full data, and incremental data from PolarDB for Oracle to an OceanBase database. You can also ensure migration reliability and data backflow capabilities after the cutover through validation and reverse incremental synchronization. | Migrate data from a PolarDB-O database to an OceanBase database Oracle tenant |
Added support for data migration from AnalyticDB for MySQL databases to OceanBase database MySQL tenants. You can use the data migration feature to quickly migrate full data from an AnalyticDB for MySQL database to an OceanBase database to meet the needs of data warehouse replacement scenarios. | Migrate data from AnalyticDB for MySQL to an OceanBase database MySQL tenant | |
Added support for configuring bidirectional synchronization tasks. When you configure a migration task for MySQL <-> OB_MySQL, Oracle <-> OB_Oracle, or OceanBase <-> OceanBase, you can choose to create a unidirectional or bidirectional synchronization task. If you choose a bidirectional task, you can configure a reverse task when the forward task enters the incremental synchronization phase. The anti-loop configuration for bidirectional replication is automatically implemented. This helps you better implement scenarios such as grayscale cutover and bidirectional parallel operations. | ||
Added a feature to dynamically modify matching rules for migration and synchronization objects. By modifying the matching rules, you can add or remove migration and synchronization objects. This prevents the need to maintain multiple tasks when your business adds new objects, which reduces the cost of using data migration and synchronization. | ||
When you synchronize data from an OceanBase database MySQL tenant to DataHub, if you select the Tuple format, DTS_Compatible is added as an option for the serialization format. This option automatically maps the format to DTS-compatible fields in the destination DataHub. Business fields are prefixed with `dts_`, and non-business fields have the same names as those in DataHub tasks created by DTS. This helps you achieve task compatibility with DTS through the data synchronization feature and avoid business transformation. | ||
The restriction on tables without non-null unique keys is lifted for all data migration and synchronization task types, except for OceanBase MySQL -> ADB and Lindorm/HBase -> OBKV. Tables without non-null unique keys can be migrated and synchronized normally. For tasks that support hidden columns (Hidden column mechanism of Data Transmission Service), an option is provided for you to choose whether to configure hidden columns to ensure the consistency of migration and synchronization for tables without non-null unique keys. Important For tables that do not have non-null unique keys or hidden columns in the destination, data duplication may occur if the migration or synchronization process restarts or pulls back data. | ||
When you migrate data from a MySQL database to an OceanBase database MySQL tenant, the MySQL `utf8mb3` character set is now automatically mapped to the `utf8mb4` character set of the OceanBase database MySQL tenant. This enables fast migration and synchronization of MySQL databases. | Migrate data from a MySQL database to an OceanBase database in MySQL compatibility mode | |
Usability improvements | When you configure a data synchronization task, a column search feature is added for selecting synchronization columns. | |
A filtering feature is added for the source and destination databases of index migration objects. |
October 30, 2024
Feature name | Feature description | References |
Cluster instances | You can purchase OceanBase V4.3.3 cluster instances. These instances support the creation of row-oriented, column-oriented, and hybrid row-column tables. They also support new features such as the vector field type, vector indexes, and vector function retrieval. | |
Read-only column-oriented replicas | OceanBase V4.3.3 cluster instances support the creation of read-only column-oriented replicas. The table data on these replicas is automatically stored in a columnar format, which improves online analytical processing (OLAP) performance. | |
Tenant parameter templates | When you create a tenant, you can apply different parameter templates to create different types of tenants. It supports OLTP tenants (table data is row-oriented by default), OLAP tenants (table data is column-oriented by default), and HTAP tenants (table data is row-oriented by default with optimized AP analysis capabilities). You can also modify parameters to have HTAP tenants automatically create hybrid row-column data tables. | |
Database proxy |
| |
Performance monitoring |
| |
Security management | SSL-encrypted links support automatic renewal of SSL certificate validity. | |
Upgrade/Downgrade | Cluster instances support conversion between 1:8 and 1:4 specifications. | |
Tag management | Clusters and tenants support a maximum of 20 tags. |
October 17, 2024
Feature name | Feature description | References |
New data migration tasks | Added support for data migration tasks from ApsaraDB for HBase Enhanced Edition V2.0 and Lindorm to Alibaba Cloud OBKV. You can use the data migration feature to quickly migrate data from ApsaraDB for HBase Enhanced Edition and Lindorm databases on Alibaba Cloud to OBKV. You can also perform reverse data backflow from OBKV to the source database. This helps you quickly and conveniently migrate data to OceanBase KV scenarios and ensures reverse disaster recovery for data after business cutover, guaranteeing a smooth transition. | |
New features | When creating indexes after data migration, two new configuration items are added: DDL Concurrency for a Single Index and Maximum Number of Concurrent Index DDLs. These items control the DDL statement concurrency for index execution and the number of post-migration indexes running simultaneously in the system. This helps control the pressure from indexing and reduces the load on the destination database. | |
For data migration tasks involving MySQL <-> OB_MySQL, OB_MySQL -> OB_MySQL, Oracle <-> OB_Oracle, and OB_Oracle -> OB_Oracle, migration capabilities for GIS field types are implemented for schema, full data, and incremental data. Data validation for GIS field types is also supported. This provides capability support for data migration of spatial data services. | ||
You can now dynamically modify the filter conditions for data migration or data synchronization tasks. After modification, the task will continue to migrate data using the new filter conditions. This adapts to changing business needs during long-term synchronization. |
August 14, 2024
Feature name | Feature description | References |
Database proxy | The SQL Firewall feature is released. It supports blocking specified SQL statements. | |
You can customize the read traffic policy, load balancing policy, and disaster recovery policy for read-only and read/write splitting endpoints. | ||
You can create read-only and read/write splitting endpoints for secondary clusters. | ||
Resource group management | You can create resource groups within a tenant to set the percentage of CPU that a database USER can use. | |
Resource limit optimization | A single cluster now supports more tenants. | |
For tenant specifications, provided that the minimum specification of 1C 4GB is met, the CPU-to-memory ratio is changed from 1:2 to 1:1. For example, you can now create tenants with 2C 4GB or 4C 4GB specifications. | ||
Instance and tenant management | Scheduled upgrades and downgrades for tenant specifications are supported. | |
You can create tenants with the Latin1 character set. | ||
The maximum length for cluster instance names and tenant names is now 64 characters. | ||
User permission management supports batch authorization for database users. | ||
You can call an API to automatically update the validity period of SSL certificates. | ||
Read replicas support automatic storage expansion. | ||
Table-level permission control is added. This allows project members to have different operation permissions for different tables, including query, change, and export operations. This further enhances collaborative control capabilities. | ||
Real-time execution analysis is added. It provides a visual and interactive presentation of sql_plan_monitor. | ||
When you create and edit lock-free schema change tasks, you can set throttling parameters. | ||
Data transmission feature optimization | You can now upgrade the instance specifications for data migration and data synchronization tasks. Upgrading the specifications increases the upper limit of RPS to meet performance improvement requirements for data migration/synchronization tasks when business pressure increases. | |
When the destination or reverse incremental source is an OceanBase database of V4.3.x or later, you can configure the table schema storage type. The options include default, row store, column store, and hybrid row-column store. | Migrate data from a MySQL database to an OceanBase database in MySQL compatibility mode | |
Data synchronization tasks from a database to a message queue support selecting synchronization objects using matching rules. | ||
You can enable SSL-encrypted connections for MySQL data sources. |
June 7, 2024
Feature name | Feature description | References |
Read replicas | A cluster instance supports the creation of up to 10 read replicas. | |
Database proxy |
| Database proxy service overview Database proxy service management |
Instance management | The instance topology graph can be switched to a list view to see replica, tenant, and node information. | |
Performance monitoring |
| |
Primary/secondary cluster | Secondary clusters support read-only queries. | |
OpenAPI | Supports tag group and tag management. | CreateTag - Create a tag group DescribeTagValues - Query tags DeleteTag - Delete a tag group |
Backup and restoration |
| |
Autonomy service |
|
April 8, 2024
Feature name | Feature description | References |
Architecture optimization | OceanBase database clusters can be deployed in regions with only two data centers. | - |
Tenant feature optimization | When creating a MySQL tenant, you can set whether table names are case-sensitive. | |
Cluster feature optimization |
| |
Second-level monitoring capability launched | The default monitoring frequency for OceanBase databases is 60s. If your business requires more precise monitoring, you can now set it to 5s (paid service). | |
Monitoring capability enhancement |
| |
Data security enhancement | Supports the signing and display of cross-border data transfer agreements. | |
Backup and restoration enhancement |
| |
Autonomy service enhancement |
| Tenant performance monitoring overview |
Data transmission feature optimization |
| |
Support for OceanBase Serverless instances is added. | ||
For data migration or data synchronization tasks that involve DDL synchronization, you can customize the DDL types to be synchronized. | ||
Concurrent resource and rate-limiting configurations are added for data migration and data synchronization tasks. By adjusting these configurations, you can control the concurrency and traffic for full migration, incremental synchronization, and reverse incremental synchronization (data synchronization tasks only), ensuring the stability of the source/destination and the task itself. | Migrate data from a MySQL database to an OceanBase database in MySQL compatibility mode | |
When setting up incremental synchronization for a TiDB data source, a TiDB data format option is added. You can choose between TiCDC or TiDB Binlog formats based on your actual scenario. This meets different TiDB incremental parsing needs and enables quick connection for incremental synchronization from TiDB to an OceanBase database MySQL tenant. |
February 7, 2024
Feature name | Feature description | References |
Serverless instances officially launched |
| |
Read replica feature officially launched | You can create read replicas for OceanBase database Standard Edition (Cloud Disk) cluster instances. With this feature, you can switch query traffic to read replicas, effectively reducing the load on the primary replica and improving the throughput capacity of the instance. | |
Database proxy service supports dedicated specifications | The OceanBase database proxy provides two types of proxy services: shared proxy and dedicated proxy.
| |
Automatic scaling optimization | The automatic storage expansion mechanism has been optimized and upgraded:
| |
Storage type conversion | You can switch the storage type of a cluster instance between ESSD PL1 and ESSD PL0 cloud disks. | |
Scheduled tenant specification change | OceanBase databases support setting scheduled tenant specification changes to dynamically adjust tenant resource quotas such as CPU and memory. | |
New specifications for OceanBase Standard Edition (Key-Value) released | In the China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), and China (Shenzhen) regions, you can select 4-core 16 GB, 8-core 32 GB, 16-core 70 GB, and 24-core 120 GB configuration options for the Standard Edition (Key-Value) series when configuring instance specifications. | |
Backup and restoration enhancement |
| CreateBackupSetDownloadLink - Create a download link for a backup task |
Autonomy service feature optimization |
|
January 24, 2024
Feature name | Feature description | References |
New features | The reverse incremental synchronization feature is added for migrating homogeneous or heterogeneous databases, such as Oracle, OceanBase, and TiDB, to OceanBase 4.2.0/4.2.1. This feature is mainly used for data backflow after data migration is complete. | |
Data migration from OceanBase 4.2.0/4.2.1 as a source is now supported. This includes data migration between OceanBase 4.2.0/4.2.1 instances and from OceanBase 4.2.0/4.2.1 to a MySQL database. | ||
A single data migration project now supports scenarios with many large objects. | ||
Data migration projects from cloud-based OceanBase database Oracle tenant cluster instances to Oracle databases over a public network or within a VPC are now supported. | Migrate data from an OceanBase database Oracle tenant to an Oracle database | |
Data migration and data synchronization projects from Alibaba Cloud RDS for PostgreSQL databases to cloud-based OceanBase database Oracle tenant cluster instances are now supported. | ||
Database-to-database data synchronization projects now support matching rules. This lets you select synchronization objects by configuring wildcard rules, which reduces the cost of selecting synchronization objects. | ||
Matching rules now support schema wildcards. | ||
Data synchronization projects from an OceanBase database MySQL tenant to Kafka now support outputting OceanBase data to Kafka in the Avro serialization format. This expands the ways you can connect to downstream big data ecosystems. | ||
Eight new OpenAPI interfaces are supported. These interfaces mainly cover RDS for PostgreSQL data sources, adding and removing tables, and transmission instance modules. |
October 20, 2023
Feature name | Feature description | References | |
New features | New ARM architecture specifications released | Standard Edition (Cloud Disk) series ARM architecture clusters are released, supporting specifications including 16C 70GB, 32C 180GB, and 62C 400GB. The corresponding compute instance prices are about 18-20% lower than the same specifications on x86, suitable for customers with different CPU architectures. | |
Overall optimization of cluster specification change capability | The existing specification change capabilities have been further categorized into temporary upgrades, standard upgrades, etc. The ability to convert temporary storage and specifications into permanent ones has been added, providing more flexibility to adapt to business changes for cloud customers. | ||
Backup and restoration enhancement |
| ||
August 22, 2023
Feature name | Feature description | References | |
New features | Automatic storage scaling | You can configure automatic storage scaling rules to achieve automatic resource expansion. The upper limit for automatic scaling is set by the user. When storage is about to overflow, the cluster's storage space can be automatically expanded to ensure the stability of online services. This is mainly suitable for scenarios with large data volumes or frequent and significant fluctuations in business volume. | |
Endpoint optimization | Supports adding two endpoints for multi-data center deployment solutions. When there are two endpoints, only read-only endpoints are supported. When there is one endpoint, the endpoint type can be read-only or read-write. | ||
Tenant specification lower limit change | The lower limit for tenant specifications in a cluster instance has been adjusted. The minimum specification for tenants of V3.x and later versions has been changed from the original 2C 5G to 1C 4G. This allows for the creation of more tenants within the same cluster size, which can reduce user costs. | ||
Backup and restoration enhancement | Supports restoration from a backup set. You can choose a specific point in time to restore from an existing backup set. | ||
New region available | The Frankfurt site is now available. It supports the full range of cluster Standard Edition (Cloud Disk) (4C-62C), supports accounts from both Alibaba Cloud China and International websites, and supports pay-as-you-go and subscription billing methods. | ||
June 30, 2023
Feature name | Feature description | References | |
New features | Temporary upgrade | Subscription cluster instance users can temporarily upgrade their specifications as needed for scenarios such as sales promotions, without affecting the original order discount. They can later gradually scale back to the original specifications. | |
Tenant instance specification change | Supports upgrading and downgrading tenant instances, allowing scaling between 1C and 2C specifications. | ||
Monitoring drill-down and custom monitoring | The monitoring drill-down feature provides data display for the same monitoring metric across different dimensions, assisting in daily O&M analysis. The custom monitoring capability allows users to configure frequently-used monitoring metrics as a custom monitoring dashboard as needed. | ||
New product | The single data center deployment mode for cluster instances now supports the selection of 3 full-featured replicas (3F). | ||
Version adaptation | Version 4.0 is delisted, and version 4.1 is fully available. The corresponding 4C specification is now fully available for purchase. | ||
New region available | The Malaysia site is now available. | ||
Pricing adjustment | Overall price adjustment, reducing the total price of 4C, 14C, and 24C cluster instances. | ||
May 22, 2023
Feature name | Feature description | References |
New features | Added support for schema migration, full migration, incremental synchronization, full validation, and reverse incremental synchronization from MySQL databases to OceanBase database MySQL tenant version 4.1.0 and OceanBase tenant instances. | Migrate data from a MySQL database to an OceanBase database in MySQL compatibility mode |
Added support for full validation and reverse incremental synchronization from MySQL databases to OceanBase database MySQL tenant version 4.0.0. | ||
Added support for schema migration, full migration, incremental synchronization, full validation, and reverse incremental synchronization from OceanBase database MySQL tenant versions 2.x and 3.x to OceanBase database MySQL tenant version 4.1.0. | ||
Added support for schema migration, full migration, incremental synchronization, full validation, and reverse incremental synchronization from TiDB databases to OceanBase database MySQL tenants. | Migrate data from a TiDB database to an OceanBase database MySQL tenant | |
Added support for full migration, incremental synchronization, and full validation from PolarDB-X 1.0 databases to OceanBase database MySQL tenants. | Migrate data from a PolarDB-X 1.0 database to an OceanBase database MySQL tenant | |
Added support for nine common batch operations, such as batch start and batch pause, to improve overall O&M efficiency. | ||
Added support for full and incremental synchronization from OceanBase databases to RocketMQ (Commercial and Community editions). | ||
Added support for DDL synchronization from OceanBase databases to Kafka. This lets you be promptly aware of schema changes. | ||
The destination Kafka, DataHub, or RocketMQ now supports the Debezium JSON format, which facilitates integration with downstream big data ecosystems. | ||
You can now set the `cluster_id` (serialization methods: Default/DefaultExtendColumnType) to handle different situations. This feature is suitable for business scenarios such as data cleansing and archive databases. | ||
Added support for dynamic modification of project names, which makes project management easier. | ||
Added support for data migration and data synchronization between different Alibaba Cloud accounts. | ||
Added support for tag management. This lets you manage projects and perform batch operations based on tags. | ||
Added support for removing non-compliant objects during the precheck step. This makes it easier to create projects and improves product usability. | ||
Added support for selecting an incremental synchronization offset when you choose incremental synchronization without full migration. |
May 17, 2023
Feature name | Feature description | References | |
New features | Binlog service | The Binlog service is used to collect OceanBase transaction logs and convert them into MySQL Binlog format, mainly for scenarios such as real-time data subscription. The Binlog service provides tenant-level activation and management functions and is currently free for a limited time. | |
Tenant isolation optimization | Supports cgroup isolation mechanism. With cgroup, CPU resource isolation between tenants can be achieved, along with CPU resource sharing between regular tenants and meta tenants, and request processing prioritization. | ||
Standard Edition (Key-Value) | Standard Edition (Key-Value) is OceanBase's NoSQL database model, which can bypass the SQL engine to directly read data from the storage engine. It also provides a variety of simpler and more efficient non-relational API interfaces, fully leveraging the advantages of the new architecture where NoSQL and SQL coexist to meet the diverse data needs of users in different scenarios. Currently, only 32C and 64C specifications are supported. | ||
Decouple secondary instances | Supports decoupling a secondary instance into a new cluster instance that is independent of the existing primary cluster. This can improve resource utilization and is generally used for scenarios such as business splitting. | ||
Convert subscription to pay-as-you-go | Supports changing the billing method from subscription to pay-as-you-go. | ||
New version released | New version V4.1.0.0 is released, supporting 2F1A replica mode, which can reduce user costs. | -- | |
March 28, 2023
Feature name | Feature description | References | |
New features | Cluster instance scale-in | Cluster instances support scale-in operations, including node scale-in, specification scale-in, and storage scale-in. This is supported for both subscription and pay-as-you-go instances on both Alibaba Cloud China and International websites. | Modify storage capacity for scale-in |
Database and table recycle bin | The recycle bin is mainly used to store information about deleted databases and tables. Users can restore database and table data from the recycle bin. Items in the recycle bin still occupy physical space and can be set to be automatically cleared after a certain period or manually purged. | ||
Backup and restoration | Supports local archive backup function, reducing the cost for users to retain backup files for a long time. Files transferred to archive backup must be stored for at least 60 days; if less than 60 days, they will be billed for 60 days. Archive backups do not currently support downloading. | Backup and restoration billing | |
March 17, 2023
Feature description | References | |
Developer Center Guide | Supports data masking, providing a static data masking function. Data masking policies can be enabled in scenarios such as data export and result set export. For example: ODC supports built-in masking rules for data such as mailboxes, bank card numbers, fixed-line phones, mobile phones, and ID card numbers. Masking policies are configured by specifying the matching range of In addition to built-in rules, you can also configure custom masking rules. ODC supports masking algorithms such as redaction, character replacement, format preservation, hash encryption, rounding, and nullification. | |
Supports shadow table synchronization, which automatically creates and synchronizes the shadow table structure in the same database based on the source table's structure. | ||
Supports partition plan function, which automatically pre-creates and deletes expired RANGE and RANGE COLUMNS partitions. | ||
Supports SQL plan tasks, which allow for the scheduled, periodic execution of user-created SQL scripts to meet the needs of periodic database development and O&M tasks. | ||
Supports automatic authorization rules. Administrators of the public resource console can automatically grant specific roles or permissions to users who meet certain criteria, such as name, department, or logon method, upon their initial logon or user creation. This avoids many redundant authorization operations. | ||
SQL window optimization:
| ||
Import and export:
|
February 27, 2023
Feature name | Feature description | References | |
New features | Backup and restoration | Supports restoring a cluster to the region where the geo-redundant backup is located using the geo-redundant backup file. Supports initiating a restoration from a destination cluster using the geo-redundant backup file of another cluster in the same region. Logical backup supports incremental data backup, ensuring data consistency of tables without downtime. | |
Security assessment | A security assessment menu has been added to the security settings. It supports detecting and assessing the overall database security, including cluster and tenant check items. Users can navigate to the specified module for security configuration based on the assessment recommendations. | ||
New specifications released | Large specification 104C is released. The list of expansion specifications has been adjusted and is controlled by a whitelist. | ||
Increase the number of nodes | Node expansion can go up to 45 nodes, i.e., 15-15-15. The previous maximum was 18 nodes. | ||
OceanBase 4.0 version | Expanded purchase options: Supports various specifications such as 4C, 8C, 14C, 24C, 30C, 62C, and 104C, giving users more choices. All specifications support expansion: Supports specification expansion, storage expansion, and node expansion capabilities, helping invitational preview users and those who purchased small specifications to smoothly transition to higher specifications for production use. | ||
Standby instance | Supports adding a secondary instance to a cluster instance to form a primary-multiple-secondary cluster network. Data is synchronized between the primary and secondary instances through asynchronous log replication. When the primary instance is unavailable, the secondary instance can take over the service, providing disaster recovery capabilities and minimizing service downtime. | ||
Autonomy service | Supports summarizing the capacity risks of all existing clusters, reflecting resource shortages, assessing whether expansion is needed, whether there is operational pressure, and reminding users to perform O&M operations in advance to avoid capacity risks. | ||
December 9, 2022
Feature name | Feature description | References | |
New features | Tenant instance (MySQL mode) | Tenant instances (1C 4G and 2C 8G) can be used independently as a database instance. Under a tenant instance, you can create databases and tables separately, providing services to upper-layer applications independently. This is mainly for developer users or scenarios with small data volumes that do not have very high availability requirements. It is not recommended for enterprise core business or other high-availability scenarios. | |
Read/write splitting | Supports read/write splitting, where reads are by default allocated to secondary replicas and writes to the primary replica. This achieves replica separation for read and write operations, enabling multi-endpoint, multi-replica load balancing and better separation of read and write transactions. | ||
Primary zone distribution | Supports the distribution of primary zones in multi-node scenarios and the ability to modify primary and read-only endpoints. This works with read/write splitting to add functionality for read and write access endpoints. | ||
November 28, 2022
Feature name | Feature description | References |
New features | Added support for schema migration, full migration, and incremental synchronization from MySQL databases to OceanBase database MySQL tenant version 4.0. | |
A precheck skip function is provided to ensure a smooth end-to-end process. | ||
Added support for dynamically adding and removing tables in the specified object mode. This reduces resource consumption and manual O&M complexity. | View and modify migration objects and their filter conditions View and modify synchronization objects and their filter conditions | |
Self-managed OceanBase databases in a VPC now support advanced option input. This caters to cross-network deployment, cross-cloud transmission, and migration of tables without unique keys. | ||
Added support for the self-service release of transmission instances to save resource usage. | ||
User experience upgrade | The full migration step now provides SQL execution time monitoring to help you effectively identify performance-related issues. | |
The incremental synchronization and reverse incremental steps now provide SQL execution time, which offers an intuitive experience of link efficiency. |
September 19, 2022
Feature name | Feature description | References |
New features | Added support for smooth migration and synchronization from MySQL 5.5 to OceanBase databases. | |
The display of full migration and validation performance data and baseline data is now available. This makes it easier for you to identify performance issues. | ||
Added support for the partition import function, which improves full migration performance and saves overall migration time. | ||
Full validation provides a new data validation method, which improves full validation efficiency. | ||
Added support for one-click skipping of unsupported incremental DDL statements. This simplifies user operations and improves link stability. | ||
Added support for displaying incremental synchronization performance data, which makes it easy for you to identify performance issues. | ||
Added support for displaying incremental synchronization DML/DDL statistics. This provides an intuitive experience of link efficiency and change object tracking. | ||
Added support for importing and exporting objects and object settings in CSV format. This allows for easy batch settings and cross-environment migration, which improves work efficiency. | ||
Eleven common OpenAPI interfaces are now available to meet your automation needs. | ||
Added support for Kafka cross-cloud transmission scenarios. | ||
Enhanced guidance is provided for setting project alerts to achieve real-time project monitoring and assurance. |
July 7, 2022
Feature name | Feature description | References | |
New features | Autonomy service | This section describes how to connect to the autonomy service. You can connect clusters that are in the running state to the autonomy service. | |
This section describes how to use real-time diagnosis. The real-time diagnosis page lets you view SQL running status, session analysis, and more. | |||
This section describes how to use the capacity center. The capacity center shows you the data volume trend of system tables. | |||
This section describes how to use security management. Security management provides you with the SQL Audit feature. | |||
This section describes how to use optimization records. By querying optimization records, you can view the operation history of cluster plan binding and index binding. | |||
July 1, 2022
Feature name | Feature description | References | |
New features | Data migration | Added support for data migration from OB_MySQL (Alibaba Cloud instance) to MySQL (RDS, PolarDB, VPC, Database Gateway, or public network). | Create a data migration project from an OceanBase database MySQL tenant to a MySQL database |
Added support for data migration from an OceanBase (Alibaba Cloud instance) to another OceanBase (Alibaba Cloud instance). | Create a data migration project from an OceanBase database to an OceanBase database | ||
Added support for migrating tables without unique keys from MySQL to OB_MySQL. | |||
Added support for automatic database creation from MySQL to OB_MySQL. | |||
Data synchronization | Added support for data synchronization from OceanBase databases to DataHub (VPC or public network). | Create a data synchronization project from an OceanBase database to DataHub | |
Added support for data synchronization from OB_MySQL (Alibaba Cloud instance) to OB_MySQL (VPC). | Create a data synchronization project from an OceanBase database to an OceanBase database | ||
Usability improvements | Optimized the process so that table processing failures during schema migration, full migration, and full validation do not affect project operations. | -- | |
A forced character set conversion capability is now available to support more data source character set compatibility scenarios. | -- | ||
May 31, 2022
Feature name | Feature description | References | |
New features | Archive database | To solve the problem of reading and updating historical data, an archive database is provided to store archived data. A low-cost storage solution that uses large-capacity mechanical disks effectively reduces the storage cost of historical data. The archive database also includes a query function, which lets you enjoy the cost-effectiveness benefits of the archive database. | |
Support for local disks | Added support for locating the database storage and database engine on the same node. This provides high I/O performance and low read/write latency to meet the high IOPS performance requirements of some business systems. | ||
TDE integration with Alibaba Cloud KMS | Added support for hosting TDE keys in Alibaba Cloud KMS to meet relevant regulatory compliance requirements. | ||
Feature optimizations | Data Transmission | Added support for automatic synchronization of incremental DDL when you migrate from MySQL to OceanBase MySQL. Added support for reverse incremental synchronization back to MySQL after you switch to OceanBase MySQL. | Create a data migration project from a MySQL database to an OceanBase database MySQL tenant |
Data synchronization efficiency is significantly improved, with support for synchronization to different topics in a single project. Full migration performance is enhanced. For example, indexes are created after full migration, and reading and writing data by partition is supported. | Create a data synchronization project from an OceanBase database to DataHub | ||
The capability of synchronizing data from OceanBase to AnalyticDB for MySQL is continuously optimized and enhanced, with support for partial automatic DDL synchronization from OceanBase MySQL to AnalyticDB for MySQL. | |||
Usability and user experience are optimized. The user interface for renaming databases and tables is optimized. The display of incremental synchronization data volume and latency monitoring curves is supported. The product is now fully internationalized. | |||
Data development | Enterprise-level control functions are provided, such as task flow change management, risk data determination and operation audit, and SQL audit, to ensure the security of your data assets and meet various audit requirements. | ||
Added support for ODP (Sharding) OceanBase MySQL data sources. Recycle bin management capabilities are provided. The SQL execution window now has an independent session design. Support for exporting functions and stored procedures and uploading multiple script files is added. | |||
Optimized PL/SQL execution details. | |||
Usability is improved. Added support for online editing of CLOB fields smaller than 200 KB. The system is optimized to display more effective prompt information, such as line numbers and positions, when a PL compilation error occurs. The product is now fully internationalized. | |||
May 13, 2022
OceanBase Migration Assessment (OMA) is released for the first time on the public cloud. It provides both online and offline assessment methods. This lets you choose between a direct instance connection or uploading collected files for compatibility and SQL assessment based on your network and resource conditions. OMA provides assessment reports in both HTML and PDF formats and features a simple and user-friendly interactive process. You can try it in the OceanBase console.
Feature name | Feature description | References | |
New feature | First release of OMA on public cloud | OMA is a database compatibility assessment tool provided by OceanBase. It offers precise compatibility assessment, SQL assessment optimization, and application transformation suggestions for migrating to OceanBase, helping users achieve an efficient and smooth migration to the distributed database OceanBase. | |
April 20, 2022
Feature name | Feature description | References | |
Feature upgrade | OceanBase data synchronization to ADB | Upgraded OceanBase MySQL tenant data synchronization to ADB. Supports schema synchronization, full data synchronization, and incremental data synchronization. Provides database and table renaming, custom partition keys and distribution keys, and partial DDL synchronization capabilities. | |
March 20, 2022
Feature name | Feature description | References | |
New features | Support for SQL Audit capability | For internal compliance scenarios, supports operation audit of SQL records in the cluster console by database, node, keyword, time range, username, operation type, etc. Also supports exporting SQL records. | |
Fast storage expansion | Supports fast expansion of ESSD cloud disks, improving customer experience. | ||
OceanBase data synchronization to Kafka | Added support for real-time data synchronization from OceanBase instances to Alibaba Cloud Kafka instances and self-managed Kafka instances in a VPC. Provides five types of JSON serialized message formats. | Create a data synchronization project from an OceanBase database to Kafka | |
December 8, 2021
Feature name | Feature description | References | |
New features | Commercialization of backup and restoration | The OceanBase backup and restoration features are free to use, but backup files occupy a certain amount of storage space. The storage medium is OSS. After successfully purchasing a cluster, a backup and restoration order will be generated for you. | |
New service account authorization feature | You can use the service account authorization feature to grant permissions for configuration, index querying, data, etc., to Alibaba Cloud technical support personnel. | ||
November 8, 2021
Feature name | Feature description | References | |
New | New OpenAPI | Supports users managing clusters through OpenAPI, including creating and deleting tenants, users, and databases under the cluster. Users can manage OceanBase clusters on their existing O&M management platform. | |
Developer Center supports permission control | Administrators can configure permissions for regular users (including whether to allow creating personal connections, whether they have access to public connections, and read/write control over public connections). | ||
Supports data synchronization between OceanBase MySQL tenants | The OceanBase data transmission feature supports synchronizing data from physical or logical tables of an OceanBase database MySQL tenant to another OceanBase database MySQL tenant. | Create a data synchronization project from an OceanBase database to an OceanBase database | |
August 19, 2021
Feature name | Feature description | References | |
New | 8C 32G model released, significant cost-performance improvement | Supports the sale of 8-core 32G models. Currently available for sale in the Hangzhou non-finance region, supporting single data center deployment mode, which greatly lowers your entry barrier. | |
Supports multi-Unit deployment for tenants | When creating a tenant, you can select the number of Units to deploy the same tenant across multiple Units, improving the tenant's distributed capability. | ||
New data synchronization feature | The data synchronization feature helps you achieve real-time data synchronization between OceanBase physical tables and self-managed Kafka, RocketMQ message queues, expanding message processing capabilities. It also supports real-time data synchronization between Sybase ASE and self-managed RocketMQ terminals. | ||
Other | Product usability improvement | The cluster and tenant management functions have been redesigned. Through a graphical interface, they provide you with clearer O&M information. | -- |
Quick BI/DataV supports OceanBase data source | OceanBase cloud service supports using OceanBase as a data source in Quick BI and DataV products, and supports data interaction via internal network. | -- | |
July 19, 2021
Feature name | Feature description | References | |
Database development and management | SQL window supports DBMS output | The SQL window supports DBMS output. When running a PL statement in the SQL window, the result tab supports displaying the return information of the DBMS statement. | |
Result set interaction optimization | In the result set, you can drag column names to adjust the column order, filter and sort fields by value, and use the Copy and Set to Null operation keys. | ||
Schema switching | In Oracle mode, after entering a connection, you can perform a schema switch operation in the navigation bar at the top of the workbench. | ||
Asynchronous execution | An asynchronous execution tool has been added. When a synchronously executed statement in the SQL window runs for too long, an execution timeout may occur. You can use the asynchronous execution tool to run time-consuming SQL statements to avoid statement execution timeouts. | ||
Analog data | ODC provides an analog data feature for you to quickly generate data based on the field types in a table, for scenarios that require a large amount of simulated data, such as testing database performance or verifying functions. | ||
June 16, 2021
Feature name | Feature description | References |
Support for log replicas | By setting the third replica as a log replica, storage and computing resource costs are reduced without affecting performance, improving cost-effectiveness. | |
New security group whitelist grouping feature | Supports whitelist grouping and editing. | |
New SSL link encryption feature | ApsaraDB for OceanBase supports SSL link encryption to ensure secure data transmission between the client and the server. | |
New TDE transparent encryption feature | ApsaraDB for OceanBase supports Transparent Data Encryption (TDE), which can encrypt data at rest. | |
Experience optimization | Includes improvements to monitoring capabilities and experience optimizations for operations such as lists and searches. For details, log on to the OceanBase console to experience. | -- |
April 12, 2021
Feature name | Feature description | References |
New Basic Edition series service | Supports hourly billing for storage capacity based on actual usage. | |
Optimized backup and restoration feature |
| |
New merge feature | Supports manual merging of cluster data. |
January 28, 2021
Feature name | Feature description | References |
New tenant parameter management feature | Lets you view the tenant's parameter list, modify parameters, and view parameter modification history. | |
Supports vertical scaling, storage space expansion, and subscription renewal |
| |
Added resource tag feature | Each cluster can have up to 10 tags. You can also add or delete tags through Manage Tags. | |
Database development and management | The Config URL connection method for OceanBase database in MySQL mode has been removed. | |
Optimized the connection password modification method. | ||
Supports viewing execution plans in text format. |
December 23, 2020
Feature name | Feature description | References |
New cluster parameter management feature | The parameter management feature lets you view the parameter list, modify parameters, and view parameter modification history. | |
Supports displaying disk usage | Monitors cluster node data and supports monitoring of disk usage. | |
Added account permissions | Multiple permissions have been added to the account types, and user permission settings are supported in RAM access control. | |
Supports purchasing across multiple zones | When deploying in multiple data centers, you can deploy three nodes in three different zones to achieve cross-zone disaster recovery at no extra charge. |
December 8, 2020
Feature name | Feature description | References | |
Monitoring and alerting feature | Supports creating alert rules and managing them by viewing, adding, modifying, or disabling them. | ||
Whitelist modification entry optimization | An entry has been added to the page, allowing you to directly manage the whitelist. | ||
Subscription purchase type displays expiration time | Provides service expiration date reminders or expiration notices. | ||
Database development and management | Creation and management of package objects | Provides a visual interface for creating and managing package objects. | |
Creation and management of sequence objects | Provides a visual interface for creating and managing sequence objects. | ||
Table creation optimization |
| ||
SQL window optimization |
| ||
Anonymous block window | A workspace for database developers to edit anonymous block scripts. Supports editing and running PL statements. | ||
Connection creation optimization | Supports advanced information configuration, allowing customization of timeout and sys view access users. | ||
Connection management optimization |
| ||
Manage sessions |
| ||
Recycle bin management |
| ||
Improved database object management |
| ||
SQL console: Comprehensive features |
| ||