My Oracle Support Banner

[ PCA 2.3.1+ ] How to Rebuild an Oracle VM Manager Database ( including User-Friendly Names) On a Private Cloud Appliance (Doc ID 2315397.1)

Last updated on JULY 29, 2020

Applies to:

Private Cloud Appliance - Version 2.3.1 and later
Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Goal

There may be scenarios during which the Oracle VM Manager Database built-in to the Private Cloud Appliance needs to be re-generated. The procedure to do so is outlined in this note.

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
 1.Preparation
 1a) Take notes of the configuration that will be needed during restoration of the database
 1b) Download and copy the required scripts to the Active Management node
 2. Check for existence of Model Dump XML files
 3. [PCA 2.3.1 ONLY] Replace the ovm_core_3.4.2.1398.ear
 a. [PCA 2.3.1 ONLY] On Master Management node
 b. [PCA 2.3.1 ONLY] On the slave management node
 4.  Delete the problematic manager database
 a) Before deleting the database it's recommended to take a copy of the mysql database.
 b) Shut down the Oracle VM manager service
 c) Using ovm_upgrade.sh from /u01/app/oracle/ovm-manager-3/ovm_upgrade/bin and the values from the .config file, delete the bad database
 d) Start the OVM services:
 5. Re-generate the Weblogic certificates
 a) Generate the weblogic replacement certificate:
 b) Generate other new certificates:
 6. Go into the OVMM UI and discover the Compute Nodes
 7. Repeat step 6 for each custom tenant group (server pool) which was created.
 8. CRITICAL: Add the internal ZFS storage array and any other storage systems added to the PCA since initial installation
 9.  Re-implement local customizations previously made
 10. Repeat Step 9 for each Custom Tenant group
 11. Restore the Simple Names for PCA and Oracle VM
 12. Refresh the Repositories
 12a) Automated :
 12b) Manually :
 13. Local repositories presentation
 14. Re-establish yum repositories in OVM Manager if necessary
 15) Tune OVM Manager via ovm_shell to increase some scale related values
 16. Configure each server for IPMI: In the WebUI - ensure that each server has the following settings for IPMI:
 a) Automated option
 b) Manual option
 17. Verify the passwords of the servers / databases
References

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