Note: 

The test efforts can be between 50% and 70% of the total migration 

effort. 

9.2  Data checking techniques

Data movement is the first thing any migration should focus on. Without having 

all your tables and data properly moved over, all other migration testing is in vain. 

The test process should detect if all rows were imported into the target database, 

verify that data type conversions were successful, and check random data 

byte by byte. The data checking process should be automated by appropriate 

scripts. When testing data migration you should:

Check 

IMPORT/LOAD

 messages for errors and warnings.

Count the number of rows in source and target databases and compare them.

Prepare scripts that perform data checks.

Involve data administration staff familiar with the application and its data to 

perform random checks.

9.2.1  IMPORT/LOAD messages

You should always check the messages generated by the 

IMPORT

 or

LOAD

commands. Example 9 1 presents messages generated by the sample 

IMPORT

command. You should read 

not

 only the summary at the end of the listing, but 

also pay attention to the warning messages.

Example 9 1   Sample IMPORT messages

db2>IMPORT from table01.unl of del replace into table01

SQL3109N  The utility is beginning to load data from file "table01.unl".

SQL3148W  A row from the input file was not inserted into the table.  SQLCODE 

" 545" was returned.

SQL0545N  The requested operation is not allowed because a row does not satisfy 

the check constraint "ITSO.TABLE01.SQL030812222227680".  SQLSTATE=23513

SQL3185W  The previous error occurred while processing data from row "2" of the 

input file.

SQL3117W  The field value in row "3" and column "1" cannot be converted to a 

SMALLINT value.  A null was loaded.

270 

MySQL to DB2 UDB Conversion Guide