ODC V4.3.2

Considerations

• Data sources

  • In ODC V4.2.0 and later, the concept of connection configuration is replaced with data source.

  • In ODC V4.2.0 and later, private connections are migrated to the individual workspace and exist as data sources.

  • In ODC V4.2.0 and later, public connections are migrated to the team workspace and exist 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 permissions

  • Starting from ODC V4.2.0, the private_connection and apply_connection roles are unavailable. In other words, the permissions of the two roles referenced by users no longer take effect after the upgrade to ODC V4.2.x.

  • Starting from ODC V4.2.0, the resource group feature is obsolete.

  • Starting from ODC V4.2.0, connection access permissions are obsolete. In ODC V4.2.x, database access control is implemented through project management.

• System settings

  • Starting from ODC V4.2.0, this feature is obsolete.

• Ticket module

  • Tickets initiated in versions earlier than ODC V4.2.0 can be viewed only on the Initiated by Me tab.

• Partitioning plans

  • This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, historical partitioning plans created in versions earlier than V4.2.0 will stop running.

• SQL plans

  • This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, historical SQL plans created in versions earlier than V4.2.0 will stop running.

• Task process

  • Starting from ODC V4.2.0, this feature is obsolete. ODC V4.2.x provides the risk level module for equivalent effects.

• Data desensitization

  • This feature is upgraded in ODC V4.2.0. After the upgrade to ODC V4.2.x, the data desensitization configurations created in versions earlier than V4.2.0 no longer take effect.

• Bastion host integration

  • In ODC V4.2.2, account integration and automatic data source configuration are supported. At present, SQL approval integration is not supported and will be supported in later versions.

• Session history

  • Starting from ODC V4.2.0, this feature is obsolete. In ODC V4.2.x, the usage status of an SQL window is saved by default.

ODC V4.3.2-BP3

Version information

• Current version: V4.3.2-BP3

• Previous version: V4.3.2-BP2

• Release date: January 3, 2025

• Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.

Bug fixes

• Data archiving

  • Fixed an overflow issue with TINYINT during native MySQL to native MySQL archiving.

  • Fixed a null pointer error in archiving caused by the current value of a numeric column being null when the previous column was empty.

  • Fixed an issue where archiving failed due to null values in TIMESTAMP fields.

• SQL development

  • Fixed a null pointer error that occurred when executing SQL after upgrading from a lower version with custom environments to ODC 4.3.2-BP1.

ODC V4.3.2-BP2

Version information

• Current version: V4.3.2-BP2

• Previous version: V4.3.2-BP

• Release date: December 23, 2024

• Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.

Bug fixes

• Data archiving

  • Fixed a mapping issue with time-type fields in MySQL to OceanBase MySQL archiving tasks that caused task failures.

  • Fixed a timeout issue in Oracle mode archiving for large tables caused by a short HINT timeout setting.

  • Fixed an issue where the condition matching strategy did not take effect in MySQL mode archiving.

  • Fixed a slow query issue when setting composite vector filter conditions in OceanBase MySQL mode archiving.

• Partitioning plan

  • Fixed an issue where the database change subtask status did not match expectations when Errors and Continue was selected in the partitioning plan.

• Online schema change

  • Fixed data loss caused by the lock user command not taking effect during online schema changes.

ODC V4.3.2-BP

Version information

• Current version: V4.3.2-BP

• Previous version: V4.3.2

• Release date: October 30, 2024

• Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.

Bug fixes

• Data sources

  • Fixed an issue where environment labels in projects were not updated after modifying them in data sources.

  • Fixed an error when opening the SQL console after adding custom environment labels to a data source.

  • Fixed a PL debugging error that occurred when there were both deleted and non-deleted databases with the same name under the same data source.

• Data archiving

  • Fixed an issue where the specified condition matching strategy in data archiving did not take effect.

  • Fixed a timeout error during archiving in OBOracle mode.

  • Fixed an issue where archiving failed due to inconsistent field order between source and target in OBMySQL mode.

• Database objects

  • Fixed the overly narrow right-click menu in the object tree.

ODC V4.3.2

OceanBase Developer Center (ODC) V4.3.2 released in September 2024 enhances the following features:

• Support for logical databases: ODC V4.3.2 introduces new logical database features to provide a quick, reliable, and easy-to-use change basis for database and table sharding. The new features include logical database configuration, access privilege management, logical table obtaining and creation, and execution of data definition language (DDL) changes.

• Archive link extension: ODC V4.3.2 adds two archive links to support archiving data from an Oracle database to an Oracle tenant of OceanBase Database and from a PostgreSQL database to a MySQL tenant of OceanBase Database, on the basis of the archive link supported in ODC V4.3.1 from a MySQL database to a MySQL tenant of OceanBase Database.

• SQL development and data source management optimization: ODC V4.3.2 improves the usability of the SQL development page, data sources, and forms and optimizes more than 10 features such as the location key, resource tree object, and SQL execution result.

For more information, see the Feature updates section.

Version information

• Current version: V4.3.2

• Previous version: V4.3.1-BP

• Release date: September 26, 2024

• Supported upgrade path: You can directly upgrade ODC V2.0.0 and later to this version.

Feature updates

• Logical database

  • Added support for configuring and removing logical databases.

  • Automatically extract logical tables based on the topology distribution of physical tables to improve efficiency.

  • Provided a new feature for creating logical tables, where users can follow prompts to configure and create logical tables.

  • Added support for submitting logical database DDL change requests through the database change order feature.

  • Added structural consistency checks for logical tables to detect physical table inconsistencies.

  • Logical databases are now included in the existing database and table permission management system, ensuring secure access to logical database data.

• Data archiving

  • Added new support for archiving from Oracle to OceanBase Oracle.

  • Added new support for archiving from Oracle to Oracle.

  • Added new support for archiving from OceanBase Oracle to Oracle.

  • Added new support for archiving from PostgreSQL to OceanBase MySQL.

• Data Cleanup

  • Added support for data cleanup for Oracle databases.

  • Added support for data cleanup for PostgreSQL databases.

• SQL Checks

  • Added a new SQL row impact check specification for OceanBase MySQL and MySQL data sources, enabling the limitation of large SQL changes to ensure business stability.

• Partitioning Plan

  • For date-type field partitions, added an option to ensure partition names and partition content ranges are consistent.

• Data Import

  • The ODC desktop version now supports direct folder selection for data imports.

• SQL Window

  • Added a feature where clicking the product logo on the SQL development page returns users to the project list page, providing a quick way to return to the homepage.

  • Improved the interaction of the SQL window positioning key, ensuring that the targeted database is automatically displayed in the visible area.

  • SQL executed in the SQL window now shows DB execution time directly on the result tab.

  • Optimized sorting of resource tree objects; resource tree items (data sources, projects, databases, tables, views, etc.) are now sorted by name by default.

  • Users can now initiate all types of tickets directly from databases in the SQL window resource tree.

• Data Source

  • Databases under a data source can now be filtered quickly based on availability and whether they are assigned to a project.

  • Improved interaction for data source connection initialization scripts, providing quick guides for common parameter configurations.

• Usability

  • Optimized empty data state interactions across all features (data sources, projects, scripts, resource tree, etc.).

  • Optimized data source selection interactions across all features (database maintenance, sensitive column scanning, adding new databases to projects).

  • For commonly used forms (ticket lists, database lists, user lists), columns that do not display fully (ticket description, data source column, sorting rules, user roles, etc.) now display full content on hover.

  • Added a GitHub issue link on the feedback page, allowing users to provide product feedback quickly via the open-source community.

• Others

  • SSO integration now supports Azure AD.

  • Updated the platform's login password policy. The latest policy requires a password length of 8-32 characters, containing at least three of the following four character types: numbers (0-9), uppercase letters (A-Z), lowercase letters (a-z), and special characters (all English special characters).

Bug fixes

• Data objects

  • Fixed the issue where an error is reported when the system executes the formatted SQL statements generated for columns that contain large object (LOB) fields after a file upload.

  • Fixed the issue where the precision of TINYINT data is incorrect in MySQL mode.

  • Fixed the issue where a column of the Character Large Object (CLOB) or Binary Large Object (BLOB) data type whose value is NULL cannot be edited on the GUI.

• Change control

  • Fixed incorrect precision for TINYINT column types (MySQL data source) in SQL generated by schema comparison tasks.

  • Resolved an issue where partition names were misidentified as table names, leading to permission errors.

  • Fixed a bug where new_table in rename table old_table to new_table was mistakenly flagged as needing new_table permissions.

  • Addressed potential failures in data simulation tasks for MySQL 5.7.

  • Resolved an issue where the manual execution button remained clickable after triggering manual execution.

  • Fixed failure in creating or updating rules when there were too many risk identification rules.

  • Fixed an issue where the page could not scroll when there were too many risk identification rules.

  • Resolved an issue allowing scheduling intervals of less than ten minutes for periodic tasks.

• Import and export

  • Fixed an issue where merging PL and table DDL into a single SQL file could cause import failures due to syntax errors.

  • Resolved a bug where path issues could cause export failures on the Windows desktop version.

  • Fixed an issue in OceanBase Oracle mode where exported result sets would be empty if table names were lowercase.

  • Resolved export failures for native MySQL data on the Windows desktop version.

  • Fixed errors when exporting tables with BigDecimal types.

  • Addressed an issue where the result set export would fail when using * and NVL functions in SQL.

  • Fixed export failures for result sets containing SDO-GEOMETRY data types.

• Data archiving

  • Fixed errors that occurred when modifying data archiving rate limiting parameters.

  • Corrected inaccurate scan record counts in the details of executed archiving tasks.

  • Fixed a bug in OceanBase Oracle mode where archiving operations would fail if users did not have DBA permissions.

• Data sources

  • Fixed the issue where a test can still be successful even though an Oracle tenant is selected as the source sys tenant of OceanBase Database to be connected.

• Others

  • Fixed the issue where single sign-on (SSO) may fail in the environment with a load balancing service deployed.

  • Fixed the issue where the startup parameter ODC_APP_EXTRA_ARGS is invalid.

Known issues

• Client ODC cannot be installed in a directory whose name contains Chinese characters.

• The exported data file and content are incorrectly displayed when the table contains virtual columns.

• In Web ODC, the maximum size of schemas or data imported in a batch cannot exceed 2 GB. Otherwise, the upload cannot be performed.

• In Web ODC, the maximum size of schemas or data exported in a batch cannot exceed 2 GB. The excess part will be lost after the export.

• In the details of an export task, the total number of records of the exported objects is not accurate but depends on the views of OceanBase Database.

• If you do not set the ob_enable_trace_log parameter to on, only the execution plans of the SQL statements executed for the first time are displayed.

References

• ODC Community Edition

• ODC Enterprise Edition