MTK by default uses a 

TIMESTAMP

 format that is `

YYYY MM DD hh:mm:ss

', so this 

matches the MySQL 

DATETIME

 values. If you want to import MySQL 

TIMESTAMP

values, you have to change the 

LOAD 

command in the 

deploy.sh 

script according 

to the following:

db2 LOAD from ""/.dat"" |

of DEL

modified by 

coldel0x09 

timestampformat=\"YYYYMMDDHHMMSS\" 

insert into .

If you have MySQL 

DATETIME

 values and MySQL 

TIMESTAMP

 values in the 

same

table, you have to convert the format of the 

TIMESTAMP

 values to the 

DATETIME

format in the data file. Then the data file can be processed by the 

LOAD 

command 

correctly.

Migration of BLOBs

BLOBs usually contain binary data. As binary data cannot be exported to text 

files, a different way has to be found to migrate them.

Note: 

If your BLOBs contain only ASCII data and no binary data, you can 

dump them out of MySQL and load them into DB2 UDB in the same way as all 

other data. 

MTK does not support the automatic migration of 

BLOB

 data in the current 

version. Porting 

BLOB

 data from MySQL to DB2 UDB needs to be done manually. 

MTK converts the DDL correctly, it exports the data correctly in case of text only 

BLOBs, but the data files are 

not

 loaded automatically into DB2 UDB. In the case 

of text only BLOBs, you just need to run the

 LOAD 

command for the MySQL 

export file generated by MTK.

If your BLOBs contain binary data (such as bitmaps), you have to write a 

program to migrates your data.

We provide a simple Java program 

MigBlob.java 

(Example 6 7)

that copies data 

from a specified MySQL 

BLOB

 to a DB2 

BLOB

. This program can be easily 

integrated into migration scripts.

 Chapter 6. Data porting 

135