Also, be sure that you have all the users created in your DB2 UDB system.

2.4.4  Application porting

The porting of the database structure, and the data can be supported by tools 

quite easily. The porting of the application, however, requires manual 

conversion. A few tools exist that can support you in some tasks such as syntax 

highlighting, but in most cases the main conversion must be done manually.

The extent to which you have to change the application code depends on the 

database interface that is used in the source application. When a database 

access layer is used, the adoption is not that complicated, otherwise, the effort to 

port the application will probably be much higher.

Application source code changes

As there are some differences in the

 Data Manipulation Language (DML) 

of 

MySQL and DB2 UDB, you may have to change SQL statements in your 

application code directly.

You might find things that are not natively supported in DB2 UDB that you used 

in MySQL, so a workaround must be established to have the application behave 

as before the migration.

Database interface

Whatever interface between application and database is used by your 

application, the access to the database must be changed because the database 

has been changed.

If standardized interfaces like ODBC or JDBC are used, the changes will be less 

than if an application uses the native API of a database product.

Condition handling

Depending on the implementation of your application, there might be some 

changes in the condition handling part of the application.

Additional considerations

DB2 UDB offers rich, robust functions, which you can take advantage of in your 

applications.

 Chapter 2. Planning the migration from MySQL to DB2 UDB 

59