Errors that occur during Derby to DB2 Universal Database™ migration
are reported in the Data Output view.
Restriction: - In Derby, version 10.0, you cannot deploy user-defined functions.
- The DDL for stored procedures, user-defined functions, and triggers are
migrated. However, you must migrate JAR files manually.
- If your table columns have Generate always as identity set,
you cannot migrate the table data.
Possible migration errors:
- Broken object-references
- If an object was not deployed on the target database, then the dependent
objects will not deploy. For example, the migration of a view that depends
on a table that is not migrated will fail.
- Data integrity problem
- The data migration for a table with referential integrity constraints
might fail if the data migration of the referred table was not successful.