January 21, 2026
This release enhances cross-cloud disaster recovery capabilities for multi-cloud deployments, expands channel and product offerings, and extends Open API functionality. We have also optimized console operations and security compliance features to improve database management efficiency and usability in multi-cloud environments.
Channels and products
- Alibaba Cloud Government Cloud now supports multiple disk configuration strategies, displayed in priority order.
- Shared storage instances can now be converted from pay-as-you-go to subscription billing.
- Binlog service now supports a new billing model based on elastic computing units.
Database disaster recovery architecture
- Cross-cloud primary and standby instances: We now support one-primary-three-standby deployment configurations with global endpoint and network monitoring capabilities.
- Alibaba Cloud Marketplace (China and International) now supports remote backup.
- Backup and restore: We have optimized page performance to reduce timeout risks during long-running backup operations. The restore process now includes a "Tenant in Restore" status and supports automatic expansion of backup storage space.
Database O&M
- Parameter template selection is now required when creating tenants to prevent configuration mismatches that can occur when using the default parameter template.
- Tenant parameter management now supports modifying the
sql_modeparameter for each tenant. - We have improved the object display and navigation experience on the alert details page.
- Account names created in Oracle-compatible tenants are now automatically converted to uppercase.
- Random password generation no longer includes the
@and:special characters. - Binlog subscription time is now consistently displayed in seconds to prevent monitoring inaccuracies.
- We have added new entry points for the standalone ODC console:
- ODC for OceanBase Cloud (China):
console-odc-cn.oceanbase.com - ODC for OceanBase Cloud (International):
console-odc.oceanbase.com
- ODC for OceanBase Cloud (China):
Network and database proxy
- For the Alibaba Cloud channel, database proxy now supports zone switching.
- The Alibaba Cloud channel now supports modifying database address domain name prefixes.
- For the Tencent Cloud channel, database proxy now supports architecture upgrades. After upgrading, you can adjust database proxy resources.
Orders and Billing
- Identity verification is now required before placing orders.
- We have improved the user experience for exporting monthly billing statements.
- We have optimized the billing logic for instance specification changes.
- Invoice management now supports deferred invoicing. After a refund, issued invoices do not need to be returned. For subsequent invoicing, deferred amounts must be offset first.
Open API
- We have added new Open APIs for SQL diagnostics, including SQL samples, history, and session management.
- New API:
DescribeRestorableTenantsfor querying information about tenants available for restore. - New API:
DescribeTenantAddressInfofor querying endpoint information for all tenants. - New APIs for security groups and IP allowlists:
ModifySecurityIps,CreateSecurityIpGroup, andDeleteSecurityIpGroup. - New API:
DescribeTenantEncryptionfor querying tenant encryption information.
January 7, 2026
This release introduces new data migration tasks between PostgreSQL, TiDB, and OceanBase Database, expands support for database migration to the cloud, and provides independent data validation and tag management features. It also enhances task management, improves the stability of migration validation tasks in multi-cloud environments, and boosts the flexibility and stability of data operations.
New data migration tasks
This release introduces new data migration tasks from PostgreSQL to OceanBase Database (MySQL and Oracle compatible modes) and from TiDB to OceanBase Database (MySQL compatible mode). These tasks support schema migration, full migration, and incremental synchronization, helping you quickly migrate data from PostgreSQL and TiDB to OceanBase Database. Additionally, new data migration tasks from OceanBase Database (MySQL and Oracle compatible modes) to PostgreSQL and from OceanBase Database (MySQL compatible mode) to TiDB are introduced, supporting incremental synchronization. These features allow you to synchronize data from other databases to OceanBase Database and then back to the source databases, meeting disaster recovery and business continuity requirements.
New data validation capabilities
In this release, data validation is separated from the data migration process and can be configured independently. This allows for more flexible operations without relying on the data migration workflow. In addition to full data validation, row count validation is now supported. This feature enables you to verify data by comparing the number of rows in table objects, significantly speeding up the validation process. Currently, full data validation and row count validation are supported for the following task types: MySQL -> OB_MySQL, OB_MySQL -> MySQL, OB_MySQL -> OB_MySQL, Oracle -> OB_Oracle, OB_Oracle -> Oracle, OB_Oracle -> OB_Oracle, PostgreSQL -> OB_Oracle, PostgreSQL -> OB_MySQL, and TiDB -> OB_MySQL.
Tag management capabilities
This release integrates tag management with data migration and data validation. Using the tag management feature on OBCloud, you can add tags to data migration and data validation tasks and filter tasks by tag on the task list page. This helps you better manage data migration and data validation tasks based on business attributes.
Stability enhancements
For data migration tasks with a PostgreSQL database as the source, incremental synchronization now defaults to using unique keys on the target database to determine conflict matrices. This avoids data quality issues caused by incomplete schema information in PostgreSQL database logs.
The incremental synchronization logic has been optimized to resolve the issue where original incremental DDL synchronization would block all subsequent DML executions. The serialization logic has been refined to the table level, meaning that DDL synchronization no longer blocks DML synchronization for unrelated tables.