KBEC-00397 - Workarounds for a Built-In Database Schema on Disk That Is Older than Required by the ElectricFlow Server for Upgrade

Description

During an upgrade, the installer displays the following error message:

ElectricFlow is configured to use the built-in database. The built-in database on disk has a schema intended for ElectricFlow version <version>, which is older than that needed by this ElectricFlow <version> server. ElectricFlow does not support version upgrades of the built-in database, so the ElectricFlow server cannot start. For options to resolve this issue, see the "Troubleshooting" chapter of the "ElectricFlow Installation Guide"

This problem occurs because starting with ElectricFlow version 8.0, Electric Cloud does not support upgrades from ElectricFlow versions that use HSQLDB. HSQLDB is the built-in (default) database that was replaced by MariaDB in ElectricFlow version 8.3 as the built-in database.

Workarounds

Because the HSQLDB database in ElectricFlow is not upgradeable, to work around this issue, you can either point to a supported database, wipe the database (if you do not need its contents), or migrate the database contents to a database supported by ElectricFlow.

Pointing to a Supported Database

To point to a different ElectricFlow-supported database, modify the database.properties file to point to that database.

Wiping the Database Contents

If you do not need the contents of the built-in database, complete the following steps:

  1. Back up the database.

    For details, see “ElectricFlow Server Backups” in the ElectricFlow Installation Guide at http://docs.electric-cloud.com/eflow_doc/FlowIndex.html.
  1. Delete the files and folders whose names match the pattern:

    <DATA_DIR>/builtin/commander.*

Migrating the Database Contents to a Supported Database

If you do need the contents of the built-in database, complete the following steps:

  1. Back up your <DATA_DIR>\builtin folder and your <DATA_DIR>\conf\database.properties, passkey, and keystore files (or simply back up the entire <DATA_DIR>\conf folder).

  2. Reinstall the prior ElectricFlow version by using the following substeps:

    a. Uninstall the newer instance that is not working.

    b. Install the prior version again, which will use a new built-in database by default.

    Note: If you installed the DevOps Insight server on the same system, you must use a different <INSTALL_DIR> and <DATA_DIR> for this ElectricFlow server installation.

    c. After the CommanderServer service starts (meaning that the plugins are installed and so on) and you can log into the installed version from substep b, stop the CommanderServer service.

    d. Back up the new <DATA_DIR>\builtin and <DATA_DIR>\conf folders and replace them with the folders that you backed up in step 1.

    e. Restart the new CommanderServer service. It should now use the original built-in database containing your data and should function properly.

  3. Do a full export of the database contents.

    For details, see “ElectricFlow Server Backups” in the ElectricFlow Installation Guide at http://docs.electric-cloud.com/eflow_doc/FlowIndex.html.
  1. Switch to another production-quality database that ElectricFlow supports.

    For details, see “Configuring ElectricFlow to Use an Alternate Database” in the ElectricFlow Installation Guide at http://docs.electric-cloud.com/eflow_doc/FlowIndex.html.
  1. Do a full import of your data to the new database.

    For details, see “ElectricFlow Server Restores” in the ElectricFlow Installation Guide at http://docs.electric-cloud.com/eflow_doc/FlowIndex.html.
  1. Re-upgrade ElectricFlow.
Have more questions? Submit a request

Comments

Powered by Zendesk