Notice
- Before you upgrade ODC from a version earlier than V4.3.0 to V4.5.1, read through the Considerations section of this topic.
- Before you use ODC V4.5.1, note the product capability limitations. For more information, see ODC V4.5.1 product capability limitations.
Considerations
Upgrade instructions
Ensure that your ODC version is 4.3.0 or later. If not, upgrade it first to 4.3.0–4.4.0.
Upgrading from 4.3.x to 4.5.1 involves migrating and changing historical data. Back up the metadata database before you upgrade.
Upgrade window
This upgrade involves migrating historical data for scheduled tasks. If your historical data volume is large, the migration time will also increase accordingly. Migrating one million tickets is known to take 20 minutes. Schedule the upgrade during an idle business window as appropriate.
To minimize the upgrade time, follow the documentation to migrate historical data first, then perform the upgrade.
Ticket tasks
- If there are unfinished (pending approval, pending execution, or in progress) tickets before the upgrade, they may be terminated or fail to execute.
Scheduled tasks
In this upgrade, four types of tickets—Data Archiving, Data Cleanup, SQL Plan, and Partitioning Plan—are migrated to the Jobs module.
For all scheduled tasks, if there are unfinished approval workflows during the upgrade, these workflows may be terminated after the upgrade.
If any windows for Data Archiving, Data Cleanup, Partitioning Plan, or SQL Plan were open in the SQL console before the upgrade, error messages may appear after the upgrade when you reopen those windows. Reopening the corresponding windows will no longer result in errors.
Regarding partitioning plans:
- After migration, the new job number for a partitioning plan will differ from the original ticket number.
- Partitioning plans that failed approval (pending approval, approval expired, or approval failed) will not be displayed in the job list.
- Partitioning plans with an empty partitioning strategy will not be displayed in the job list.
Regarding execution records:
- After migration, the numbers of historical execution records in the new job for a partitioning plan or SQL plan will differ from the original execution record numbers.
- If there are unfinished execution records for a partitioning plan or SQL plan, their status may become inconsistent with the actual situation after the upgrade. You can run a script after the upgrade to correct the data.
- Historical execution records for partitioning plans and SQL plans will still be displayed in the database change list. If you do not want them to be displayed, you can run a script after the upgrade to hide the data.
Logical database changes
- After the upgrade, you cannot view historical data of change tickets for logical databases. You can run scripts to obtain historical change data from the MetaDB.
ODC V4.5.1
Current version: V4.5.1
Previous version: V4.5.0 BP1
Release date: November 03, 2026
Supported upgrade path: You can directly upgrade from ODC V4.4.0 and later versions to this version.
Feature updates
Project management
Project creation, editing, and listing now support project tags.
The project list supports filtering by tag.
Roles can manage project permissions in batches based on project tags, supporting both "AND" and "OR" strategies.
Approval flow
Supports configuring approval flows at the project level, including external integration approvals.
If a project does not have an configured approval flow, it automatically inherits the global approval flow, maintaining the existing project behavior.
The page displays the effective source of the current approval flow, facilitating troubleshooting and auditing.
Database objects
- Visual table creation now supports the
VECTORfield type.
- Visual table creation now supports the
Data lifecycle
- Optimized sparse data reading for OBMySQL: Primary shards use streaming reading to reduce empty reads caused by large primary key spans, improving data archiving and cleanup efficiency.
Partitioning plans
Added syntax scope hints for custom partition name expressions.
Fixed an issue where the partition name in the preview SQL might be
nullwhen using an ascending order strategy for a timestamp-type partitioning key.Fixed an issue where the expression generated an abnormal partition name when the upper bound of a partition contained a hyphen.
Optimized the processing and display of historical deleted partition configurations.
Enhanced parsing compatibility for table-level columnar storage and multi-valued JSON index tables.
Import and export
Upgraded obloader and obdumper to version 4.3.7-RELEASE.
Fixed the issue where spaces were not correctly preserved after importing an SQL file when the
UPDATEstatement contained spaces.Fixed the issue where exporting query results from native Oracle failed.
Fixed the issue where masked data was marked as dirty data due to GroovySystem initialization failure in specific environments.
SQL/PL
Fixed the issue where incorrect syntax caused asynchronous import failures when using the
/separator in complex package bodies.Fixed the issue where execution failures occurred for some stored procedures due to parsing differences.
Fixed the issue where execution results of extremely long SQL statements triggered the JSON string length limit.
External integration and login
Fixed the issue where some approval tickets behaved abnormally after the upgrade.
Fixed the issue where response validation failed when a BPMS approval variable contained
database.owner.accounts.Fixed the issue where custom fields for single sign-on could not be configured with array values.
Unified the naming of "System Integration" in permission configurations with "External Integration" on the page.
Message notification
- Fixed the issue where no notification was sent after a data cleanup task timed out.
Join a project
Fixed the issue where the OceanBase icon was not displayed on the create data source page when the data source list was empty.
Fixed the issue where the page would become stuck when uploading multiple attachments simultaneously for a database change ticket.
Bug fixes
- Fixed the issue where approval ticket processing is abnormal after upgrading ODC to 4.5.0 BP1.
- Fixed the issue where SHOW CREATE TABLE fails to parse for OceanBase MySQL-compatible mode tables with columnar storage or multi-valued JSON indexes, incorrectly reporting "Unsupported db table".
- Fixed the issue where
select /*+ hint*/ from tablecannot be parsed correctly. - Fixed the issue where an initialization failure of GroovySystem during result set export causes errors in the desensitization phase and marks all data as dirty.
- Fixed the issue where exporting a result set via native Oracle format fails.
- Fixed the issue where uploading multiple attachments for a database change task gets stuck.
- Fixed the issue where the OB icon is not displayed when creating a data source if the data source list is empty.
- Fixed the issue where JSON array variables used in BPMS approvals are incompatible with the comma-separated string format used by external BPMS.
- Fixed the issue where no notification is sent when a data cleanup job times out.
- Fixed the issue where the name "System Integration" for user permission allocation does not correspond to the actual page display "External Integration".
- Fixed the issue where, for a partitioning key type of TIMESTAMP, if the existing partition is later than the current time and the partition interval is greater than 1, the upper bound of the pre-created partition is incorrect.
- Fixed the issue where, for a partitioning key type of DATE, if the partition upper bound contains hyphens, using sequential increment for partition creation and creating the partition name with an expression results in incorrect partition creation.
- Fixed the issue where, for a partitioning plan, if the existing partition is later than the current time, using an expression containing
now()leads to incorrect pre-created partitions.
Dependency component versions
Component |
Version |
|---|---|
| OceanBase Client (driver) | 2.4.16 |
| obloader/obdumper (export components) | 4.3.7-RELEASE |
| h2 (desktop database) | 2.3.232 |
| JDK | JDK 17 |
| Springframework | 6.2.19 |
| Springboot | 3.5.13 |