Data checking

Beside the basic data checks that should be done when exporting and importing 

the data, you should also check if the application handles your data correctly and 

that manipulations on the databases like inserts, updates, or deletes do not lead 

to unexpected results.

You can perform this checking manually, or you can also write some scripts to 

have your data checked.

Code and application testing

It is very important that the behavior of your application has not changed. 

Interactions between components of your application must be tested as well as 

each module of the application. A code review of all changed code is 

recommended as well.

Troubleshooting

Whenever the migration leads to a problem, like wrong data or wrong application 

behavior, you have to determine what the problem is in order to have it fixed.

You should understand error messages from the application as well as DB2 error 

messages. The troubleshooting process includes studying the DB2 log files.

See the DB2 technical support Web site for help with specific problems:

http://www 306.ibm.com/software/data/support/

Basic tuning

Once your new system is working perfectly, you might want to tune it for an even 

better performance. With the correct database configuration, and some hints 

from DB2 tuning tools, you can speed up your queries quite easily.

DB2 UDB provides tools like 

Performance Monitor

or 

Index Advisor

to support 

you in speeding up your DB2 UDB system.

 Chapter 2. Planning the migration from MySQL to DB2 UDB 

61