Scenario: Export Already Completed

Symptoms

•

.mv-bak.db exists.

•

.mv.db missing.

Cause

Export likely succeeded already. This indicates that a previous export operation has already renamed the original database.

Fix

•

If the migration file (flexnetls-h2-1-4-x-migration-source.data) exists, proceed to import.

•

If the migration file is missing, do the following:

•

On Windows—Rename the backup file (flexnetls_licenses.mv-bak.db) back to flexnetls_licenses.mv.db, then rerun the export.

•

On Linux—Run the following command:

mv /var/opt/flexnetls/<publisher>/flexnetls_licenses.mv-bak.db \

/var/opt/flexnetls/<publisher>/flexnetls_licenses.mv.db

This command renames flexnetls_licenses.mv-bak.db to flexnetls_licenses.mv.db.

Now try rerunning export.