Migration considerations for Version 8.1.4

This section describes Version 8.1.4 migration issues and provides the necessary instructions for the DB2 Everyplace Sync Server and Sync Client:

• For the Sync Server:

  The infrastructure that supports the replication of JDBC subscriptions is different in DB2 Everyplace 8.1.4. In order for it to function properly, DB2 Everyplace 8.1.4 needs to migrate JDBC subscriptions that were created with a previous version of DB2 Everyplace. This migration should take place before the newly installed DB2 Everyplace Sync Server is started. You should replicate all mirror databases before upgrading an existing DB2 Everyplace installation to DB2 Everyplace 8.1.4. If the mirror databases are replicated immediately before installation and migration is performed immediately after installation, then migration will not require much time. Otherwise, it may take an extended period of time to complete. Before you install DB2 Everyplace 8.1.4, it is highly recommended that all source databases, mirror databases, and the DSYCTLDB database be backed up. After installation, when migration is performed, it is necessary that all source tables in a JDBC subscription be quiescent. Activity on the tables may resume once migration has completed.

  Prerequisites

  • Ensure that the CLASSPATH contains the JDBC drivers of all source databases referred to in a JDBC subscription.
  • Ensure that all tables included in a JDBC subscription are quiescent.

  Procedure

  During the installation of DB2 Everyplace, this task can be performed for you. If you choose not to have the installation Setup Wizard perform this task, you must perform the following steps after DB2 Everyplace is installed.

  1. Invoke the migration utility:
     • For Windows, execute %DSYINSTDIR%\Server\bin\dsyjdbcmigration.bat.
     • For UNIX, execute $DSYINSTDIR/Server/bin/dsyjdbcmigration.sh.
  2. Check the log file dsyjdbcmigration.log in %DSYINSTDIR%\Server\logs or $DSYINSTDIR/Server/logs for errors.
  3. If there are errors, correct them and repeat steps 1 and 2. If problems persist, contact IBM software support.
• For the Sync Client:

  Procedure

  If you have previously synchronized using Linux or QNX Neutrino Sync Client, you must migrate the Sync Client configuration files by running migrate.sh in the target directory. The target directory is where the Sync Client configuration files (For example, CONFIG1, MISC1) are stored. The script simply changes the file names to lowercase. The file migrate.sh is located in the /bin directory. If you try to synchronize using a Linux or QNX Neutrino 8.1.4 Sync Client and the previous configuration files (which are all upper case), then the API function iscConfigOpen() with return ISCRTN_Failed.

Related tasks

• Installing on a server for Windows