Exalogic Virtual 188.8.131.52.X: Troubleshooting Procedure And Checklist For Solving OVM Manager 3.4.X Database Corruption Issues
(Doc ID 2631516.1)
Last updated on JANUARY 31, 2020
Oracle Exalogic Elastic Cloud Software - Version 184.108.40.206.0 and later Linux x86-64
Oracle Virtual Server x86-64
**** Procedure in this Note only applies to 220.127.116.11.X Exalogic Virtual racks. ****
This MOS Note provides detailed troubleshooting procedure and checklist for solving OVM Manager 3.4.X Database Corruption issues in Exalogic Virtual 18.104.22.168.X releases.
There are different approaches to solving the 3.4.X OVM Manager Database corruption issues in Exalogic Virtual racks 22.214.171.124.X like restoring OVM Manager DB from available backups, running Fixup procedure on OVM Manager DB for removing corruption and rebuilding OVM DB. There are different factors which have to be taken into account to determine the best course of action (whether running Fixup on DB, Restore from available DB backups or rebuilding OVM DB) to remediate OVM manager DB corruption. Factors like available Exabr & OVM DB backups, number of vServers created from EMOC after the last available backups etc. have to be taken into account. Checklist information in this Note gathers information on all these factors involved which will help determine best methodologies to remediate and solve OVM Manager DB corruption.
As first pre-requisite action complete following Checklist. This checklist information will help Oracle Exalogic Support to determine the best course of action for fixing OVM Manager DB corruption in case running fixup procedure in SOLUTION section of this Note does not resolve OVM Manager DB corruption issue.
Make a note of latest available OVM Manager DB backups.
Following command can be executed on EMOC EC1 Control vServer for listing OVM Manager DB backups.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!