Running the migration

You can run the data migration utility to upgrade the transaction database.

Note:  You must back up the older version of the database before updating the database. Stop the Appserver before running the migration.
  1. Navigate to installed home/apache-tomcat 9.0.x/bin.
  2. Open the run_dbMigration.bat script for Windows or script for Linux/UNIX OS.
  3. Ensure that the MIGRATION_FOLDER parameter value points to the intended sub-folder under installed home/apache-tomcat 9.0.x/common/classes/largesoft/install/databaseMigrations folder.
    Note:  If the migration is from the previous release to the current release (for example, 10.1.x to 10.2.x) the MIGRATION_FOLDER parameter is set automatically and requires no change. But if the migration is from an older version, the MIGRATION_FOLDER parameter must be updated.


    If you migrate a database from version 8.3.4 to version10.2.11, you must first migrate the database from v 8.3.4 to v10.0.0, v10.0.0 to v10.1.0, and from v10.1.0 to v10.2.11.

    If the migration scripts for the older versions have jar files for example, extnMigration.jar, do not replace the existing jars as the jars in the migration scripts might not be valid. See, Migrating from an older version to a recent version.
  4. Execute the run_dbMigration.bat script for Windows or the script for Linux/UNIX OS.
    Note: The script requires executable permissions for using the chmod command. For the multi-tenant environment, specify the tenant name in the command line. For example, run_dbMigration.bat -tenant tenant.

    The specified tenant db information is retrieved from the central database.

  5. Check the dbMigration_# .log log file located at installed build\apache-tomcat-9.0.x\bin\logs folder for any errors stored in the logs subdirectory of the migration folder. For a multi-tenant environment, the log is located at the install build\apache-tomcat-9.0.x\bin\tenant directory and the name of the log is tenant_dbMigration_#.log.
    Note:  The migration process uses the database properties (name, server, type, user/password) in the file and the file in the customerconfig directory of the build. Ensure that both the files have the migrated database information set. For the multi-tenant environment, the database properties are in the central database.