Environment

  • UMS 6 on Windows or Linux

If the embedded database of UMS* is corrupted, try the following measures to resolve the issue.

*The underlying technology of the embedded database is Apache Derby.

Restoring a Database Backup Made with the UMS Administrator

If a backup of the embedded database is available (see Creating a Backup), just restore the backup, see Restoring a Backup.

Restoring a File-Based Backup

If an uncorrupted copy of the database files located under C:\Program Files...\IGEL\RemoteManager\db\rmdb (default installation path on Windows) and/or /opt/IGEL/RemoteManager/db/rmdb/ (default installation path on Linux) is available, you can restore the file copy. In the remainder of this how-to, the aforementioned possible paths will be referred to as RMDB_PATH.


To restore the backup, perform the following steps:

  1. Open the UMS Administrator, and go to Datasource in the menu on the left.

    Default path to the UMS Administrator:

    Linux: /opt/IGEL/RemoteManager/RMAdmin.sh
    Windows: C:\Program Files\IGEL\RemoteManager\rmadmin\RMAdmin.exe

  2. In the Datasource area, delete the corrupted Derby DB.
  3. Create a new embedded DB with exactly the same user name and password as you used for the deleted DB.
  4. Deactivate the newly created DB.

  5. Stop the UMS Server service. For details on how you can stop it, see HA Services and Processes.

  6. Erase all files contained in the folder at RMDB_PATH.
  7. Copy your previously backed-up files to RMDB_PATH.
  8. Activate the DB with the UMS Administrator under Datasource.
  9. Wait 1 - 2 minutes, then log in to the UMS Console.