My Oracle Support Banner

[ PCA 2.3.1+] Procedure and Scripts to Re-install OVM Manager and Re-build OVM Manager Database On a PCA System (Doc ID 2657826.1)

Last updated on MARCH 17, 2022

Applies to:

Private Cloud Appliance - Version 2.3.1 and later
Private Cloud Appliance X8-2 - Version All Versions and later
Private Cloud Appliance X5-2 Hardware - Version All Versions and later
Linux x86-64

Goal

This document provides the procedures required to rebuild the OVM Manager database on a PCA system.

Private Cloud Applicance includes the Oracle VM (OVM) product. The Oracle VM Manager core application is a Java-based Oracle WebLogic application. The Oracle VM Manager database stores configuration information and event data. The actual database management server is a MySQL Enterprise database that is bundled with the Oracle VM Manager. Objects are managed using the Oracle Distributed Object Fabric (ODOF) layer.

Some circumstances can cause a logical disconnection between ODOF and the MySQL database resulting in loss of service to some or all OVM Manager functions. Extensive root cause analysis of such errors has identified different causes, including but not limited to:

 

Examples of symptoms of a logical corruption of an OVM Manager database are, but not limited to:

The Solution section below documents the required steps to correct the issue. The entire procedure should be reviewed before commencing.

The length of time it will take depends on the size of the installation - e.g. number of compute nodes, number of storage servers and number of their underlying resources.


The procedure only affects the OVM Manager. provided the PCA system is at PCA 2.3.4 or later. Compute nodes and the virtual machines they run on PCA 2.3.4 or later systems are not impacted. However, they cannot be managed using the OVM Manager until the step "Restore the Simple Names for PCA and Oracle VM" is complete.

Note that PCA systems at PCA 2.3.3 or earlier should take heed of the Note box in section "8g) Refresh the physical disks". This affects systems that have had Fibre-Channel storage systems added.

This document applies only to PCA 2.3.1 and later. For earlier releases refer to "[ PCA <= 2.2.2 ] How to Rebuild an Oracle VM Manager Database ( including User-Friendly Names) On a Private Cloud Appliance (Doc ID 2224820.1)"

 

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) Download and install the "virtualRx-pca" rpm and additional scripts.
 1a) Copy the rpm to the active management node and install it
 1b) Download and copy the required scripts to the Active Management node
 Please only use the utilities specified in this document. Any other utilities included in the RPM should only be used after approval from Oracle support.
 2. [PCA 2.3.1 ONLY] Replace the ovm_core_3.4.2.1398.ear
 2a) On Primary Management Node
 2b. On the non-Primary Management Node
 3) Backup Model Dump XML files needed later in the process
 4) Record site-specific information
 5) The "pca-reinstall-ovmm" script.
 5a) Review the "pca-reinstall-ovmm" man page
 5b) Run the pca-reinstall-ovmm script.
 6. Discover the Compute Nodes
 6a) IP Address to use for discovery
 6b) 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
 8a) In the OVM Manager UI, click on the Storage Tab, then in either of the top panes click on the icon "Discover SAN Servers"
 8b) The "Access" pane will then display.
 8c) The "Add Admin Servers" pop-up will then display
 8d) The "Manage Access Group" pane will then display
 8e) Add other Storage arrays
 8f) Add any NFS Servers with the settings noted down during the preparation phase.
 8g) Refresh the physical disks
 9) Re-implement local customizations previously made
 10) Repeat Step 9 for each Custom Tenant group
 11) Refresh the Repositories
 11a) Automated:
 11b) Manually:
 12). Restore the Simple Names for PCA and Oracle VM
 13). Local repositories presentation
 14). Re-establish yum repositories in OVM Manager if necessary
 14a) [Only for PCA 2.3.x and earlier] Verify existence of yum repository "ovm.repo"
 14b) [Only for PCA 2.3.x and earlier] Add yum repository "ovm.repo"
 14c) [Only for PCA 2.3.x and earlier] Add "upgrade" repositories if required.
 15) Restore PCA settings for OVM Manager defaults
 15a) Run the vm_settings.py script, e.g.:
 15b) Run the ovmm_tuning.py script. e.g.:
 15d) Verify the new values have taken effect, e.g.:
 16) Configure each server for IPMI
 17). Verify the passwords of the servers / databases
 18). Remove the virtualRx-pca rpm
References


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