Oracle VM Manager 3.2 and earlier: How to Recover from Data base corruption including "ObjectNotFound Exception" Errors (Doc ID 1555915.1)

Last updated on SEPTEMBER 22, 2017

Applies to:

Oracle VM - Version 3.0.1 to 3.2.11 [Release OVM30 to OVM32]
Linux x86
Linux x86-64


Receiving "ObjectNotFoundException" "ONF Exception" or persistent java.lang.RuntimeException errors signifies a corrupt DB

Examples of an ObjectNotFoundException Error:

No such object (level 1):
ObjectNotFoundException: No such object (level 1):
odof.exception.ObjectNotFoundException: No such object (level 1):
com.oracle.odof.exception.ObjectNotFoundException: No such object (level 1)

Example of a java.lang.RuntimeException error
java.lang.RuntimeException: java.lang.NullPointerException

Goal

Repair corrupted Oracle VM database for OVM versions 3.0.x , 3.1.x and 3.2.x Only,

DO NOT USE THIS Support article for OVM versions 3.3x or higher   

For OVM 3.3 and higher: Oracle VM: How To Regenerate The OVM 3.3.x/3.4.x DB (Doc ID 2038168.1)

DO NOT USE THIS FOR any versions of the Oracle Private Cloud Appliance - PCA.

   For PCA: How to Restore an Oracle VM Manager Database ( including User-Friendly Names) On a Private Cloud Appliance (Doc ID 2224820.1)

There are two options to recover the Oracle OVM Manager DB from an ObjectNotFoundException
   • Restore DB (This is the Preferred Method)
        o Restoring the MYSQL Database
        o Restoring the Oracle Database
        o Validating the Database
• Regenerate DB (If a Backup of the Oracle Manager DB is not available to Restore)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms