ODC V4.4.2

Version description

ODC 4.4.2 focuses on enhancing job management capabilities, SQL development, component performance optimization, and data source expansion and security reinforcement.

• Enhanced job and ticket management: The job module now supports batch import/export and batch termination, enabling cross-environment data migration and batch task maintenance. Partitioning strategies have been optimized for improved structural security and deletion verification. Data archiving/cleanup tasks now include tagging and throttling configurations to enhance manageability. The ticket module also supports batch termination of unfinished tickets and fixes an issue with the import drawer display.

• SQL development and component performance optimization: SQL development now supports sorting for Oracle time types, and resource tree searches can match keywords. Component management has been optimized for OB parser performance, significantly reducing SQL parsing time, and the OB Driver version has been upgraded.

• Data source expansion and security reinforcement: New data sources now support MySQL and OBMySQL connections via seekdb. Security has been enhanced by fixing a vulnerability in the ODC 1-Click client takeover feature.

For more information on the version, please refer to the feature updates.

Considerations

• Upgrade instructions

  • Make sure that your ODC version is V4.3.0 or later. Otherwise, upgrade it to V4.3.0-V4.4.0 first.
  • When you upgrade ODC V4.3.x to V4.4.x, historical data migration and changes are involved. Before the upgrade, back up the metadata database.

• Upgrade window

  • This upgrade involves the migration of historical data of scheduled task tickets. If your historical data is large, the migration will take longer. It is known that migrating 1 million tickets takes 20 minutes. Therefore, schedule the upgrade during a business idle window.
  • To minimize the upgrade time, follow the Pre-upgrade operations section in Preparations for upgrade to migrate historical data first, then proceed with the upgrade.

• Tickets

  • If there are uncompleted tickets before the upgrade, they may be canceled.

• Scheduled tasks

  • This upgrade migrates four types of tickets (data archiving, data cleanup, SQL plans, and partitioning plans) to the job module.

  • If there are uncompleted approval flows during the upgrade, the approval flows may be terminated after the upgrade.

  • If there are open windows for data archiving, data cleanup, partitioning plans, or SQL plans in the SQL console before the upgrade, error prompts may appear after the upgrade. After the upgrade, the error prompts will no longer appear when you reopen the windows.

  • Partitioning plans

    • After the migration, the new job numbers will be different from the original ticket numbers.
    • Partitioning plans that have not been approved (pending approval, expired, or rejected) will not be displayed in the job list.
    • Partitioning plans with empty partition strategies will not be displayed in the job list.

  • Execution records

    • After the migration, the execution record numbers in the new jobs will be different from the original ones.
    • If there are uncompleted execution records for partitioning plans or SQL plans, the execution record status after the upgrade may not match the actual situation. You can correct the data after the upgrade. For more information, see the Correct data section in Upgrade verification.
    • The historical execution records of partitioning plans and SQL plans will still be displayed in the database change list. If you want to hide them, you can do so after the upgrade. For more information, see the Hide data section in Upgrade verification.

• Logical database changes

  • After the upgrade, historical data of logical database change tickets will no longer be available. You can retrieve the historical change data from the metadata database. For more information, see the Check the history of logical database changes section in Upgrade verification.

ODC V4.4.2

• Current version: V4.4.2

• Previous version: V4.4.1-bp1

• Release date: March 23, 2026

• Supported upgrade path: You must first upgrade ODC V2.0.0 and later to V4.3.0–V4.4.0 before you can upgrade it to this version.

Feature updates

• Job module

  • Jobs support batch import and export, facilitating data migration between different environments.

  • Unfinished jobs can be terminated in batches, simplifying batch maintenance of job tasks.

  • Partitioning plans

    • The partition maintenance strategy for the same scheduling cycle is fixed to "add first, then delete," ensuring the security of the partition structure.
    • It is clearly stated that the product does not support secondary non-templated partitions, avoiding user confusion.
    • The partition deletion strategy now includes a retention time check, providing dual verification for secure partition deletion.
    • The partition creation strategy allows new partitions to copy the statistical information from existing partitions, ensuring the stability of the execution plan.

  • Data archiving/cleanup

    • Data archiving/cleanup tasks can be marked with the ob_org_cluster_id value, facilitating filtering and screening downstream.
    • Flow control parameters (CPU, memory, row, and data size limits) can be configured at the task level, ensuring user optimization flexibility.

• Ticket module

  • Fixed the issue where the import ticket drawer was too small to display all information.
  • Supports batch termination of unfinished tickets, simplifying batch maintenance of ticket tasks.

• SQL development

  • Supports sorting of Oracle time types in the table component.
  • Improved search interaction in the resource tree, supporting name keyword matching to shorten the search path.
  • Added SQL query result count check configuration items to ensure the validity of space and environment-level constraints.

• Component management

  • Optimized the performance of the OB parse parser, significantly reducing SQL parsing time (involving features such as SQL window execution and ticket pre-checks).
  • Upgraded the OB Driver version.

• Data sources

  • ODC supports connecting to seekdb through MySQL or OBMySQL data sources.

• Security

  • Fixed the 1-Click client takeover vulnerability in ODC.