5.4 Upgrading Oracle VM Manager

This section describes procedures for upgrading Oracle VM Manager.

5.4.1 Running the Script to Upgrade Oracle VM Manager

The runInstaller.sh script included on the Oracle VM Manager installation ISO includes an option that allows you to perform an upgrade of a previous version of Oracle VM Manager.

# ./runInstaller.sh
Oracle VM Manager Release 3.4.x Installer

Oracle VM Manager Installer log file:
/tmp/ovm-manager-3-install-yyyy-mm-dd-xxxxxx.log

Please select an installation type:
   1: Install
   2: Upgrade
   3: Uninstall
   4: Help

   Select Number (1-4): 2

Verifying upgrading prerequisites ...
*** WARNING: Ensure that each Oracle VM Server for x86 has at least 200MB of available space for the /boot partition and 3GB of available space for the / partition.
Starting Upgrade ...

Reading database parameters from config ...

It is also possible to trigger the upgrade process by passing the correct installtype parameter on the command line:

# ./runInstaller.sh --installtype Upgrade

If you do not have both the zip and unzip packages installed on the system that you are upgrading, the installer exits with an error notifying you to install these packages before proceeding with the upgrade.

You are prompted to provide the passwords for each component during the upgrade procedure. You must enter the password you set for that component during the original installation, or the current password if it has been changed since installation.

A log of the upgrade is available in the /var/log/ovmm/ovm-manager-3-install-date-id.log file.

Important

After you successfully upgrade Oracle VM Manager to Release 3.4, you must not discover or interact with any instances of Oracle VM Server earlier than Release 3.2.10.

If you discover an instance of Oracle VM Server that is earlier than Release 3.2.10 with Oracle VM Manager Release 3.4, an error message is returned for the job and conflicts occur between the databases that Oracle VM Manager requires for maintaining synchronization between internal components.

To upgrade Oracle VM Manager:

  1. Log in to the Oracle VM Manager host computer as the root user.

  2. Oracle VM Manager must be running to perform the upgrade. If Oracle VM Manager is not running, start it. On Linux:

    # service ovmm start

    If Oracle VM Manager is not running when you run the installation script, an error is returned by the script and the installer exits.

  3. Mount the Oracle VM Manager ISO file or create bootable physical media. See either Section 1.3, “Installation From Bootable Physical Media” or Section 1.4, “Loopback ISO Mounts” for more information.

  4. Start the Oracle VM Manager installation script, for example:

    # cd /mnt
    # ./runInstaller.sh

    The installer starts and presents you with a variety of options:

    Oracle VM Manager Release 3.4.x Installer
    
    Oracle VM Manager Installer log file:
    /var/log/ovmm/ovm-manager-3-install-yyyy-mm-dd-xxxxxx.log
    
    Please select an installation type:
       1: Install
       2: Upgrade
       3: Uninstall
       4: Help
    
       Select Number (1-4): 2
    Verifying upgrading prerequisites ...
    *** WARNING: Ensure that each Oracle VM Server for x86 has at least 200MB of available space for the /boot partition and 3GB of available space for the / partition.
    Starting Upgrade ...
    
    Reading database parameters from config ...

    Enter the menu number for the Upgrade option and press Enter to continue with the upgrade. You are prompted for the password that must be used to access the current Oracle VM Manager database:

    Typically the current Oracle VM Manager database password will be the same as the 
    Oracle VM Manager application password.
    
    Database Repository
    ==========================
    Please enter current Oracle VM Manager database password for user ovs:  

    Enter the password that should be used to access the database for the ovs user. If you set a system-wide password during the original installation and have not changed the database password at any stage, this password should be used here. This password continues to be used for the database after the upgrade is complete. If you enter this password incorrectly and the installer is unable to access the database, the installer exits with an error message.

    The installer prompts you for the current Oracle VM Manager password. This is the same password that you use to log into the Oracle VM Manager Web Interface, using the admin username.

    Oracle VM Manager application
    =============================
    Please enter current Oracle VM Manager application password for user admin:

    Enter the password. If you set a system-wide password during the original installation and have not changed the admin user password at any stage, this password should be used here. This password continues to function after the upgrade. If you intend to change it, you must do so after the upgrade is complete.

    The installer prompts you to enter the Oracle WebLogic Server password.

    Oracle WebLogic Server 12c
    ==========================
    Please enter the current password for the WebLogic domain administrator:

    You are prompted for the system's FQDN (fully qualified domain name) or IP address to use during the generation of the SSL certificate that should be used for HTTPS connections to Oracle VM Manager:

    Please enter your fully qualified domain name, e.g. ovs123.us.oracle.com, 
    (or IP address) of your management server for SSL certification 
    generation 192.168.0.254 [192.168.0.254]: manager.example.com

    It is important that you specify the hostname, fully qualified domain name or the IP address that is to be used when accessing the Oracle VM Manager Web Interface, so that the SSL certificate hostname matches the hostname portion of the URL entered into the web browser.

    The installer completes verification checks to see if the Oracle VM Manager database passwords for the root and appfw users match the database password for the user ovs. If either of these user passwords differ, the upgrade tool displays a password verification failure message for the user and then prompts you to enter the current Oracle VM Manager database password for the required user. For example, as follows for the user root:

    Password verification for the user root failed
    Please enter the current Oracle VM Manager database password for the user root:

    The installer then verifies that the password entered matches the current database password for the user and displays a successful password verification message. For example, as follows for the user root:

    Successfully verified password for user root

    The installer displays the current release number and the release number to which Oracle VM Manager is to be upgraded, and presents a final option to exit from the upgrade process:

    Verifying configuration ...
    Verifying 3.x.y.z meets the minimum version for upgrade ...
    
    Upgrading from version 3.x.y.z to version 3.4.v.w
    
    Start installing the configured components:
       1: Continue
       2: Abort
    
       Select Number (1-2): 1

    Select the Continue option to continue with the upgrade process.

    Running full database backup ...
    Successfully backed up database to /u01/app/oracle/mysql/dbbackup/3.x.y_preUpgradeBackup-
    yyyymmdd_xxxxxx

    The upgrade process automatically ensures that the database for the current installation is fully backed up prior to starting the upgrade. This ensures that you are able to roll back to the version that you currently have installed if something fails during the upgrade process. This backup file is located in /u01/app/oracle/mysql/dbbackup/.

    A pre-upgrade script runs prior to the actual upgrade process to prepare the environment for upgrade. If you are upgrading from Oracle VM Manager Release 3.2.10, this script removes any existing job history. This process can take quite some time, depending on the number of jobs in the job history. The pre-upgrade process provides output that indicates the number of jobs that must be deleted at different stages of its progress so that you can monitor its status:

    Running ovm_preUpgrade script, please be patient this may take a long time ...
     
    timestamp: Deleting 4163 Jobs before upgrade.
    timestamp: 200 Jobs have been deleted. 3963 Jobs remaining.
    timestamp: 400 Jobs have been deleted. 3763 Jobs remaining.
    timestamp: 600 Jobs have been deleted. 3563 Jobs remaining.
    timestamp: 800 Jobs have been deleted. 3363 Jobs remaining.
    ...
    timestamp: 3800 Jobs have been deleted. 363 Jobs remaining.
    timestamp: 4000 Jobs have been deleted. 163 Jobs remaining.
    timestamp: Jobs have been deleted.
    

    Regardless of the release that you are upgrading from, the pre-upgrade script also checks for any jobs that are still running. In the case that it discovers jobs that are running, it prints the details of these jobs to the screen and provides the option to force quit and delete these jobs, or to abort the upgrade:

    timestamp ERROR: Job test1 is in the 
    CONSTRUCTING state and was created on timestamp
    Would you like to delete the jobs above? Saying no will cancel the upgrade:
       1: Yes
       2: No
    

    If you press 2 here, the upgrade process aborts and exits immediately. If you press 1 here, any running jobs are quit and deleted and the following output is displayed:

    timestamp ERROR: Job test1 is in the 
    CONSTRUCTING state and was created on timestamp
    timestamp:  1  jobs have been deleted.
    

    The rest of the upgrade process is automated and continues as follows:

    Exporting weblogic embedded LDAP users
    Stopping service on Linux: ovmcli ...
    Stopping service on Linux: ovmm ...
    Exporting core database, please be patient this may take a long time ... 
    NOTE: To monitor progress, open another terminal session and run: 
    tail -f /var/log/ovmm/ovm-manager-3-install-YYYY-MM-DD-HHmmss.log 
    
    Product component : Java in '/u01/app/oracle/java'
    Java is installed ...
    
    Removing Java installation ...
    
    Installing Java ...
    
    DB component : MySQL RPM package
    MySQL RPM package installed by OVMM was found...
    Removing MySQL RPM package installation ...
    
    Installing Database Software...
    Retrieving MySQL Database 5.6 ...
    Unzipping MySQL RPM File ...
    Installing MySQL 5.6 RPM package ...
    Configuring MySQL Database 5.6 ...
    Installing MySQL backup RPM package ...
    
    Product component : Oracle VM Manager in '/u01/app/oracle/ovm-manager-3/'
    Oracle VM Manager is installed ...
    Removing Oracle VM Manager installation ...
    
    Product component : Oracle WebLogic Server in '/u01/app/oracle/Middleware/'
    Oracle WebLogic Server is installed
    
    Removing Oracle WebLogic Server installation ...
    Service ovmm is deleted.
    Service ovmcli is deleted.
    
    Retrieving Oracle WebLogic Server 12c and ADF ...
    Installing Oracle WebLogic Server 12c and ADF ...
    Applying patches to Weblogic ...
    Applying patches to ADF ...
    
    Installing Oracle VM Manager Core ...
    Retrieving Oracle VM Manager Application ...
    Extracting Oracle VM Manager Application ...
    
    Retrieving Oracle VM Manager Upgrade tool ...
    Extracting Oracle VM Manager Upgrade tool ...
    Installing Oracle VM Manager Upgrade tool ...
    Installing Oracle VM Manager WLST Scripts ...
    
    Dropping the old database user 'appfw' ...
    Dropping the old database 'appfw' ...
    Creating new domain...
    Creating new domain done.
    Upgrading core database, please be patient this may take a long time ...
    NOTE: To monitor progress, open another terminal session and run: 
    tail -f /var/log/ovmm/ovm-manager-3-install-YYYY-MM-DD-HHmmss.log
    Starting restore domain's SSL configuration and create appfw database tables.
    Restore domain's SSL configuration and create appfw database tables done.
    AdminServer started.
    Importing weblogic embedded LDAP users
    
    Retrieving Oracle VM Manager CLI tool ...
    Extracting Oracle VM Manager CLI tool...
    Installing Oracle VM Manager CLI tool ...
    
    Configuring Https Identity and Trust...
    Deploying Oracle VM Manager Core container ...
    Configuring Client Cert Login...
    Deploying Oracle VM Manager UI Console ...
    Deploying Oracle VM Manager Help ...
    Disabling HTTP access...
    
    Retrieving Oracle VM Manager Shell & API ...
    Extracting Oracle VM Manager Shell & API ...
    Installing Oracle VM Manager Shell & API ...
    
    Retrieving Oracle VM Manager Wsh tool ...
    Extracting Oracle VM Manager Wsh tool ...
    Installing Oracle VM Manager Wsh tool ...
    
    Retrieving Oracle VM Manager Tools ...
    Extracting Oracle VM Manager Tools ...
    Installing Oracle VM Manager Tools ...
    Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
    Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
    Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
    
    Enabling Oracle VM Manager service ...
    Shutting down Oracle VM Manager instance ...
    Starting Oracle VM Manager instance ...
    Waiting for the application to initialize ...
    Oracle VM Manager is running ...
    
    Please wait while WebLogic configures the applications...
    
    Installation Summary
    --------------------
    Database configuration:
      Database type               : MySQL
      Database host name          : localhost
      Database name               : ovs
      Database listener port      : 49501
      Database user               : ovs
    
    Oracle WebLogic Server configuration:
      Administration username     : weblogic
    
    Oracle VM Manager configuration:
      Username                    : admin
      Core management port        : 54321
      UUID                        : UUID
    
    
    Passwords:
    There are no default passwords for any users. The passwords to use for Oracle VM Manager, 
    Database, and Oracle WebLogic Server have been set by you during this installation. In the 
    case of a default install, all passwords are the same.
    
    Oracle VM Manager UI:
      https://manager.example.com:7002/ovm/console
    Log in with the user 'admin', and the password you set during the installation.
    
    For more information about Oracle Virtualization, please visit:
      http://www.oracle.com/virtualization/
    
    As of Oracle VM Release 3.4.5, the TLSv1.2 protocol is used for all connections and management of 
    3.2.10/11 servers is not possible by default. TLSv1 protocol must be enabled, which is less secure.
    For instructions, see the Oracle VM 3.4 Installation and Upgrade guide.
    
    Oracle VM Manager upgrade complete.
    
    Please remove configuration file /tmp/ovm_configxyz.

5.4.2 Removing Temporary Files After Upgrade

If you have upgraded from a release prior to 3.4, you must remove the temporary files that are created as part of the upgrade process. These files can be used by Oracle Support to help you recover your environment if something goes wrong with your upgrade and you did not take adequate steps to backup your database before the upgrade. However, they also contain information about your entire environment that should not be left in temporary file space indefinitely.

It is important that you verify that your upgrade has completed successfully and that Oracle VM Manager is fully functional before you remove these temporary files. Log into the Oracle VM Manager Web Interface and check that your environment is configured as it was prior to upgrade. Check that you are able to perform actions on your Oracle VM Servers and storage via the Oracle VM Manager Web Interface. If your environment is functional, you can proceed with the removal of the temporary files generated by the upgrade.

To remove temporary files after upgrade, do the following as the root user on the Oracle VM Manager host:

# rm -Rf /tmp/workdir_sel*
# rm -Rf /tmp/ovm*

On many systems, temporary files are deleted automatically on reboot. If you have any concern about security after an upgrade, in most cases a system reboot ensures that these files are cleaned up properly.