Release Note

v2.8.1(2025.01.14)

Bug Fixes

Fixed data synchronization problem caused by synchronization to MogDB to unique non-empty index when Oracle primary key uses non-unique index
Optimize the synchronization of newline and carriage return data in the data during full synchronization
Fixed the issue that the synchronization status on the table was not updated after full synchronization in some scenarios
Fixed an issue with missing table associated indexes and constraints in the table details subpage
Fixed the problem that part of the verification logic failed and the node failed when the node was added.

v2.8.0(2025.01.03)

Features

Optimise the logic of full migration (snapshot), support copy method for MogDB target, compared with batch insert method, the performance is about double.
Adjust the export format of failed objects to csv format to avoid Excel font error when exporting.
Adjust the polling mechanism of dynamic validation, the interval is adjusted to 2 seconds, and the number of attempts is adjusted to 5.

Bug Fixes

Fix the problem of losing some sync records of objects with the same name in structure sync details.
Fix a cascading selection problem when selecting objects with the same name in the object selection pages.
Fix a bug that Kafka node type filtering does not work when querying the node list.
Fix a bug that Kafka topic is not configurable in the channel task synchronised to Kafka after a channel status change.

v2.7.0(2024.11.12)

Features

Support web display of full-sync exceptions (in the table object details page, switch to the data synchronization tab to check the exception)
Supports Oracle/MogDB database's master/slave structures, and the initialization of full data gives priority to querying with the standby database.
Channel state optimization, the channel task state is no longer strongly correlated with the specific state of the objects.
In the data verification module, support for precise positioning of the difference columns and data.
Support for synchronization Oracle ROWID, and as a primary key to perform subsequent synchronization, and can avoid opening any level of supplemental logging in the source database.
Support for ROWID-based data conflict processing
Optimized the object add logic, greatly improving the efficiency of adding objects (Oracle can add 10,000 objects per minute)

Bug Fixes

Fixed the problem that the parameter Skip Incremental Delivery in Advanced Parameters does not take effect.
Fix the problem of synchronizing full and incremental objects when the number of objects in the source database is large.

v2.6.0(2024.09.30)

Features

Open the DDL synchronization configuration function on the page and support configuring rules to automatically add newly created tables to the channel.
Optimize synchronization to Kafka as the target and support custom configuration of the target end Kafka topic.
Optimize the incremental exception handling logic, support the display of incremental exceptions on the web page, and use can perform failure retry or ignore error data.
Expand the data verification function and support data repair after comparison for primary key tables.
Externalize the repository database initialization and upgrade scripts to facilitate handling exceptions caused by scripts.

Bug Fixes

Fix the problem that the NVARCHAR2 type of Dameng database is not supported in data verification. Fix the problem of failed connectivity check of PG nodes when creating a channel. Fix the problem that the default value of the bit type is not converted when synchronizing the structure from MySQL to MogDB. Fix the problem that when setting some tables to skip increments during data synchronization, incremental data is still synchronized.

v2.5.0(2024.09.02)

Features

Add the DDL synchronization for MYSQL to MogDB (partial table-related DDL)
Support static data verification for Dameng and MogDB
Support structure synchronization and full migration from DB2 to MogDB
Support modifying the buffer type for Oracle Logmnr. Add Chronicle Queue which can be used to avoid OOM caused by large transactions during extraction.
Support full and incremental data conflict handling with Oracle, MySQL, and MogDB as the target ends.

Bug Fixes

Fixed the problem that some advanced parameters in the channel detail page did not perform data value verification.
Fixed the problem of losing line breaks in the text type during the data synchronization process from MySQL to MogDB.
Fixed the problem of losing text type data during the data synchronization process from MogDB to MySQL.
Fixed the problem of bit type parsing during the data synchronization process from MySQL to MogDB.

v2.4.0(2024.08.12)

Features

Add the DDL synchronization for Oracle to MogDB (partial table-related DDL)
Supports manual add and remove tables during the data synchronization process (needs to be executed when channel is paused)
Support table level breakpoint resumption during the full migration for databases with Oracle, MySQL, or MogDB as the source
Preliminary support for the continuous verification of Oracle, MySQL, and MogDB
Support sync sequence values in the default value when migrating from OG to Oracle 12c and above
Security enhancement: supporting automatic encryption of configuration files and user passwords in MDB
Supports refined data type mapping, make the type mapping between structure migration of Oracle, MySQL, and MogDB more reasonable
Supports automatic resource cleaning after channel deletion, automatically cleans up processes, temporary files and data of full sync, increment sync, and data verification, and automatically cleans up slot in the MogDB database
During the full migration, file-level read-write separation is supported to avoid the accumulation of MDB temporary files caused by large sharded data

Bug Fixes

Fixed the issue of invalid delivery of delete and update at the target end caused by non-precise numbers in the float of tables without primary keys
Fixed the problem of processing bool and uuid type data during the synchronization process from MogDB to Oracle
Fixed the inaccurate NULL value verification problem during the data verification process of MySQL and openGauss nodes
Fixed the problem of possible loss of changed data in some scenarios during the incremental data merging process at the target end

v2.3.0(2024.07.09)

Features

Add the DDL synchronization for MogDB to Oracle and MySQL (partial table-related DDL)
Add advanced channel parameters, and support adjusting the performance parameters of full migration from the page of advanced channel parameters
Add the node cloning function, support quickly cloning a new node from the existing node to avoid repeated information input
Support accurate query of the channel list related to a certain node on the channel list page
Optimize the automatic conflict handling logic, and support automatic conflict handling within channels targeting Oracle, MySQL, and MogDB
Optimize the incremental synchronization startup logic of MySQL, and add advanced parameters to control whether to lock the table at startup
Optimize the LOB processing logic: Small LOB fields do not record files separately to reduce the occupation of file handles

Bug Fixes

Fix the issue that for tables with LOB and no primary key, the full-field matching cannot match LOB during UPDATE/DELETE.
Fix the issue of data conflict in incremental synchronization of the primary key table of MySQL.
Fix the issue that LOB is not deleted after the completion of full migration and synchronization.
Fix the reading logic of the MySQL date/time type to avoid the issue of time formatting error: HOUR_OF_DAY: 0 -> 1.
Fix the issue that when there are both indexes and constraints on the same field, the index is created as unique.
Fix the issue of incorrect check constraint verification in the structure comparison from MogDB to MySQL. The MySQL check constraint column is parsed from the expression.
Fix the issue that the limit on the number of new channels does not remove draft channels.

v2.2.0(2024.05.17)

Features

Added MDB user rights management to achieve cross-user functions and data rights management
Optimize the channel creation process, using a step-by-step guided process to guide new users to create and run a synchronization task
Oracle primary key/Unique constraint Non-unique indexes are used. This function automatically creates dependent indexes as unique indexes on the MogDB server
If a full task fails in a channel, you can click to skip the full migration of the failed table
Added dynamic data comparison between MySQL and MogDB in the data verification module
Support MariaDB 10.4 or later (corresponding to MySQL)
Optimized sequence value automatic update logic, executed only in incremental synchronization phase, increased sequence latest value synchronization interval range parameter

Bug Fixes

Fixed an oom task full migration issue in large LOB scenarios
Fixed some MySQL time reading exceptions
Fixed syntax errors when field default values in MogDB are synchronized to other libraries using double colon type conversion
Fix sync error when sequence name with $sign from MogDB to Oracle
Fixed a syntax error caused by default time field values not being wrapped with quotation marks during MySQL to MogDB synchronization
Fixed an issue where sequence objects could not be synchronized after using sequence as the default value of table fields in some scenarios
Fix sequence value synchronization syntax rewriting issue when MogDB to Oracle

v2.1.0(2024.04.03)

Features

Java version of data verification range extension, support: Oracle, MogDB, MySQL,DB2
Supports type mapping that controls the synchronization of BLOBs from other libraries to MogDB. The synchronization can be bytea or blob, which can be controlled by the advanced parameter enableBlob2Blob
When Oracle Sequence is synchronized to MogDB, if the maximum value of bigint is exceeded, the Oracle Sequence is automatically synchronized to Large Sequence
Support for generate as synchronization to MogDB Sequence after Oracle 12c
Supports object export after structure synchronization fails, and batch import and repair of failed objects
When MySQL is synchronized to MogDB, bit(1) is mapped to bool, which can be controlled by the advanced parameter enableBit1toBool
Support MogDB to MySQL synchronization, automatically determine whether the line length exceeds the MySQL limit (65535), can be controlled by the advanced parameter autoConvertDataType
Supports automatic processing of unique value conflicts during incremental data synchronization from MogDB to Oracle/MySQL
Support for confirming and executing MogDB replication slot creation directly in MDB, as well as automatically performing heartbeat table creation

Bug Fixes

Optimizes the query logic on the source end of full synchronization, avoiding frequent oom OOM problems during full synchronization
Fixed an ORA-1461 error that may occur when MogDB is fully synchronized to Oracle in some scenarios
Fixed an issue where too many links were created in the source database during full synchronization in some scenarios
Fixed the bool/numeric type problem during the full synchronization from MogDB to MySQL
Fixed a bit type data value parsing error during incremental synchronization from MySQL to MogDB
Fixed a data insertion issue caused by a small range of MySQL timestamp types when MogDB was synchronized to MySQL
Fixed the MySQL to MogDB full synchronous database link reuse issue
Fixed 0x00 issue caused by NULL value in Batch mode when MySQL was synchronizing to MogDB

v2.0.0(2024.02.26)

Features

Data verification: Added the independent data verification function (currently available only for Oracle and MogDB nodes), which supports channel-based data verification and node-based custom data verification
Synchronization policy enhancement: Supports customized shard parallelism with MySQL/MogDB as the source database
Enhanced synchronization policy: Supports parallel KEY shards with MySQL/MogDB as the source database, greatly improving the full synchronization efficiency of MySQL/MogDB
Enhanced structure synchronization: Supports MogDB to DB2 object structure synchronization plane
Structure synchronization enhanced: When the MySQL prefix index structure is synchronized, the index prefix structure is retained on the target end
Enhanced Dolphin mode compatibility: Support for MySQL to MogDB B mode self-increment column mapping to self-increment column
Optimized channel logic: After a blank channel (no synchronization object is selected) is entered, the object selection boundary is automatically displayed
Process design: Designed MDB user rights management and related UI interface (the overall function will be released in the next version)

Bug Fixes

Fixed an issue with automatically cleaning sql errors when resetting objects
Fixed an issue where source DDL had a leading space causing conversion errors