The Oracle VM Manager Web Interface and the Oracle VM Manager Command Line Interface make use of a separate database to store a representation of the data model that is used by the Oracle VM Manager core. This is a legacy design artifact that is intended to help with performance and to allow for the potential to decouple the Oracle VM Manager Web Interface from the Oracle VM Manager core. This database makes use of events that are returned by the Oracle VM Manager core to notify the user interface layer of changes to the data model.

In rare instances, where the database used by the Oracle VM Manager Web Interface falls out of sync with the actual data model in the Oracle VM Manager core database, information represented within the Oracle VM Manager Web Interface may not reflect the actual environment. A typical scenario where this may happen is during a virtual machine clone operation that fails. During this process, the virtual machine is actually created within the data model and the database used by the user interface layer. If a part of the whole operation fails, Oracle VM Manager attempts to clean up and roll back, resulting in the virtual machine being removed from the data model. However, in this case, an event is not generated to notify that the clean up has succeeded, and the virtual machine information remains in the user interface database. The result is that the cloned virtual machine is still shown in the Oracle VM Manager Web Interface and the Oracle VM Manager Command Line Interface even though it does not actually exist in the environment.

The user interface database is not resynchronized automatically when the service is restarted, as this can take a long time for large environments. To force database resynchronization, you must create a file on the Oracle VM Manager host before restarting the service. The following instructions explain how to force resynchronization.