This topic describes the release notes of ApsaraDB for OceanBase.
June 7, 2024
Feature | Description | Related Documentation |
Database proxy |
| - |
Instance Management | The instance topology now supports viewing the information on replicas, tenants, and nodes. | |
Performance Monitoring |
| |
Primary/Standby Clusters | Standby clusters support read-only queries. | |
OpenAPI | Supports tag group and tag management. | |
Backup and Restore |
| |
Autonomous Service |
|
April 8, 2024
Feature | Description | Related Documentation |
Architecture Optimization | OceanBase database clusters now support deployment in regions with only two IDCs. | - |
Tenant Feature Optimization | When creating a new MySQL tenant, it supports setting case sensitivity for table names. | |
Cluster Feature Optimization |
| |
Second-level Monitoring | The default monitoring frequency for OceanBase database is 60 seconds. For more precise monitoring, it now supports setting it to 5 seconds (Charges apply). | |
Enhanced Monitoring Capability |
| |
Enhanced Data Security | Supports signing and displaying cross-border data transfer protocols. | |
Enhanced Backup and Restore Capability |
| |
Enhanced Autonomous Service Capability |
| Tenant performance monitoring overview |
February 7, 2024
Feature | Description | Related Documentation |
Auto Scaling Optimization | The automatic scaling mechanism for storage space has been optimized and upgraded:
| |
Tenant Specification Scheduled Scaling | OceanBase Database supports scheduled adjustments of tenant specifications, dynamically adjusting resources such as CPU and memory quotas for tenants. | |
Enhanced Backup and Restore Capability |
| |
Autonomous Service Optimization |
|
January 24, 2024
Feature | Description | Related Documentation |
New Features | Added support for reverse incremental functionality for homogeneous or heterogeneous databases such as Oracle, OceanBase, and TiDB after migrating to OceanBase 4.2.0/4.2.1 versions. This is mainly used for data backflow after data migration is completed. | |
Added support for data migration with OceanBase V4.2.0/V4.2.1 as the source: supports data migration between OceanBase V4.2.0/V4.2.1 instances and from OceanBase V4.2.0/V4.2.1 to MySQL databases. | ||
Added support for scenarios with large object quantities in a single data migration project. | ||
Added support for data migration projects from OceanBase Oracle instances to Oracle databases. | Migrate data from an Oracle tenant of OceanBase Database to an Oracle database | |
Added support for data migration and synchronization projects from Alibaba Cloud RDS PostgreSQL databases to OceanBase Oracle instances. | Migrate data from an ApsaraDB RDS for PostgreSQL instance to an Oracle tenant of OceanBase Database | |
Added matching rule capabilities to database-to-database synchronization projects, helping users select synchronization objects through simple wildcard rule configurations, thereby reducing the cost of selecting synchronization objects. | ||
Added support for schema wildcard capabilities in matching rules. | ||
Added support for data synchronization projects from OceanBase MySQL instances to Kafka, enabling the output of OceanBase data to Kafka in Avro serialization format, expanding the ways users can integrate with downstream big data ecosystems. | ||
Added support for 8 new OpenAPI interfaces, mainly covering functionality modules such as RDS PostgreSQL data source, table addition and deletion, and transmission instances. | - |
October 20, 2023
Feature | Description | Related Documentation | |
New Features | New ARM Architecture Specifications Release | Released the Standard Edition (Cloud Disk) series ARM architecture clusters, supporting specifications including 16C 70GB, 32C 180GB, and 62C 400GB. The corresponding compute instance prices are approximately 18%-20% lower than the same specifications on x86, suitable for customers using different CPU architectures. | |
Overall Optimization of Cluster Configuration Change Capability | Further categorized the existing configuration change capabilities into temporary configuration changes, standard configuration changes, etc. Added the ability to convert temporary storage and specifications into permanent storage and specifications, providing more flexible adaptation to business changes for cloud customers. | ||
Enhanced Backup and Restore Capability |
| ||
August 22, 2023
Feature | Description | Related Documentation | |
New features | Automatic storage scale-out | You can configure rules for automatic storage scale-out and specify the upper limit for automatic scale-out. After the automatic storage scale-out feature is enabled, when the storage space of a cluster is about to be exhausted, the storage space can be automatically scaled out to ensure the stability of online business. This feature applies to scenarios with a large business data volume or frequent and drastic fluctuations in the business volume. | |
Access address optimization | You can add two access addresses for the multi-IDC deployment solution. If you want to add two access addresses, they must be read-only addresses. If you want to add only one access address, it can be a read-only or read/write address. | ||
Change of the minimum tenant specifications | In OceanBase Database V3.x and later, the minimum specifications for tenants in a cluster instance are changed from 2C5G (2 CPU cores and 5 GB of memory) to 1C4G (1 CPU core and 4 GB of memory). This way, a cluster can support more tenants with the same resources, thereby reducing the costs. | ||
Backup and restore enhancement |
| ||
New region available | The Germany (Frankfurt) region is available and supports the full cluster series of Standard Edition (Cloud Disk) ranging from 4C to 62C, Alibaba Cloud accounts of the China and international sites, and the pay-as-you-go and subscription billing methods. | ||
June 30, 2023
Feature | Description | Related Documentation | |
New features | Upgrade and downgrade of tenant instance specifications | Specification upgrade and downgrade are supported for tenant instances. Specifically, the specification of a tenant instance can be upgraded from 1C to 2C or downgraded from 2C to 1C. | |
Drill-down monitoring and custom monitoring | The drill-down monitoring feature can provide data of the same monitoring metric in different dimensions to assist you in routine O&M analysis. The custom monitoring feature allows you to configure general monitoring metrics on the custom monitoring panel as needed. | ||
New product | You can select three full-featured replicas (3F) for the single-IDC deployment mode. | ||
Version adaptation | OceanBase Database V4.0 is no longer available and OceanBase Database V4.1 is fully available. The corresponding 4C specification is available. | ||
New region available | The Malaysia (Kuala Lumpur) region is available. | ||
Pricing adjustment | The total prices of the 4C, 14C, and 24C cluster instance specifications are reduced. | ||
May 22, 2023
Feature | Description | Related Documentation |
New features | Schema migration, full migration, incremental synchronization, full verification, and reverse incremental migration are supported for migration from a MySQL database to a MySQL tenant of OceanBase Database V4.1.0 and for OceanBase Database tenant instances. | Migrate data from a MySQL database to a MySQL tenant of OceanBase Database |
Full verification and reverse incremental migration are supported for migration from a MySQL database to a MySQL tenant of OceanBase Database V4.0.0. | ||
Schema migration, full migration, incremental synchronization, full verification, and reverse incremental migration are supported for migration from a MySQL tenant of OceanBase Database V2.x or V3.x to a MySQL tenant of OceanBase Database V4.1.0. | ||
Schema migration, full migration, incremental synchronization, full verification, and reverse incremental migration are supported for migration from a TiDB database to a MySQL tenant of OceanBase Database. | Migrate data from a TiDB database to a MySQL tenant of OceanBase Database | |
Full migration, incremental synchronization, and full verification are supported for migration from a PolarDB-X 1.0 database to a MySQL tenant of OceanBase Database. | Migrate data from a PolarDB-X 1.0 database to a MySQL tenant of OceanBase Database | |
Nine general batch operations such as batch start and batch pause are supported to improve the overall O&M efficiency. | ||
Full synchronization and incremental synchronization are supported for migration from OceanBase Database to a RocketMQ instance of Enterprise Edition or Community Edition. | Synchronize data from OceanBase Database to a RocketMQ instance | |
Synchronization of DDL operations from OceanBase Database to a Kafka instance is supported. This way, you can promptly detect schema changes. | Synchronize data from OceanBase Database to a Kafka instance | |
The Debezium JSON format is supported for the destination Kafka, DataHub, or RocketMQ instance to facilitate interconnection with the downstream big data ecosystem. | ||
You can set the cluster ID based on the actual situation. The Default and DefaultExtendColumnType serialization methods are supported. This feature applies to business scenarios such as data cleansing and history database. | ||
You can dynamically change project names to facilitate project management. | ||
Data migration and data synchronization across different Alibaba Cloud accounts are supported. | ||
Tag-based management is supported so that you can manage projects and perform batch operations based on tags. | ||
You can remove objects that do not meet your conditions during the precheck. This facilitates project creation and improves the ease-of-use. | ||
An incremental synchronization checkpoint can be selected for incremental synchronization. This option is not supported for full migration. |
May 17, 2023
Feature | Description | Related Documentation | |
New features | Binlog | Binlog collects the transaction logs of OceanBase Database and converts them into MySQL binary logs (binlogs). This service is designed for scenarios such as real-time data subscription. The binlog service can be enabled and managed at the tenant level. A limited-time free trial is provided. | |
Multi-tenant isolation optimization | The cgroup-based isolation mechanism is supported to implement CPU resource isolation between tenants, CPU resource sharing between user tenants and meta tenants, and request priority configuration. | ||
Standard edition (key-value) | Key-value is the NoSQL model of OceanBase Database that bypasses the SQL engine and directly reads data from the storage engine. The key-value model of OceanBase Database takes full advantage of a new database architecture that integrates both NoSQL and SQL features and provides a variety of non-relational APIs that are simpler and more efficient to meet your requirements in different scenarios. At present, the key-value model supports only specifications of 32 and 64 CPU cores. | ||
Standby instance decoupling | You can decouple a standby instance from the primary cluster so that the standby instance functions as a new independent cluster. This improves resource utilization and can be performed in scenarios such as business splitting. | ||
Billing method change | You can change the billing method from subscription to pay-as-you-go. | ||
New release | OceaBase Database V4.1.0.0 is released. In this version, the 2F1A deployment mode is supported to reduce costs. | - | |
March 28, 2023
Feature | Description | Related Documentation | |
New features | Cluster instance scale-in | Users of the China or international site that choose the subscription or pay-as-you-go billing method can reduce the nodes, specifications, and storage space to scale in their cluster instances. | |
Recycle bin for databases and tables | The recycle bin stores deleted data such as databases and tables. You can restore the deleted data of databases and tables from the recycle bin. Databases and tables in the recycle bin still occupy the storage space. You can configure the automatic purging interval or manually purge it. | ||
Backup and restore | The local archive backup is supported to reduce the retention costs of long-stored backup files. Archive backup files are retained for at least 60 days. You will be charged for 60-day retention even if the retention period is shorter than 60 days. Archive backup files cannot be downloaded. | ||
March 17, 2023
Description | Related Documentation | |
ODC user guide | ODC supports static data desensitization and allows you to enable data desensitization strategies in operations such as data export and result set export. For example, ODC supports built-in desensitization rules for data such as email addresses, bank card numbers, phone numbers, ID card numbers, and names. You can configure desensitization strategies based on the valid range of ODC also allows you to configure custom desensitization rules by using desensitization algorithms such as masking, character replacement, format retaining, hashing, rounding, and null value assignment. | |
The shadow table synchronization feature is added, which automatically creates shadow table schemas in the same database based on the schemas of source tables and automatically synchronizes the schemas to the destination. | ||
The partitioning plan feature is added, which supports automatic precreation and deletion of expired RANGE partitions and RANGE COLUMNS partitions. | ||
SQL plan tasks are supported. ODC can periodically execute SQL scripts created by users to complete database development and O&M tasks as required by the users. | ||
Automatic authorization rules are added. The administrator of the public resource console can automatically assign specific roles or permissions to users that meet specified conditions when they log on to the console for the first time or when they are created, which avoids redundant authorization. For example, the administrator can authorize users whose name, organization, department, or logon method meets specified judgment conditions. | ||
SQL window optimization:
| ||
Import and export:
|
February 27, 2023
Feature | Description | Related Documentation | |
New features | Backup and restore | Remote backup files of a cluster can be used to restore the cluster to the region where the remote backup files are located. In other words, assuming that the remote backup files of cluster A are stored in the region in which cluster B is located, tenants of cluster A can be restored to cluster B by using the remote backup files of cluster A. In this case, the restore is initiated from cluster B, namely the destination cluster. Logical backup supports incremental data backup, which ensures data consistency for tables without downtime. | |
Security assessment | A security assessment menu is provided in the security settings module for you to detect and assess the overall database security based on cluster check items and tenant check items. You can configure security settings in the specified module based on the assessment suggestion. | ||
New specification available | The specifications available for scaling are adjusted, and the 104C specification is provided. However, the 104C specification is available to whitelisted users only. | ||
More nodes supported | The number of nodes is increased from 18 to 45 in 15-15-15 deployment mode. | ||
OceanBase Database V4.0 | More specifications are provided, such as 4C, 8C, 14C, 24C, 30C, 62C, and 104C. The package specifications, storage specifications, and node specifications can be scaled up to help testers and small-specification users smoothly scale up the specifications for production systems. | ||
Standby instances | You can add standby cluster instances for a primary cluster instance to form a cluster network. In this cluster network, the primary and standby instances maintain data consistency by performing asynchronous log replication. When the primary instance becomes unavailable, a standby instance can take over the services and provide the disaster recovery capability to minimize the service downtime. | ||
OceanBase Autonomy Service | The capacity risks of all existing clusters are aggregated to reflect resource usage. This helps evaluate the necessity of scaling and allows you to avoid capacity risks by taking early actions. | ||
December 9, 2022
Feature | Description | Related Documentation | |
New features | Tenant instance (MySQL mode) | A tenant instance (1C4G or 2C8G) can run as an independent database instance. You can create a database in a tenant instance and create tables in this database to provide services for upper-layer applications. This feature is designed for individual developers or scenarios that deal with a small amount of data. We recommend that you do not use this feature in high-availability scenarios such as the core business systems of an enterprise. | |
Read/Write splitting | Read/Write splitting is supported. By default, read operations are allocated to followers and write operations are allocated to leaders to implement replica-level splitting and implement load balancing across multiple endpoints and replicas, thereby implementing transaction-level splitting of read and write operations. | ||
Distributed primary zone | The distributed primary zone feature is supported in multi-node scenarios. The primary endpoint and read-only endpoints can be modified. The feature of reading and writing endpoints is added. | ||
November 28, 2022
Feature | Description | Related Documentation |
New features | Schema migration, full migration, and incremental synchronization from a MySQL database to a MySQL tenant of OceanBase Database V4.0 are supported. | |
The precheck skip feature is provided to ensure that the entire process is free of stuck. | ||
In the Specify Objects mode, you can dynamically add and remove tables to reduce resource consumption and simplify manual O&M. | ||
A self-managed OceanBase database in VPC supports advanced options, cross-network deployment, cross-cloud transmission, and migration of tables without unique keys. | ||
Transmission instances can be automatically released to save resources. | ||
Improved user experience | Monitoring the execution time of SQL statements in the full migration step is supported to help you effectively identify performance-related issues. | |
The execution time of SQL statements is displayed in the incremental synchronization and reverse incremental synchronization steps to show the performance of the migration process. |
September 19, 2022
Feature | Description | Related Documentation |
New features | Smooth migration and synchronization from MySQL 5.5 to OceanBase Database are supported. | |
Performance data and baseline data of full migration and verification are displayed to help you identify performance issues. | ||
Partition import is supported to improve the full migration performance and save the migration time. | ||
New data verification methods are supported to improve the efficiency of full verification. | ||
Unsupported incremental DDL statements can be skipped with a few clicks, which simplifies user operation and improves the process stability. | ||
The performance data of incremental synchronization can be displayed to help you identify performance issues. | ||
Statistics of DML and DDL statements in incremental synchronization can be displayed to help visually learn about the performance of the synchronization process and track the changed objects. | ||
Importing and exporting objects and object configurations in the CSV format are supported to implement batch setting and cross-environment migration, which improves work efficiency. | ||
11 general APIs are provided to meet your automation requirements at work. | ||
Cross-cloud Kafka data transmission is supported. | ||
The project-specific alert configuration guides are improved to implement real-time monitoring and subsequent assurance of a project. |
July 7, 2022
Feature | Description | Related Documentation | |
New features | OceanBase Autonomy Service | Describes how to connect to OceanBase Autonomy Service. You can connect a cluster in the running state to OceanBase Autonomy Service. | |
The real-time diagnostics feature is provided. On the real-time diagnostics page, you can view information such as the SQL running status and session analysis information. | |||
The capacity center is provided. The capacity center displays the data volume trends of system databases and tables. | |||
The security management feature is provided. This feature allows you to perform SQL audit. | |||
The optimization records feature is provided. You can query the optimization records to view the historical operations of binding plans or indexes in a cluster. | |||
July 1, 2022
Feature | Description | Related Documentation | |
New features | Data migration | Migrating data from an ApsaraDB for OceanBase Database instance in MySQL mode to a MySQL database is supported. The MySQL database can be an RDS database, ApsaraDB for PolarDB instance, a database deployed in a VPC or public network, or a database deployed by using a database gateway. | Create a project to migrate data from a MySQL tenant of OceanBase Database to a MySQL database |
Migrating data between ApsaraDB for OceanBase Database instances is supported. | Create a project to migrate data from one OceanBase database to another | ||
Migrating tables without unique keys from a MySQL database to an OceanBase database in MySQL mode is supported. | |||
Automatically creating an OceanBase database in MySQL mode is supported to migrate data from a MySQL database to the OceanBase database. | |||
Data synchronization | Synchronizing data from an OceanBase database to a DataHub instance in a VPC or public network is supported. | Create a project to synchronize data from an OceanBase database to a DataHub instance | |
Migrating data from an ApsaraDB for OceanBase instance in MySQL mode to an OceanBase database in MySQL mode (in VPC) is supported. | Create a project to synchronize data between two OceanBase databases | ||
Improvement of operation easiness | The schema migration, full migration, and full verification processes are optimized to avoid the impact of table processing failures on the running of a project. | - | |
Force conversion of character sets is supported to improve the compatibility with more character sets of data sources. | - | ||
May 31, 2022
Feature | Description | Related Documentation | |
New features | History database | To solve historical data read and update problems, the history database feature is provided to store archived data. The low-cost storage solution based on large-volume physical disks effectively reduces the storage cost of customers in storing historical data. You can also query data in the history database to enjoy high cost efficiency. | |
Support for local disk | The storage and engine of OceanBase Database can be deployed in the same node to improve the I/O performance and reduce the read/write latency, which meets the IOPS requirements of some business systems. | ||
Transparent Data Encryption (TDE) interconnection with Alibaba Cloud Key Management Service (KMS) | Hosting the TDE key by using the KMS service of Alibaba Cloud is supported, which meets the compliance requirements of regulatory authorities. | ||
Optimized features | Data transmission | The incremental migration of DDL operations from a MySQL database to a MySQL tenant of OceanBase Database is supported. Reverse incremental migration from a MySQL tenant of OceanBase Database to a MySQL database is also supported. | Create a project to migrate data from a MySQL database to a MySQL tenant of OceanBase Database |
Data synchronization to different topics in a single project is supported to improve the data synchronization efficiency. Index creation after full migration and partition-based data reads and writes are supported to improve the performance of full migration. | Create a project to synchronize data from an OceanBase database to a DataHub instance | ||
Incremental synchronization from a MySQL tenant of OceanBase Database to an AnalyticDB for MySQL (ADB) database and the automatic synchronization of some DDL operations from a MySQL tenant of OceanBase Database to an ADB database are supported. | |||
Regarding operation simplicity and user experience, the operations of renaming databases and tables are optimized, and the data volume and latency curves in incremental synchronization can be displayed. All features of the service are available in multiple languages. | |||
Data R&D | Enterprise-level management features such as task process change management, risk data judgment, operation audit, and SQL audit are supported to meet the asset security and audit requirements for user data. | ||
Adding ODP (Sharding) as a data source for a MySQL tenant of OceanBase Database is supported. The recycle bin management capability is provided. An independent session design is available in the SQL window. You can export functions and stored procedures and upload multiple script files. | |||
PL/SQL statement execution details are optimized. | |||
Regarding operation simplicity, online editing of CLOB fields that are less than 200 KB is supported. More fields such as the row number and position are displayed when a PL/SQL compilation error occurs. All features of the service are available in multiple languages. | |||
May 13, 2022
In the first release of OceanBase Migration Assessment (OMA) for the public cloud, both online and offline assessment methods are provided. You can select an assessment method based on the network and resource status: directly connect to an instance or upload files to perform compatibility assessment and SQL assessment. OMA allows you to generate assessment reports in HTML or PDF format. The operations are simple. You can go to the ApsaraDB for OceanBase console to have first-hand experience.
Feature | Description | Related Documentation | |
New features | First release of OMA for public cloud | OMA is a database compatibility assessment tool provided by OceanBase Database. OMA provides precise compatibility assessment, SQL assessment, and application reconstruction suggestions for data migration to OceanBase Database. It helps migrate data to a distributed OceanBase database efficiently and smoothly. | |
April 20, 2022
Feature | Description | Related Documentation | |
Feature upgrades | OceanBase Database data synchronization to AnalyticDB | Synchronizing data from a MySQL tenant of OceanBase Database to an AnalyticDB instance is supported. Schema synchronization, full synchronization, and incremental synchronization are supported. Database and table renaming, partitioning key and distribution key customization, and the synchronization of some DDL operations are supported. | |
March 20, 2022
Feature | Description | References | |
New features | SQL audit | Auditing SQL records by database, node, keyword, time range, username, and operation type in the cluster console is supported in internal compliance scenarios. You can also export the SQL records. | |
Quick scale-out of enhanced SSD | Quick scale-out of enhanced SSD is supported to improve customer experience. | ||
OceanBase Database data synchronization to Kafka | Synchronizing data of an OceanBase Database instance to a Kafka instance on Alibaba Cloud is supported. You can create a Kafka instance in a VPC. Five JSON serialization message formats are available. | Create a project to synchronize data from an OceanBase database to a Kafka instance | |
December 8, 2021
Feature | Description | Related Documentation | |
New features | Commercialization of backup and restore | The backup and restore feature of ApsaraDB for OceanBase is free. However, the backup files will occupy storage space, which is provided by Object Storage Service (OSS). After you purchase an OceanBase cluster, a backup and restore order is generated for you. | |
Service account authorization | You can use the service account authorization feature to grant permissions such as the configuration, query, and data permissions to technical support engineers at Alibaba Cloud. | ||
November 8, 2021
Feature | Description | Related Documentation | |
New | New APIs | You can manage clusters by using APIs, including APIs for creating and deleting tenants, users, and databases in a cluster. You can manage OceanBase clusters on the original system O&M platform. | |
Permission management in OceanBase Developer Center (ODC) | DBAs can configure permissions of general users, including creating personal connections, accessing public connections, and reading/writing public connections. | ||
Data synchronization between MySQL tenants of OceanBase Database | Synchronizing physical or logical tables from a MySQL tenant of OceanBase Database to another MySQL tenant is supported. | Create a project to synchronize data between two OceanBase databases | |
August 19, 2021
Feature | Description | Related Documentation | |
New | 8C32G server | 8C32G servers are available for sale in the non-financial zones in Hangzhou. The servers can be deployed in a single IDC. | |
Deployment of a tenant in multiple units | When you create a tenant, you can specify the number of units to deploy the tenant in the units. This improves the distributed capability of the tenant. | ||
Data synchronization | The data synchronization feature allows you to synchronize data between an OceanBase physical table and a created Kafka data source or RocketMQ message queue in real time, extending the message processing capability. It also supports real-time data synchronization between Sybase ASE and created RocketMQ terminals. | ||
Others | Improvement of product operation easiness | The cluster and tenant management feature is changed to the graphical form to show you clear O&M information. | - |
OceanBase Database as a data source in Quick BI/DataV | ApsaraDB for OceanBase allows you to use OceanBase Database as a data source in Quick BI and DataV and perform data interaction in the internal network. | - | |
July 19, 2021
Feature | Description | Related Documentation | |
Database development and management | DBMS output in the SQL window | Database management system (DBMS) output is supported in the SQL window. After you execute PL/SQL statements in the SQL window, the returned information of the DBMS statement is displayed on the result tab. | |
Result set interaction optimization | You can drag column names in a result set to adjust the sequence of the columns, and filter and arrange fields based on their values. The Copy and Set to Null buttons are provided. | ||
Schema switchover | In Oracle mode, you can open a connection and change the schema in the top navigation bar of the workspace. | ||
Asynchronous execution | The asynchronous execution tool is added to Tools. Statements in the SQL window are executed synchronously, and the execution may time out when the statement runs for a long time. You can use the asynchronous execution tool to run time-consuming SQL statements to avoid execution timeout. | ||
Data mocking | ODC provides the data mocking feature that can generate data based on field types in a table. This can meet your requirement for generating a large amount of data during database performance tests or feature verification. | ||
June 16, 2021
Feature | Description | Related Documentation |
Support for log replicas | This feature allows you to set the third replica as a log replica. It improves cost efficiency in terms of storage and computing resource consumption without affecting the performance. | |
Security group whitelist group | You may create and edit whitelist groups. | |
SSL link encryption | ApsaraDB for OceanBase supports SSL link encryption to ensure secure data transmission between clients and servers. | |
TDE | ApsaraDB for OceanBase supports transparent data encryption (TDE) for data flushed to disks. | |
User experience optimization | The monitoring capability is improved, and the user experience of performing list and search operations is also optimized. For details, log on to the OceanBase console. | - |
April 12, 2021
Feature | Description | Related Documentation |
Basic edition series services | A new billing method is provided, in which the storage fees are charged based on the actual usage on an hourly basis. | |
Optimization of the backup and restore feature |
| |
Major compaction | Manual compaction of cluster data is supported. |
January 28, 2021
Feature | Description | Related Documentation |
Tenant parameter management | You can view the parameters and parameter modification history of a tenant and can modify the parameters. | |
Support for vertical scaling, storage space scale-out, and subscription |
| |
Resource tagging | You can select up to 10 tags for each cluster. You can use the Manage Tags feature to create or delete tags. | |
Database development and management | The Config URL connection mode is canceled for OceanBase Database in MySQL mode. | |
The method for changing the connection password is optimized. | ||
Execution plans can be viewed in text. |
December 23, 2020
Feature | Description | Related Documentation |
Cluster parameter management | The parameter management feature is provided. You can view the parameters and parameter modification history and can modify parameters. | |
Support for disk space usage display | The node data of clusters is monitored and the disk space usage is displayed. | |
Account privileges | Several account privileges are added, and user privilege configuration is supported in RAM access control. | |
Multi-zone support | If you choose a multi-IDC deployment plan, you can deploy three nodes in three different availability zones (AZs) to achieve zone-level disaster recovery. This does not incur additional charges. |
December 8, 2020
Feature | Description | Related Documentation | |
Monitoring and alerting | You can create alert rules and view, add, modify, and disable alert rules. | ||
Whitelist modification entry optimization | The whitelist modification entry is added to the page to facilitate whitelist management. | ||
Display of the subscription expiration date | The service subscription expiration date or status is displayed. | ||
Database development and management | Program package object creation and management | Program package objects can be created and managed in a visualized manner. | |
Sequence object creation and management | Sequence objects can be created and managed in a visualized manner. | ||
Table creation optimization |
| ||
SQL window optimization |
| ||
Anonymous block window | The anonymous block window is a work area for database developers to edit anonymous block scripts and edit and execute PL/SQL statements. | ||
Connection creation optimization | Advanced information can be configured. The timeout period and users with the privilege to access sys views can be customized. | ||
Connection management optimization |
| ||
Session management |
| ||
Recycle bin management |
| ||
Database object management improvement |
| ||
SQL console feature improvement |
| ||