Migrating Apache Derby databases

The migration tools migrate any Apache Derby instances to the new configuration, and they copy any Apache Derby instances that are stored in the previous release's WebSphere® Application Server configuration tree to the new release's configuration tree. After you use the migration tools, verify the results of the database migration and manually migrate any database instances or copy any Derby database instances that the tools do not automatically migrate or copy.

Before you begin

For resources to help you plan and perform your migration, visit Knowledge Collection: Migration planning for WebSphere Application Server.

Tips:
  • Before you run the migration tools, ensure that any application servers hosting applications that are using a Derby database are closed.

    Otherwise, the database migration will fail.

  • Before you run the migration tools, ensure that the debug migration trace is active.
    By default, this trace function is enabled. To reactivate the debug migration trace if it is disabled, set one of the following trace options:
    • all traces*=all
    • com.ibm.ws.migration.WASUpgrade=all

About this task

WebSphere Application Server Version 9.0 requires Apache Derby Version 10.3 or later. Apache Derby Version 10.3 is a pure Java™ database server that combines the Derby runtime with the opportunity to use the full services of IBM® Software Support. For comprehensive information about Apache Derby Version 10.3, read the Apache Derby Web site.

Important: Derby-to-Derby migration performs a file-system copy of the data at a given point in time. This snapshot will not remain in sync with the database in the previous installation. If you roll back to the previous release, any updates to the database that you made after migration will not be reflected in the previous installation.

Procedure

  1. Migrate the configuration to Version 9.0.
  2. Verify that the Derby database instances have been copied.

    When you migrate from WebSphere Application Server Version 7.0 or later to Version 9.0, the migration tools automatically upgrade Derby database instances that are accessed through the embedded framework by some internal components such as the UDDI registry. The tools also attempt to upgrade Derby instances that your applications access through the embedded framework. You must verify these migration results after running the migration tools.

    • To distinguish between a partially and a completely successful Derby migration, verify the automatic-migration results by performing the following tasks:
      1. Check the general migration post-upgrade log for database error messages.

        These exceptions indicate database migration failures. The migration tool references all database exceptions with the prefix DSRA.

      2. Check the individual database migration logs.

        These logs have the same timestamp as that of the general migration post-upgrade log. The individual logs display more detail about errors that are listed in the general post-upgrade log as well as expose errors that are not documented by the general log.

        The path name of each database log is app_server_root/profiles/profileName/logs/myFulldbPathName_migrationLogtimestamp.log.

      3. Look at the debug log that corresponds with the database migration log.

        The WebSphere Application Server migration utility triggers a debug migration trace by default; this trace function generates the database debug logs.

        The full path name of each debug log is app_server_root/profiles/profileName/logs/myFulldbPathName_migrationDebugtimestamp.log.

      Performing these tasks gives you vital diagnostic data to troubleshoot the partially migrated databases as well as those that fail automatic migration completely. Ultimately, you must migrate databases that were not completely migrated automatically through a manual process. The log messages contain the exact old and new database path names that you must use to run the manual migration. Note these new path names precisely.
    • Verify that any Derby database instances that are stored in the previous release's WebSphere Application Server configuration tree were copied to the new release's configuration tree

      Check the general migration post-upgrade log for database error messages. These exceptions indicate database migration failures. The migration tool references all database exceptions with the prefix DSRA.

      .
  3. Manually copy Derby database instances where necessary.
    • The Version 9.0 migration tools do not attempt to migrate database instances that transact with applications through the Apache Derby Network Server framework. This exclusion eliminates the risk of corrupting third-party applications that access the same database instances as those accessed by WebSphere Application Server.

      To minimize the risk of migration errors for databases that were only partially upgraded during the automatic migration process, delete the new database. Troubleshoot the original database according to the log diagnostic data, then perform manual migration of the original database.

    • The Version 9.0 migration tools do not copy any Derby database instances outside the WebSphere Application Server configuration tree.

      If migration does not copy a Derby database instance automatically, copy the database instance manually.

  4. Manually migrate your UDDI registry if it uses a database on the Apache Derby Network Server framework.

    Read Migrating the UDDI registry in the documentation for more information.

What to do next

Read Installing and configuring the SDO repository in the documentation for more information on upgrading the SDO repository application to Version 9.0.