MySQL
IBM DB2

MySQL to IBM DB2 Converter

Tables, keys and rows into DB2, once or as a sync, with saved jobs you can run again.

Version
5.8.0
Release Date
Nov. 8, 2026
Size
46.4 MB
Platform
Windows 10 or later

Rather not run it yourself?

Let us do the migration →

Move a MySQL database into IBM DB2 without writing the DB2 schema by hand. DBConvert creates the tables, keys and indexes, picks a DB2 type for every column, and copies the rows server to server.

  • Reads MySQL, MariaDB, Percona Server, Amazon RDS or Aurora, Azure Database for MySQL, or Google Cloud SQL.
  • Writes to DB2 for Linux, UNIX and Windows 11.1 and later.
  • Reaches a DB2 server through the built-in SSH tunnel.
  • Runs on Windows as a desktop application.
  • The same download converts DB2 back into MySQL.

Convert once, or keep DB2 in step

Conversion

Creates the DB2 tables and loads the rows. Rows go in large batches. A row DB2 refuses is named in the log with the server's reason, and the rest of its batch still arrives.

Synchronization into DB2

Carries inserts, updates and deletes from MySQL into DB2 each time the job runs. It works in one direction: DB2 is never the source of a sync. How sync works

How MySQL types map to DB2

These are the defaults. Change any column's type on the Tables step before a row moves.

Scroll sideways to see all columns.

In MySQL In DB2
Integers, UNSIGNED The DB2 integer that holds the range. An UNSIGNED column takes the next size up; BIGINT UNSIGNED becomes DECIMAL(20).
BIT(n) Its number: SMALLINT, INTEGER or BIGINT by width, and DECIMAL(20) for BIT(64). Every value arrives whole.
DECIMAL DECIMAL up to 31 digits. Wider ones become DECFLOAT(34), which holds 34 digits exactly.
DATETIME, TIMESTAMP, TIME TIMESTAMP(n) with the same fraction digits. DB2 TIME keeps whole seconds within a day: a fraction, a time past 24 hours or a negative time is refused and named in the log.
VARCHAR, CHAR, ENUM, SET VARCHAR and CHAR, sized in characters; longer text becomes CLOB. ENUM and SET become VARCHAR.
Indexes, AUTO_INCREMENT Index names get the table name in front, since DB2 names indexes per schema. FULLTEXT indexes are not created. AUTO_INCREMENT becomes an identity that continues after the copied rows.

What stays behind

DBConvert moves tables, columns, keys, indexes, foreign keys, defaults and rows. Views, procedures, functions and triggers are not converted: rewrite them by hand for the new database.

DB2 means DB2 for Linux, UNIX and Windows 11.1 or later. DB2 for z/OS and IBM i (AS/400) are not supported.

Supported versions and services

MySQL

  • MySQL 5.x, 8.x; MariaDB; Percona Server
  • Amazon RDS / Aurora MySQL, Azure Database for MySQL, Google Cloud SQL

IBM DB2

  • IBM DB2 for Linux, UNIX and Windows 11.1 and later
  • Setup downloads the IBM Data Server Driver for ODBC and CLI from IBM. Installing offline

How to migrate MySQL to IBM DB2

1

Setup: connect MySQL and IBM DB2

Pick Convert or Sync, then choose the source and destination connections side by side on one screen. A connection is saved once and reused by every job.

MySQL source

Use the MySQL connection guide for local MySQL or MariaDB, or read from Amazon RDS / Aurora for MySQL, Azure Database for MySQL, or Google Cloud SQL for MySQL.

DB2 target

Enter the host, port (50000 by default), database name, user and password. Leave the schema empty to write into the login's own. See Connect IBM DB2.

Verify the copy

With Verify after the run on, the destination is checked when the copy ends: schema, totals and rows. The window shows which tables, rows and columns differ.

How Verify works

Move MySQL data into IBM DB2

Download the current build and run the first job against your own database.

Windows Windows 10 or later · 46.4 MB