Notice
- Before you upgrade ODC from a version earlier than V4.2.0 to V4.3.4-BP3, you must read through the description in the Considerations section of this topic.
- Before you use ODC V4.3.4-BP3, pay attention to the limitations on the capabilities of ODC V4.3.4-BP3. For more information, see Limitations.
Considerations
Data sources
In ODC V4.2.0 and later, the concept of connection configuration is replaced with data source.
The creation of ODP data sources is not supported in ODC V4.2.2.
In ODC V4.2.0 and later, private connections are migrated to the individual workspace and managed as data sources.
In ODC V4.2.0 and later, public connections are migrated to the team workspace and managed as data sources.
In ODC V4.2.0 and later, for the read-only and read/write accounts in original public connections, only the read/write accounts are retained after the upgrade.
User privileges
The private_connection and apply_connection roles are unavailable in ODC V4.2.0 and later. The privileges of the two roles referenced by users no longer take effect.
Resource groups are unavailable in ODC V4.2.0 and later.
Connection access privileges are unavailable in ODC V4.2.0 and later. Database access control is implemented through project management.
System settings
- System settings are unavailable in ODC V4.2.0 and later.
Ticket module
- Tickets initiated in versions earlier than ODC V4.2.0 can be viewed only on the Initiated by Me tab.
Partitioning plans
- Historical partitioning plan tasks created in versions earlier than ODC V4.2.0 will stop running.
SQL plans
- Historical SQL plan tasks created in versions earlier than ODC V4.2.0 will stop running.
Task process
- The task process feature is unavailable in ODC V4.2.0 and later. Risk levels are used to achieve the same effect.
Data desensitization
- The data desensitization settings made in versions earlier than ODC V4.2.0 no longer take effect.
Session history
- The session history feature is unavailable in ODC V4.2.0 and later. After the upgrade, the usage status of the SQL window is saved by default.
ODC V4.3.4-BP3
Current version: V4.3.4-BP3
Previous version: V4.3.4-BP2
Release date: August 01, 2025
Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.
Feature updates
Database changes
You can modify the default configuration for creating a database change ticket.
You can view the result set of a database change ticket.
Others
- After integrating the bastion host into the SQL console resource tree, the SQL window of the target database is automatically opened.
ODC V4.3.4-BP2
Current version: V4.3.4-BP2
Previous version: V4.3.4
Release date: June 18, 2025
Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.
Bug fixes
SQL development
Modified the PL debug timeout period to be a parameter.
Fixed the issue that the frontend button is unobstructed when the table data is modified.
Database changes
Fixed the issue that an npe exception is no longer thrown when the original table structure cannot be obtained during database changes.
Fixed the issue that database changes fail to terminate tasks when generating regression plans.
Fixed the issue that a user without the permission to change the logical database can successfully initiate a logical database change task.
Data archiving and cleanup
Fixed the issue that the option "Enable Target Table Schema Synchronization" selected when creating a data archiving task cannot be deselected.
Fixed the issue that the related configurations are not disabled when object storage is selected for data archiving.
Fixed the issue that the tables are skipped when a data archiving task is canceled due to execution timeout.
Projects
Fixed the issue that the roles are displayed as numbers when edited.
Fixed the issue that the the interface probabilistically does not respond when an unauthorized user creates a view.
Others
Fixed the issue that the SAML test login address is incorrect.
Fixed the issue that the frontend probabilistically crashes during searches in databases.
Fixed the issue that some parameters are not synchronized when a task is re-initiated.
ODC V4.3.4
Version information
Current version: V4.3.4
Previous version: V4.3.3-BP2
Release date: May 09, 2025
Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.
This iteration focuses on enhancing the following three areas:
- Quick Start: Introduced a workspace that includes the Overview, Quick Start Guide, Recently Accessed Databases, About Us, and Best Practices modules to help users quickly understand the core services of ODC. Also improved the empty object process guidance, global search, locate key, and database grouping features.
- Configuration Center: Upgraded the configuration center with personal and team space configurations. Defined the dependencies, scenarios, and priorities of various configuration levels (space level, environment level, user level, and feature level). Added 6 space-level configurations to meet customer needs.
- Feature Enhancements: Added support for materialized view management. Data archiving now supports multi-table association. Partitioning plans support the creation of INT/Char partitioned fields with sequential incremental partitions. Implemented column DDL operations under lock-free structural changes. For more information about this version, see the version change list.
Feature updates
Quick Start
The team workspace now includes a workspace that contains five modules: task overview, quick start, recently accessed databases, about us, and best practices. This workspace guides users through the quick start process and showcases the core services and advantages of ODC.
The process of guiding users on what to do when the feature page has no data is more complete. This solves the problem of users not knowing how to use ODC when they log in for the first time.
The global search capability is improved. Users can search for databases, projects, and data sources.
The primary key capability is improved. The global search and database object page primary keys can locate specific database objects. The team workspace now includes an SQL console entry, which allows users to quickly access the SQL console.
Database list
The database grouping capability is added. Users can group databases in the resource tree, database list in projects, database selection in SQL windows, and database selection when creating tickets based on projects, data sources, clusters, tenants, database types, and environments. The grouping conditions can be persistently saved to allow users to define their own grouping preferences.
The database search capability is improved. Users can search for databases in the resource tree, database list in projects, database selection in SQL windows, and database selection when creating tickets based on databases, data sources, clusters, and tenants.
The database annotation capability is added. Users can manage database annotations in the database list page in projects. The annotation information can be displayed in the resource tree, database list in projects, database selection in SQL windows, and database selection when creating tickets. When the pointer hovers over a database, the database details, including the annotations, are displayed to help users identify databases with the same name.
Configuration center
The configuration center is upgraded. The concept of space configuration, including personal space and team space, is added to constrain the configurations of modules in the space.
The dependencies, application scenarios, and priorities of ODC configurations at different levels (space level, environment level, user level, and feature level) are clarified to ensure logical consistency.
Six new configurations are added to space configurations:
Maximum number of SQL queries allowed: This configuration limits the maximum number of result sets that can be obtained in SQL query scenarios in the space.
Default value of SQL queries: This configuration provides the default number of result sets that can be obtained in SQL query scenarios in the space.
Allow schema replacement in import tickets: This configuration limits whether to enable the schema replacement option when importing tickets.
Default generation of backup rollback plans for database changes: This configuration provides the default value for whether to automatically generate rollback content for database changes.
Define task description prompt: This configuration defines the prompt for the task description to guide users on how to fill in the remarks.
Define data source key: This configuration allows users to modify the data source key for a more secure key encryption strategy.
The configurations in the original [Settings] module are adjusted to user configurations. The [Result Set Row Limit] configuration is dropped. It is replaced by the [Maximum Number of SQL Queries Allowed] and [Default Value of SQL Queries] configurations in space configurations. This iteration only provides global search. Therefore, the [Enable Global Object Retrieval] configuration is dropped.
The configurations are standardized. The original environment-level configuration [Maximum Number of Rows in Result Set Returned by SQL Window] is adjusted to [Maximum Number of SQL Queries Allowed in SQL Window].
SQL development
The management of materialized views on the GUI is supported. Users can create, view, and manage materialized views on the GUI.
The support for script batch download is added.
The support for displaying the object DDL statement when the pointer hovers over the object name in the SQL window is added.
Data archiving
The support for multi-table associated archiving is added. Users can define multi-table associated archiving conditions.
The support for archiving tables with generated columns is added.
A new data cleanup exception handling mechanism is added. Users can choose to skip, update the target database, or fail the task when encountering exceptions. This solves the problem of poor fault tolerance, where the feature is directly terminated when exceptions occur during data cleanup.
Partitioning plans
- The creation method of INT/CHAR partitioned fields with sequential incremental partitions is supported. This greatly reduces the partitioning strategy configuration cost for INT/CHAR partitioned fields.
Lock-free schema changes
- The support for DDL changes in the column deletion scenario is added.
Collaborative development
The number of affected rows by DML changes is displayed in database change tickets. This allows users to assess the change risks.
The support for merging database and table permission application tickets is added. If the requested databases hit the same approval flow, the tickets are merged into one.
The approval flow hit rule for database and table permission application tickets is upgraded. The approval flow is determined based on the risk level identified by matching the risk identification rules in the security specifications.
The authorization mechanism is improved. Users can manage the data sources and users they created.
The support for batch setting administrators for databases in projects is added.
Task framework
The task framework is upgraded. The new task framework:
Abstracts the access methods into a unified resource module.
Provides flexible resource control strategies with customizable resource implementations that balance costs and startup speed.
Optimizes the state machine module. Task driving is changed to single-node driving to reduce database access pressure and lock competition.
Optimizes the logic of several abnormal states to reduce the impact of concurrent access on task states.
Persistently stores task allocation information. This allows you to track the scheduling time and status of tasks through the database, enabling effective alerts.
Others
The V4.2X series of OceanBase is adapted to V4.2.5 BP3, and the V4.3.X series is adapted to V4.3.5 BP1.
The OBLOADER and OBDUMPER components are upgraded to V4.3.3 BP1.
The changes in logical databases, partitioning plans, and shadow table tickets are supported.