Migrating the stand-alone database logger
You can migrate the stand-alone database logger software by stopping the logger and installing the new version to the same location. Back up your database before migration. Before you restart the database logger, update the database schema to store the new information produced by the later version of WebSphere® MQ File Transfer Edition.
Procedure
- Stop the database logger using the fteStopDatabaseLogger command.
- Back up the database using the tools supplied with the database software.
- Back up the database logger installation directory
by copying to a new directory. By default, the database
logger installation is located in the following directory:
- c:\Program Files\IBM\WMQFTE\tools on Windows platforms
- /opt/IBM/wmqfte/tools on UNIX platforms
- If the existing level of database logger is V7.0.3 or earlier, /opt/IBM/wmqfte/tools on Linux platforms
- If the existing level of database logger is V7.0.4 or later, /opt/ibm/wmqfte/tools on Linux platforms
- Install the new version of the stand-alone database logger in the same location as the existing stand-alone database logger using the WebSphere MQ File Transfer Edition Remote Tools and Documentation installer. When asked if you want to reuse or replace the existing configuration options, select Reuse existing configuration. For information about using the Remote Tools and Documentation installer, see Installing IBM WebSphere MQ File Transfer Edition Remote Tools and Documentation using the graphical installer.
- If your database schema is at an earlier version,
you must migrate the schema to each subsequent level in order. For
example, if your database schema is at V7.0.1 and you are migrating
to V7.0.4, you must migrate your schema from V7.0.1 to V7.0.2, then
from V7.0.2 to V7.0.3, and then from V7.0.3 to V7.0.4. Migrate your
database schema from version old to
version new, where old and new are
variables that describe a schema version, by performing the one of
the following actions for each version of the schema that you must
migrate through:
If your database is DB2® on z/OS® and you are migrating between the V7.0.2 and V7.0.3 schemas or between the V7.0.3 and V7.0.4 schemas, you must create a new database schema and copy your existing data into it. For more information, see Migrating the database tables on Db2 on z/OS.
If your database is Db2 on Windows, Linux or UNIX, you are migrating between the V7.0.2 and V7.0.3 schemas, and you created your database with a page size of less than 8K; you must increase the page size of the database before migrating to the new version of the database schema. For more information, see Increasing the page size of the log database on Db2 on Windows, UNIX or Linux.
If your database is not Db2 or you created your database with a page size of more than 8K, you can migrate the schema in the same way as for other versions, by completing the steps below.
- If you are migrating between database tables in any other
circumstances complete the following steps:
- Choose the file that is appropriate to your database platform and has a name that includes the string old-new. This file is located in the install_directory/tools/sql directory of the Remote Tools and Documentation installation.
- If you have made modifications to the initial schema, review the migration file to ensure that the file will be compatible with your modified database.
- Run the SQL file against your database.
- Start the database logger using the fteStartDatabaseLogger command.

Feedback
