Server fails to start due to version validation

Edit online

During server start, the version of software is checked for consistency between IBM® Business Automation Workflow (BPM) profiles and the Workflow Server and Performance Data Warehouse databases. If the versions are not consistent, the related servers fail to start.

Errors related to the database schema version stored in LSW_SYSTEM_SCHEMA can occur for the following reasons:
  • The Business Automation Workflow generated SQL scripts were not used to create the tables.
  • The DBUpgrade command did not complete successfully after a product upgrade.
  • The database rollback did not complete successfully when a product upgrade was rolled back.

Resolving the problem

To resolve the problem, make sure that there is one row in the LSW_SYSTEM_SCHEMA table of the Workflow Server or Performance Data Warehouse database with the name DatabaseSchemaVersion. This row contains a version value that is appropriate for your current product version, and is used to validate that the expected database schema level matches what is applied to your databases.
Note: The value does not necessarily match the product version. If the value is wrong, the error message provides the expected value.
  • If the row does not exist, re-create the environment using the SQL scripts generated by Business Automation Workflow during installation or deployment environment creation. For example, the scripts mentioned in Running the generated Db2 database scripts Be sure to use the topic that is appropriate for your setup.
  • If the row exists but the value is wrong, it is usually because of missed or failed steps during upgrade or migration.
    • If you skipped the required DBUpgrade step or it did not finish successfully, you might see that the value is older than what is expected by the product. Ensure that the DBUpgrade command finishes successfully before proceeding to the rest of the step in the upgrade or migration process.
      Note: DBUpgrade is not required for every upgrade. Make sure that you are following the instructions for the specific upgrade you are doing.
    • If you upgraded your database and later rolled back the product installation, you might see that the value is newer than what is expected by the product. Ensure that you have properly followed the rollback steps. These include rolling back the databases in the deployment environment to a backup that you took before you ran the DBUpgrade command.