My Oracle Support Banner

Exalogic Virtual 2.0.6.0.X, 2.0.6.1.X, 2.0.6.2.X, 2.0.6.3.X: How To Fix OVM Manager 3.2.X Database Corruption Using Fixup Command? (Doc ID 2632099.1)

Last updated on JANUARY 29, 2020

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.0.0 and later
Linux x86-64
Oracle Virtual Server x86-64

***** This MOS note applies to below Exalogic Virtual releases.

This MOS Note provides detailed details on how to fix OVM Manager Database corruption in following Exalogic Virtual releases using OVM Shell level fixup command.

- Exalogic Virtual 2.0.6.0.X
- Exalogic Virtual 2.0.6.1.X
- Exalogic Virtual 2.0.6.2.X
- Exalogic Virtual 2.0.6.3.X

Goal

This MOS Note provides detailed details on how to fix OVM Manager Database corruption in following Exalogic Virtual releases using OVM Shell level fixup command.

NOTE:

Procedure in this Note will fix if there is minor corruption or inconsistencies in OVM Manager DB. If the completely OVM Manager DB is corrupted or has lot of inconsistencies then the procedure of running OVM shell level fixup command mentioned in this Note will not fix the problem. You will to rebuild the OVM Manager DB. Reach out to Oracle Exalogic Support team by opening Service Request for assistance on rebuilding OVM Manager DB if the running fixup procedure in this Note does resolve the OVM DB corruption issue.

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.