MySQL to Db2

BladePipe supports data replication from MySQL to Db2. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

Db2

Connection

Basic Functions

Function	Description
Schema Migration	If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.
Table Name Mapping	Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

Function	Description
Setting Target Primary Key	Change the primary key to another field to facilitate data aggregation and other operations.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Limits

Limit	Description
MySQL Storage Engine	Support InnoDB, MyISAM, AWS XEngine. Other storage engines have not been tested yet.
MySQL Character Set	Support utf8, utf8mb4, latin1. Other encodings have not been tested yet.

FAQ

• How to handle MySQL DataJob latency?

• What to do when binary Log cannot be found in MySQL Source?

• What to do when access to schema in MySQL Source is denied?

  Tip: MySQL source-related FAQ also applies to MySQL-based DataSources.

---

Source

Prerequisites

Prerequisite	Description
Permissions for Account	See Permissions Required for MySQL/MariaDB.
Enabling Binlog	[mysqld] log-bin=mysql-bin # Enable Binlog binlog-format=ROW # Choose ROW mode binlog_row_image=FULL # Changes include all column data

Parameters

Parameter	Description
parseBinlogParallel	Number of threads for parallel parsing of Binlog in Incremental DataJobs.
parseBinlogBufferSize	Size of the circular buffer for parsing Binlog in Incremental DataJobs.
maxTransactionSize	Maximum number of data rows per transaction. If exceeded, the transaction will be split and flushed in parts.
limitThroughputMb	Limit the throughput of incremental Binlogs.
extraDDL	Support synchronization of additional DDL, including PT, GHOST, ALI_DMS, and PT_GHOST.
needJsonEscape	Escape special characters in JSON to be written to the target database.
fullDataSqlConditionEnabled	Add filtering conditions in SQL during source data scanning. It only works in Full Data migration.
srcTimeZone	Source time zone, e.g., +08:00, Asia/Shanghai, America/New_York, etc.

Tips: To modify the general parameters, see General Parameters and Functions.

---

Target

Parameters

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during write in Incremental DataTask: IGNORE Ignore conflicts (default) REPLACE Replace conflict (optional) EXCEPTION Raise an exception on conflict (optional)
limitWriteRps	Write RPS (Requests Per Second) to the Target.
writeParallel	The number of parallel threads allowed to write data to the Target, significantly affecting migration or synchronization performance.
minPoolSize	Minimum size of the data source connection pool.
maxPoolSize	Maximum size of the data source connection pool.
maxWait	Maximum wait time for a connection to the data source, in milliseconds.
soTimeoutSec	TCP socket timeout length for the data source connection, in seconds.
increParallelApplyStrategy	Parallel write strategy for relational databases in the Target: KEY: Parallel writing to partitions separated based on primary keys. TABLE: Parallel writing to partitions separated based on tables.

Tips: To modify the general parameters, see General Parameters and Functions.