The source supported vCloud Automation Center 5.2 version database contains stale migration table data that is blocking the administrator from successfully rerunning the vRealize Automation pre-migration or migration task.

Problem

Stale migration tables in the source database can cause several problems. In some cases, pre-migration or migration fails. In other cases, pre-migration and migration appear to be successful, but managed machines are not visible in the catalog after migration is finished.

Cause

Problems with migration tables in the source database occur most commonly for the following reasons:

  • You specify one target system when you run pre-migration and a different one when you rerun pre-migration.

  • You specify one target system when you run pre-migration and a different one when you run migration.

  • You specify a test target system when you initially run pre-migration and migration and a production target system when you rerun pre-migration and migration.

  • You specify a beta target system when initially run pre-migration and migration and a production target system when you rerun pre-migration and migration.

The error message that you receive for each situation may differ, and in some cases you may not receive an error, but the cause is typically the same. You must delete the stale migration tables in the source database and then restart the pre-migration and migration process. Alternatively, if you created a backup of your source database or a snapshot of your source system before you started the pre-migration and migration process, you can revert to that clean backup database and restart the process.

If you specify a different target system when you rerun pre-migration or migration, the source database is left with stale migration tables which block the task from finishing successfully. In most cases, the pre-migration or migration report and logs generate an error, informing you of the database table problem.

If you migrate to one target system and then migrate to another without clearing the stale database tables first, machines may be visible from the Infrastructure tab in the target system but not visible from the Items tab. For details, see Machines Not Visible on Items Page After Migration.

Procedure

  1. Open the source 5.2 database using a method of your choice.
  2. Delete the following tables:
    • DynamicOps.Migration.EntitlementMapping

    • DynamicOps.Migration.Properties

    • DynamicOps.Migration.Users

    • DynamicOps.Migration.UserTables

    • DynamicOps.Migration.VmUsers

    • DynamicOps.Migration.ImportedVirtualMachines

  3. Save the updated database.
  4. Restart the vRealize Automation migration tool .

Results

The pre-migration task and migration successfully run to completion.