Regenerate Oracle VM Manager repository database

Ronnie Kalisingh

Some quick notes to regenerate a corrupted Oracle VM manager repository database.

How did we discover the corruption?
The MySQL repository databases was increasing in size, the file “OVM_STATISTIC.ibd” was 62G. We also found the following error messages in the “AdminServer.log” logfile:

####<2018-02-13T07:52:17.339+0100> <Error> <> <ovmm003.gemeente.local> <AdminServer> <Scheduled Tasks-12> <<anonymous>> <> <e000c2cc-e7fe-4225-949d-25d2cdf0b472-00000004> <1518504737339> <BEA-000000> <Archive task exception: No such object (level 1), cluster is null: <9208>

Regenerate steps
– Stop the OVM services

– Delete the Oracle VM Manager repository database

“/u01/app/oracle/ovm-manager-3/ovm_upgrade/bin/ –deletedb –dbuser=ovs –dbpass=<PASSWORD> –dbhost=localhost –dbport=49500 –dbsid=ovs”


– Generate replacement certificate

– Start the OVM services and generate new certificates

– Restart OVM services

– Repopulate the database by discovering the Oracle VM Servers

– Restore simple names
Copy the restoreSimpleName script to /tmp, see Oracle Support note: 2129616.1

[OVM] Issues with huge OVM_STATISTIC.ibd used as OVM_STATISTIC Table. (Doc ID 2216441.1)
Oracle VM: How To Regenerate The OVM 3.3.x/3.4.x DB (Doc ID 2038168.1)
Restore OVM Manager “Simple Names” After a Rebuild/Reinstall (Doc ID 2129616.1)

Next Post

First steps with Docker Checkpoint - to create and restore snapshots of running containers

Docker Containers can be stopped and started again. Changes made to the file system in a running container will survive this deliberate stop and start cycle. Data in memory and running processes obviously do not. A container that crashes cannot just be restarted and will have a file system in […]
%d bloggers like this: