This chapter provides information on upgrading to Oracle Exalytics Release 2 (2.2.0.0.0.ovs-3.2.9) on virtual deployments. For information on upgrading to Oracle Exalytics Release 2 on non-virtual deployments, see Chapter 2, "Upgrading to Oracle Exalytics Release 2 (2.0.0.0.el5) on Non-Virtual Deployments."
Note:
Oracle Exalytics Release 2 can only be applied on an Oracle Exalytics Release 1 Patchset 5 (Oracle Exalytics Base Image 1.0.0.7). If you are on an earlier patchset, you must upgrade to Oracle Exalytics Release 1 Patchset 5 (Oracle Exalytics Base Image 1.0.0.7) before you can upgrade to Oracle Exalytics Release 2.This chapter includes the following sections:
Section 3.1, "About Oracle Exalytics Release 2 on Virtual Deployments"
Section 3.2, "Guidelines for Upgrading to Oracle Exalytics Release 2 on Virtual Deployments"
Section 3.5, "Upgrading Oracle Exalytics for Oracle VM 3.0.3 or Later Version to Oracle VM 3.2.9"
Section 3.6, "Applying the Oracle Exalytics Release 2 Upgrade on a Virtualized Environment"
Section 3.7, "Configuring Flash on an Exalytics Machine Configured for Virtualization"
Section 3.10, "Deinstallation Instructions for the Oracle Exalytics Release 2"
Oracle Exalytics Release 2 for X2-4, X3-4, X4-4, and X5-4 Exalytics Machines consists of the following system software components:
Exalytics Base Image for Oracle VM x86-64 (2.2.0.0.0.ovs-3.2.9)
Exalytics VM Upgrade Patch (Guest) for Linux 5 (2.2.0.0.0.el5)
Exalytics VM Template (Guest) for Linux 5 (2.2.0.0.0.el5)
Exalytics VM Template (Guest) for Linux 6 (2.2.0.0.0.el6)
The Oracle Exalytics Release 2 on virtual deployments comprises of updates to the system components that are listed in listed in Table 3-1.
Table 3-1 System Components and Supported Versions in Oracle Exalytics Release 2 on Virtual Deployments
| System Component | Version in Release 2 | Kernel Version |
|---|---|---|
|
Oracle Exalytics Base Image for Oracle VM |
2.2.0.0.0.ovs-3.2.9 |
2.6.39-400.215.9.el5uek x86_64 |
|
Oracle Exalytics VM Upgrade Patch (Guest Linux 5) |
2.2.0.0.0.el5 |
2.6.39-400.248.3.el5uek x86_64 |
|
Oracle Exalytics VM Template (Guest Linux 5) |
2.2.0.0.0.el5 |
2.6.39-400.248.3.el5uek x86_64 |
|
Oracle Exalytics VM Template (Guest Linux 6) |
2.2.0.0.0.el6 |
2.6.39-400.248.3.el6uek x86_64 |
Oracle Business Intelligence, Oracle Enterprise Performance Management, Oracle TimesTen for Exalytics, Oracle Database In-Memory, and Oracle Endeca software releases are certified on Exalytics Release 2. These software updates may contain new capabilities built for Exalytics only. Customers are advised to update the application software stack with the latest Exalytics certified version.
For detailed information on system components and supported application product components, see Oracle Exalytics Certification Matrix at the following location:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Review the following guidelines before upgrading to Oracle Exalytics Release 2:
Ensure that you are currently on Oracle Exalytics Release 1 Patchset 5 (Oracle Exalytics Base Image 1.0.0.7).
Before upgrading, ensure that you back up your current installation, configuration files, and any user-specific artifacts, and stop all applicable services.
If you have installed Oracle Enterprise Performance Management components on the Exalytics Machine, stop all Enterprise Performance Management services before upgrading. Also, ensure that you start all services after upgrading. For more information, see "Chapter 12, Starting and Stopping EPM System Products" in Oracle Enterprise Performance Management System Installation and Configuration Guide Release 11.1.2.3 at the following location:
http://docs.oracle.com/cd/E40248_01/epm.1112/epm_install.pdf
When upgrading from Oracle Exalytics Oracle Exalytics Release 1 Patchset 5, delete aggregates in Oracle TimesTen using the nqcmd utility. For more information, see "Creating and Persisting Aggregates for Oracle BI Server Queries" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
For late-breaking information, see Oracle Exalytics In-Memory Machine Release Notes for Linux.
This upgrade is available to all Exalytics virtualization customers who are running Oracle VM server 3.0.3 or later version and Oracle VM Manager 3.0.3 or later version. This upgrade is available on Exalytics X2-4, X3-4 and X-4, servers currently running OVM manager and OVM server 3.0.3 or later. To configure X5-4 servers for virtualization, you must install OVM Manager and OVM server 3.3.3.
Note:
Oracle recommends that all current customers running Exalytics virtualization upgrade to Oracle Exalytics Release 2. X5-4 servers cannot be upgraded to Release 2, but can be re-imaged according to the instructions in Chapter 5, "Configuring Exalytics Machine for Virtualization."The following prerequisites must be met before you can upgrade to Oracle Exalytics Release 2 on an Exalytics Machine configured for virtualization:
You have one or more Exalytics Machines configured for virtualization.
You have upgraded to Oracle VM Server 3.2.9 and Oracle VM Manager 3.2.9 or later version.
You have added Oracle VM Server to your Oracle VM Manager environment. To add Oracle VM Servers to your Oracle VM Manager, see Section 5.1.2.2.3, "Discovering Oracle VM Servers."
Note:
If you have already upgraded to Oracle VM 3.2.9, you can ignore this section and go directly to Section 3.6, "Applying the Oracle Exalytics Release 2 Upgrade on a Virtualized Environment."Note:
Currently, upgrading to OVM 3.3.3 is not supported. It is suggested to re-image /install OVM 3.3.3 on X5-4 to use the NVME Flash cards according to the instructions in Chapter 5, "Configuring Exalytics Machine for Virtualization."This section consists of the following topics:
Oracle VM Manager provides a graphical user interface to manage Oracle VM Servers, virtual machines, and resources.
Note:
If you are installing Oracle VM Manager for the first time, you can install Oracle VM Manager 3.2.9 directly. For information, see Section 5.1.2.2, "Installing and Configuring Oracle VM Manager."To upgrade Oracle VM Manager 3.0.3 or later version to 3.2.9:
Navigate to http://edelivery.oracle.com/oraclevm and perform the following steps:
In the Select a Product Pack list, select Oracle VM.
In the Platform list, select x86-64 bit.
Click Go.
Select Oracle VM 3.2.9, x86-64 bit, and click Continue.
Download Oracle VM Manager 3.2.9 - Upgrade only (Part Number V74421-01).
Follow the readme instructions for upgrading Oracle VM Manager.
Note:
If you are configuring Exalytics Machine for virtualization for the first time, you can install Oracle VM Server 3.2.9 directly. For information on installing Oracle VM Server 3.2.9, see Section 5.1.2.1, "Installing and Configuring Oracle VM Server."Upgrading Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or later version to Oracle VM Server 3.2.9 consists of the following steps:
This section consists of the following topics:
Editing the Grub Configuration File to Increase Memory
Edit the Grub configuration file to increase the allocated memory from 2 GB to 16 GB.
To edit the Grub configuration file to increase memory:
Log on as the root user.
Open the /etc/grub.conf file in a text editor.
Change the allocated memory from 2 GB to 16 GB.
Modify the kernel /xen.gz line in grub.conf file so it displays as follows:
kernel /xen.gz dom0_mem=16384M allowsuperpage dom0_vcpus_pin dom0_max_vcpus=20 no-bootscrub
Modify the module/vmlinuz line in the grub.conf file so it displays as follows:
module /vmlinuz-2.6.39-300.32.6.el5uek ro root=UUID=5d6c3568-1894-41cd-80d9-5d190b4529f5 no-bootscrub swiotlb=131072
Stop and start Oracle VM Server. For instructions, see "Stopping and Starting Oracle VM Server".
Stopping and Starting Oracle VM Server
To stop and start Oracle VM Server:
To stop and start Oracle VM Server, perform the following steps:
Stop all applicable processes running on the Exalytics Machine.
Stop all virtual machines running on the server.
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, expand Server Pools, and then select the server pool containing the Exalytics Machine.
Right-click the Exalytics Machine, and select Restart Server.
The Oracle VM Server stops and starts automatically.
Confirm that Oracle VM Server has restarted.
Upgrading Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or Later Version to Oracle VM Server 3.2.9
Before you upgrade Oracle VM Server, ensure that you have upgraded Oracle VM Manager.
To upgrade Oracle VM Server 3.0.3 (Base Image 2.0.1.1) or a later version to Oracle VM Server 3.2.9:
Stop Oracle VM Server, by performing the following steps:
Stop all applicable processes running on the Exalytics Machine.
Stop all virtual machines running on the server.
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, expand Server Pools, and then exalytics_server_pool.
Right-click the Exalytics Machine, and select Stop Server.
For more information, see "Section 6.10.7 Stopping Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Business Intelligence.
In the Platform list, select Linux X86-64.
Click Go.
Select Oracle Exalytics Software Media Pack for Linux x86-64 (Release 2.0.0.0).
Click Continue.
Download and unzip the Oracle Exalytics Base Image 2.2.0.0.0 for Exalytics Oracle VM x86-64 file (part number V 76307-01) to a local directory.
The zip file contains the following iso file:
Exalytics_2.2.0.0.0_Upgrade_OVS-3.2.9-751_<DATE>.iso: You use this iso file to upgrade to Oracle VM Server 3.2.9.
On the Exalytics Machine, connect and log on to Oracle Integrated Lights Out Manager (ILOM).
Note:
If you are upgrading to Oracle VM Server 3.2.9 on an X2-4 or X3-4 Exalytics Machine, you must use ILOM 3.1.2.24.d. If you are upgrading to Oracle VM Server 3.2.9 on an X4-4 or X5-4 Exalytics Machine, you must use ILOM version 3.2.4.18 or later version.For the latest Exalytics certified ILOM versions, see the Oracle Exalytics Certification Matrix. The Oracle Exalytics Certification Matrix is located at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
On the Summary Information screen, under Actions, click Launch to launch the Remote Console.
The ILOM remote console is displayed.
Depending on the configuration of the Exalytics Machine, perform one of the following actions:
For X2-4 or X3-4 Exalytics Machine, in ILOM version 3.1.2.24.d, from the menu bar, select Devices, then CD-ROM Image to link the Oracle VM Server 3.2.9 upgrade image (Exalytics_2.2.0.0.0_Upgrade_OVS-3.2.9-751_<DATE>.iso) as a remote virtual CD-ROM in ILOM.
For X4-4 or X5-4 Exalytics Machine, in ILOM version 3.2.4.18, from the menu bar, select KVMS, then Storage. Click Add to link to the Oracle VM Server 3.2.9 upgrade image (Exalytics_2.2.0.0.0_Upgrade_OVS-3.2.9-751_<DATE>.iso) as a remote virtual CD-ROM in ILOM. Click Connect.
In the left pane of the ILOM, expand Host Management, then click Host Control. In the Next Boot Device list, select CDROM, then click Save.
Restart the machine by expanding in the left pane of the ILOM, Host Management, then click Power Control. In the Select Action list, select Power Cycle, then click Save.
The Exalytics Machine restarts and the CD Found screen is displayed.
Press OK to start the media test.
The Media Check screen is displayed.
Press Test to test the CD in the drive.
At the conclusion of the test, the Media Check Result screen is displayed.
Press OK.
The Media Check screen is displayed.
Press Continue.
The Keyboard Selection screen is displayed.
Select the model keyboard attached to the Exalytics Machine, and click OK.
The OVS EULA screen is displayed.
Press Accept.
The System to Upgrade screen is displayed.
Select the currently installed Oracle VM Server, and press OK.
The Upgrade Boot Loader Configuration screen is displayed.
Select Skip updating boot loader configuration, and press OK.
Press OK.
Confirm the upgrade completes successfully, and then press Reboot.
The Exalytics Machine restarts.
Perform the following steps to rediscover the upgraded Oracle VM Server:
Connect to Oracle VM Manager.
Select the Servers and VMs tab.
In the left pane, expand Server Pools, and then exalytics_server_pool.
Right-click the Exalytics Machine and select Rediscover Server.
Enter the following information for the server:
- Oracle VM Agent Port. The default port number is 8899.
- Oracle VM Agent Password. The default password is "oracle".
- IP Address.
Click OK.
For more information, see "Section 6.10.7 Stopping Oracle VM Servers" in Oracle VM User's Guide for Release 3.2.
This section consists of the following topics:
You upgrade the Exalytics Base Image for Oracle VM 2.2.0.0.0 by applying the upgrade patch on Oracle VM Server. The patch upgrades the Base Image to 2.2.0.0.0, installs Flash drivers and utilities.
Note:
This step is mandatory for all Exalytics virtualized servers when installing Release 2.0.0.0.0.To upgrade Oracle Exalytics Base Image for Oracle VM to 2.2.0.0.0:
Navigate to My Oracle Support and download patch number 20431965: Patchset Upgrade Utility for Exalytics Base Image 2.2.0.0.0 Oracle VM for Linux x86-64. The patch contains the p2.6.39-400.248.3.el6uek x86_64 .zip file.
The zipped file contains Flash drivers and Flash configuration scripts.
Log on to the Exalytics Machine as the root user.
Extract the contents of the file into an appropriate directory on the Exalytics Machine.
Unzip the file into a temporary (/tmp) directory.
The following directory is created:
exalytics_ovs_server_base_image_2.2.0.0.0.ovs-3.2.9
Navigate to the directory by entering the following command:
# cd exalytics_ovs_server_base_image_upgrade_to_2.2.0.0.0
To upgrade the Base Image to 2.2.0.0.0 and to install Flash, enter the following command:
# /update.sh
The output looks similar to the following:
current_kernel_version=2.6.39-400.215.9.el5uek
minimum_kernel_version=2.6.39-400.215.9.el5uek
OS Version check passed..
Update to 2.2.0.0.0.ovs-3.2.9 starting at DAY-DD-MM-YYYY HR:MIN:SEC
Removing unnecessary packages...
Skipping removing rpm kernel-ib-devel as it doesn't exist...
Skipping removing rpm kernel-ib as it doesn't exist...
Skipping removing rpm ibvf-config as it doesn't exist...
Removing RPM OpenIPMI-tools ...
Done
Running new install steps...
Preparing... ################################################## [100%]
exalogic.tools ################################################## [100%]
--------------------------------------------------------
Successfully installed exalogic.tools
--------------------------------------------------------
.....[exalogic.tools] := Post Transaction called...............
Running update...
Applying libibumad
Preparing... ################################################## [100%]
libibumad ################################################## [100%]
Preparing... ################################################## [100%]
libibmad ################################################## [100%]
Preparing... ################################################## [100%]
openib ################################################## [100%]
Preparing... ################################################## [100%]
opensm-libs ################################################## [100%]
opensm ################################################## [100%]
error: Failed dependencies:
infiniband-diags is needed by ovsvf-config-1.0-10.noarch
Preparing... ################################################## [100%]
infiniband-diags ################################################## [100%]
Preparing... ################################################## [100%]
exalytics-flash ################################################## [100%]
postInstall (exalytics-flash) 1 ...
[EXALYTICS_INFO:GENERAL] Updating exalytics-flash-config file to set FLASH_INSTALL_TYPE=OVS ...
postInstall (exalytics-flash) 1; done
Preparing... ################################################## [100%]
Installing....
Lib_Utils ################################################## [100%]
MegaCli ################################################## [100%]
Preparing... ################################################## [100%]
hesiod ################################################## [100%]
autofs ################################################## [100%]
sas_snmp ################################################## [100%]
Starting snmpd
Starting snmpd: [ OK ]
Registering Service lsi_mrdsnmpd
Starting LSI SNMP Agent
Starting LSI SNMP Agent:LSI MegaRAID SNMP Agent Ver 3.18.0.2 (Oct 30th, 2012) Started
[ OK ]
Preparing... ################################################## [100%]
policycoreutils-1.33.12-14.8.el5
oracle-hmp-libs ################################################## [100%]
oracle-hmp-hwmgmt ################################################## [100%]
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
ipmiflash ################################################## [100%]
ipmitool ################################################## [100%]
mstflint ################################################## [100%]
oracle-hmp-snmp ################################################## [100%]
oracle-hmp-tools ################################################## [100%]
oracle-hmp-tools-biosconfig############################################# [100%]
oracle-hmp-tools
ubiosconfig ################################################## [100%]
QConvergeConsoleCLI ################################################## [100%]
Preparing... ################################################## [100%]
package glibc-common-2.5-123.0.1.el5_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el5_11.1.x86_64 is already installed
package glibc-2.5-123.0.1.el5_11.1.i686 is already installed
package nscd-2.5-123.0.1.el5_11.1.x86_64 is already installed
Removing bm flash scripts...
Running post install script...
Running post patch script
Setting SET_IPOIB_CM=yes
file /etc/sysconfig/network-scripts/ifcfg-bondib0 not found
/usr/lib/init-exalogic-node/init-ipoib.sh not exist in /etc/rc.local , nothing to delete
Completed post patch script
Enabling services...
Updating dom0 memory to 16G..
Copying Exa* files...
Updating imageinfo...
Image name in imageinfo is already uptodate
finished; DAY-DD-MM-YYYY HR:MIN:SEC
finished; DAY-DD-MM-YYYY HR:MIN:SEC
To verify that the upgrade was successful, enter the following command:
# imageinfo
The output looks similar to the following:
Exalytics 2.2.0.0.0.ovs-3.2.9 (build:r20150409.1) Image version : 2.2.0.0.0.ovs-3.2.9 Image build version : 20150409.1 Creation timestamp : DAY-DD-MM-YYYY HR:MIN:SEC Kernel version : 2.6.39-400.215.9.el5uek Image activated : DAY-DD-MM-YYYY HR:MIN:SEC Image status : SUCCESS
To verify that Flash is installed and the number of Flash cards installed, enter the following command for X2-4, X3-4, and X4-4 configurations:
# ddcli
For an X4-4 configuration, three Flash cards are displayed. For an X2-4 or X3-4 configuration, six Flash cards are displayed. The output looks similar to the following:
**************************************************************************** LSI Corporation WarpDrive Management Utility Version 107.00.00.04 (2012.06.05) Copyright (c) 2011 LSI Corporation. All Rights Reserved. **************************************************************************** ID WarpDrive Package Version PCI Address -- --------- --------------- ----------- 1 ELP-4x100-4d-n 06.05.09.00 00:11:00:00 2 ELP-4x100-4d-n 06.05.09.00 00:21:00:00 3 ELP-4x100-4d-n 06.05.07.00 00:31:00:00 4 ELP-4x100-4d-n 06.05.07.00 00:a1:00:00 5 ELP-4x100-4d-n 06.05.01.00 00:c1:00:00 6 ELP-4x100-4d-n 06.05.01.00 00:d1:00:00
To view the list of Flash cards in an X5-4 configuration, enter the following command:
#nvmead list
The output appears as follows:
SUNW-NVME-1 SUNW-NVME-2 SUNW-NVME-3
You can either upgrade Oracle VM Guest to 2.2.0.0.0 or create Oracle VM Guest 2.2.0.0.0. See Section 3.6.3, "Creating Oracle VM Guest 2.2.0.0.0."
Note:
You can only upgrade Oracle VM Guest on the same Linux operating system. For example, you cannot upgrade Oracle VM Guest that is installed on a Linux 5 operating system to Oracle VM Guest 2.2.0.0.0 that is installed on a Linux 6 operating system.You upgrade Oracle VM Guest to 2.2.0.0.0 by applying the patch on each Oracle VM Guest in your system. The patch upgrades Oracle VM Guest to 2.2.0.0.0.
Note:
You must apply the patch mentioned in this section on each Oracle VM Guest and not on Oracle VM Server.To upgrade Oracle VM Guest to 2.2.0.0.0:
Navigate to My Oracle Support and download patch number 20618011:Upgrade Utility for Exalytics Virtualized Guest from 2.0.1.4.0 to 2.2.0.0.0 that contains the p20618011_10060_Linux-x86-64.zip file.
Log in to Oracle VM Guest as the root user.
Using FTP, navigate to a temporary (/tmp) directory on the Exalytics Oracle VM Guest.
Enter the following commands to navigate to the /tmp directory and unzip the zip file:
# cd/tmp
# unzip p20618011_10060_Linux-x86-64.zip
Disable all existing yum repositories (if any), by performing the following actions:
Enter the following command to check for any existing repositories:
Check /etc/yum/repos.d/ directory
Set enabled=0 for each existing repository.
Enter the following command to run the upgrade script:
# ./update.sh
Restart Oracle VM Guest from Oracle VM Manager.
Enter the following commands to verify the current RPM versions:
# uname - rm
The following output is displayed:
2.6.39-400.248.3.el5uek x86_64
# cat /etc/oracle-release
The following output is displayed:
Oracle Linux Server release 5.11
To verify that the upgrade was successful, enter the following command:
# imageinfo
For the Linux 5 operating system, the output looks similar to the following:
Exalytics 2.2.0.0.0.el5 (build:r04102015.1) Image version : 2.2.0.0.0.el5 Image build version : 04102015.1 Creation timestamp : DAY-DD-MM-YYYY HR:MIN:SEC Kernel version : 2.6.39-400.248.3.el5uek Image activated : DAY-DD-MM-YYYY HR:MIN:SEC Image status : SUCCESS
For the Linux 6 operating system, the output looks similar to the following:
Exalytics 2.2.0.0.0.el6 (build:r04102015.1) Image version : 2.2.0.0.0.el6 Image build version : 04102015.1 Creation timestamp : DAY-DD-MM-YYYY HR:MIN:SEC Kernel version : 2.6.39-400.248.3.el6uek Image activated : DAY-DD-MM-YYYY HR:MIN:SEC Image status : SUCCESS
Note:
You can ignore this section if you have upgraded Oracle VM Guest to 2.2.0.0.0. See Section 3.6.2, "Upgrading Oracle VM Guest to 2.2.0.0.0."This section consists of following topics:
To install and configure Oracle VM Guest 2.2.0.0.0, you must download the latest VM templates.
To download VM templates:
Navigate to the Oracle Software Delivery Cloud web site at the following link:
In the Select a Product Pack list, select Oracle Business Intelligence.
In the Platform list, select Linux X86-64.
Click Go.
Select Oracle Exalytics Software Media Pack for Linux x86-64 (Release 2.0.0.0).
Click Continue.
Depending on the Linux operating system, perform one of the following actions:
To install VM template on a Linux 5 operating system, download the template, Oracle Exalytics Oracle VM Template 2.2.0.0.0.el5, Part Number: V76308-01.
To install VM template on a Linux 6 operating system, download the template Oracle Exalytics Oracle VM Template 2.2.0.0.0.el6, Part Number: V76309-01.
Save the template on a web server.
Importing VM Templates into Oracle VM Manager
After downloading the templates, you import them into Oracle VM Manager.
To import VM templates into Oracle VM Manager:
Log on to Oracle VM Manager.
Select the Repositories tab.
In the left pane, select the Repository in which you want to store the template.
Select VM Templates.
In the toolbar, click Import VM Template to display the Import VM Template dialog.
Select the Oracle VM Server and enter the URL or FTP server to the VM template that you downloaded on the web server.
Click OK to import the VM template.
Creating Virtual Machines from VM Template
After importing the template in Oracle VM Manager, you use the template to create virtual machines.
Before you create virtual machines, keep the following guidelines in mind:
Ensure that Hyperthreading is disabled on Oracle VM Server.
Note:
Oracle recommends that Hyperthreading be disabled when creating new virtual machines.Maximum number of virtual machines you can create for a non-InfiniBand configuration on an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is ten.
Total virtual processors (vCPUs) you can assign on Oracle VM Server for an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is ten.
Total memory you can allocate on Oracle VM Server for an X2-4, X3-4, X4-4, and X5-4 Exalytics Machine is 16 GB.
Review Table 3-2 for the total vCPUs and memory you can allocate on all virtual machines and the maximum vCPUs and memory you can allocate to each virtual machine.
Table 3-2 Total and Maximum vCPUs and Memory Allowed For Virtual Machines
| System | Total vCPUs for all Virtual Machines | Maximum vCPUs for each Virtual Machine | Total RAM for all Virtual Machines | Maximum RAM for each Virtual Machine |
|---|---|---|---|---|
|
X2-4 |
40 |
28 |
984 GB |
800 GB |
|
X3-4 |
40 |
28 |
984 GB |
800 GB |
|
X4-4 |
60 |
28 |
1984 GB |
800 GB |
|
X5-4 |
72 |
28 |
1984 GB |
800 GB |
Note:
For the X2-4 and X3-4 Exalytics Machine, total memory on Oracle VM Server (Dom0) (16 GB) and all virtual machines (984 GB) cannot exceed 1000 GB. For the X4-4 and X5-4 Exalytics Machine, total memory on Oracle VM Server (Dom0) (16 GB) and all virtual machines (1984 GB) cannot exceed 2000 GB.To create virtual machines from the VM template:
Select the Servers and VMs tab.
Log on to Oracle VM Manager.
In the left pane toolbar, click Create Virtual Machine.
The Create Virtual Machine dialog is displayed.
Select Clone from an existing VM Template.
Perform the following steps:
In the Clone Count list, select the number of machines you want to clone.
In the Repository list, select a repository for the machine.
In the VM Template list, select the VM template from which you want to create the virtual machine.
Enter a name for the virtual machine.
In the Server Pool list, select a server pool.
Enter a description for the virtual machine.
Click Finish.
The virtual machine is created and is ready to be configured.
To configure and start a virtual machine, configure a network on a virtual machine, and configure SWAP on a virtual machine, see Section 5.6, "Maintaining Virtual Machines."
Note:
When you start the virtual machine for the first time, the virtual machine takes approximately fifteen minutes to initialize.For more information, see "Chapter 7, Managing Virtual Machines" in Oracle VM User's Guide for Release 3.2.
This section is applicable only for the following customers who have Flash storage:
Customers running Exalytics X3-4, X4-4 or X5-4 machines
Customers running Exalytics X2-4 machines with Upgrade kits (Flash Upgrade Kit or Memory and Flash Upgrade Kit
Note:
The following customers can ignore this section:Oracle Exalytics X2-4 customers who do not have Upgrade kits (Flash Upgrade Kit or Memory and Flash Upgrade Kit).
Oracle Exalytics X3-4 or X2-4 customers with Upgrade kits who have already configured Flash.
To verify that you have already configured Flash, navigate to Oracle VM Manager and confirm that the names of the Flash drives in Oracle VM Manager are the same as the names specified in the FlashDriveMappings file.
This section consists of the following topics:
Section 3.7.1, "Configuring Flash on Oracle VM Server on X2-4, X3-4, and X4-4 Machines"
Section 3.7.3, "Configuring RAID1 for Flash in Oracle Virtual Machine on X5-4 Machines"
Each X2-4 and X3-4 Exalytics Machine contains six 400 GB Flash cards. Each Flash card contains four 100 GB drives, for a total of 24 individual drives with a capacity of 2400 GB. Each X4-4 Exalytics Machine contains three 800 GB Flash card. Each Flash card contains four 200 GB drives, for a total of 12 individual drives with a capacity of 2400 GB. Each X5-4 Exalytics Machine contains three 1600 GB Flash card. Each Flash card contains four 400 GB drives, for a total of 12 individual drives with a capacity of 4800 GB.You next configure Flash to enable names of the Flash drives on Oracle VM Server to be read by Oracle VM Manager.
Note:
Before Oracle Exalytics X2-4 customers with Flash Upgrade kits can configure Flash, they must have Oracle Field Services engineers install six Flash cards on the Exalytics Machine being used for virtualization.To configure Flash on Oracle VM Server:
Log on to the Exalytics Machine as the root user.
To create a FlashDriveMappings file, enter the following command:
# /opt/exalytics/bin/exalytics_flashovsrepos.sh -script > ~/flashDriveMappings
The FlashDriveMappings file extracts the names of the Flash drives on Oracle VM Server into a text file.
Navigate to the /root directory to view the text file.
On Oracle VM Server, copy the FlashDriveMappings file to the /opt/exalytics/bin/exalytics_ovm_scripts/ folder and then tar the FlashDriveMappings file by entering the following commands:
# cd /opt/exalytics/bin/
# tar -cvf exalytics_ovm_scripts.tar exalytics_ovm_scripts/
Copy the tar file to the machine where Oracle VM Manager is installed.
Connect to machine where Oracle VM Manager is installed.
Navigate to the directory where you copied the scripts and the FlashDriveMappings file.
To untar the file, enter the following command:
# tar -xvf exalytics_ovm_scripts.tar
To confirm that the "expect" package is available, enter the following command:
# rpm -qa | grep expect
If the "expect" package is not available, install it before proceeding to Step 10.
To rename the Flash drives in Oracle VM Manager, navigate to the exalytics_ovm_scripts folder and enter the following command:
# ./exalytics_ovm_rename_flash.sh <path_to _flashmappingfile> <Oracle VM Manager Username> < Oracle VM Manager Password> <Exalytics_Machine_Configuration>
where Exalytics_Machine_Configuration is x2-4, x3-4, x4-4, or x5-4.
The names of the Flash drives in Oracle VM Manager now appears the same as the names specified in the FlashDriveMappings file.
Attach the Flash drives to Oracle VM Manager by performing the following tasks:
In Oracle VM Manager, select the Server and VMs tab.
In the left pane, select the server pool on which the virtual machine resides.
From the Perspective list, select Virtual Machines.
In the Management pane, select a virtual machine.
In the toolbar, click Edit.
The Edit Virtual Machine dialog is displayed.
Click the Disks tab.
Under Disk Type, select Physical Disk.
Under Actions, select Select a Virtual Machine Disk.
Select a Physical Disk page is displayed.
Select the Flash card you want to attach to Oracle VM Guest Machine, and click OK.
Repeat the previous step to attach other Flash cards to Oracle VM Guest Machine.
In Oracle VM Manager, select the Servers and VMs tab.
In the left pane, expand Server Pools, and then select exalytics_server_pool.
From the Perspective list, select Virtual Machines.
In the Management pane, select a virtual machine.
Click the expand arrow to the left of the selected virtual machine.
Click the Disks tab.
Confirm that the Flash drives attached to Oracle VM Guest Machine are displayed.
RAID Level 1 is usually referred to as mirroring. RAID Level 1 duplicates data from one drive on a second drive so that if either drive fails, no data is lost. This is useful when reliability is more important than data storage capacity.
The following procedure assumes you have attached the Flash drives to Oracle VM Manager.
Note:
In this example, RAID1 is configured for two (xvdb and xvdc) Flash drives that are on two different Flash cards. Depending on your configuration, you can configure RAID1 for a different number of Flash drives.To configure RAID1 for Flash in Oracle Virtual Machine:
Connect as a root user to the Oracle Virtual Machine to which you attached the Flash drives.
Identify the Flash drives.
For example: xvdb and xvdc
To configure RAID1 for the two Flash drives (xvdb and xvdc), enter the following command:
# /sbin/mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/xvdb /dev/xvdc
To add the RAID1 configuration to the RAID configuration file, enter the following command:
# mdadm --detail --scan --verbose >> /etc/mdadm.conf
This enables the RAID configuration to be recognized when Oracle VM Manager restarts.
To create a file system on the new RAID1 device, enter the following command:
# mkfs -t ext4 /dev/md2
To create a new directory (/u02) on the virtual disk, enter the following command:
# mkdir -p /u02
To mount the RAID1 on this directory, enter the following command:
# mount /dev/md2 /u02
/u02 is created as the new Flash drive.
To update the file system, enter the following command:
# echo "/dev/md2 /u02 ext4 defaults 0 0" >> /etc/fstab
The following procedure assumes you have attached the Flash drives to Oracle VM Manager. This procedure is valid only for Oracle VM Server 3.3.3 running on X5-4 machines.
Note:
In this example, RAID1 is configured for two Flash drives that are on two different Flash cards. Depending on your configuration, you can configure RAID1 for a different number of Flash drives.To configure RAID1 for Flash in Oracle Virtual Machine:
Connect as a root user to the Oracle Virtual Machine to which you attached the Flash drives.
Identify the Flash drives.
Select flash drives from two different flash controllers. For example, the flash cards are displayed as nvme1n1p1, nvme2n1p1. The values nvme1 and nvme2 indicate the controller. Select nvme1n1p1 and nvme2n1p1 for the RAID configuration.
To configure RAID1 for the two Flash drives (nvme1n1p1 and nvme2n1p1), enter the following command:
# /sbin/mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/nvme1n1p1 /dev/nvme2n1p1
mdadm: /dev/nvme1n1p1 appears to be part of a raid array: level=raid1 devices=3 ctime=Tue Nov 10 11:15:30 2015 mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90 mdadm: /dev/nvme2n1p1 appears to be part of a raid array: level=raid1 devices=3 ctime=Tue Nov 10 11:15:30 2015 Continue creating array? yes mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md1 started.
To add the RAID1 configuration to the RAID configuration file, enter the following command:
# mdadm --detail --scan >> /etc/mdadm.conf
This enables the RAID configuration to be recognized when Oracle VM Manager restarts.
Edit /etc/mdadm.conf file and apply following changes:
Remove the line with the entry: # DEVICE /no/device
Add the following entries for nvme devices:
DEVICE /dev/nvme0n1p* /dev/nvme1n1p* /dev/nvme2n1p*
Create a partition on the new RAID1 device by entering the following command:
# parted /dev/md1p1
(parted) mklabel msdos (parted) mkpart primary 1MiB -1MiB (parted) unit s print (to validate partition was created correctly) (parted) quit
The partition can range from 1 MiB to any GB value based on user needs.
Find the vm.cfg file which corresponds to the VM Guest on which you want the RAID device to be mounted:
Go to Oracle VM Manager.
Select the Repositories tab and select the main repository for your system.
Note the repository ID.
Select the Servers and VMs tab.
Edit the OVM Guest, select the Configuration tab, and note the VM ID.
The vm.cfg file will be located under the directory with the repository ID number and VM ID number. It appears as /OVS/Repositories/<repository ID number>/VirtualMachines/VM ID number/vm.cfg.
Add the newly created partition md1p1 to vm.cfg. This will create /dev/xvdb on the VM guest when the guest is started.
Note:
Steps a through c below show a sample repository ID number and VM ID number. Your repository ID and VM ID number will be different and you will need to substitute the ID for your specific VM in the sample commands given as follows.Save the original /OVS/Repositories/0004fb0000030000b25b4b2848c959f4/VirtualMachines/0004fb000006000043ee01db14c067f2/vm.cfg to vm.ori.
Edit the vm.cfg file using the following command:
vi /OVS/Repositories/0004fb0000030000b25b4b2848c959f4/VirtualMachines/0004fb000006000043ee01db14c067f2/vm.cfg
If a virtual disk is previously allocated, add or modify the following line (with highlighted text):
disk = ['file:/OVS/Repositories/0004fb0000030000b25b4b2848c959f4/VirtualDisks/0004fb0000120000afd68c2d37f266a2.img,xvda,w', 'phy:/dev/md1p1,xvdb,w']
If no other disk is previously allocated, add the following line:
disk = [ 'phy:/dev/md1p1,xvdb,w']
Save a copy of the modified vm.cfg by entering the following command:
cp vm.cfg vm.cfg_PostFlash
Start the Oracle VM Guest and mount the device xvdb:
Login to Oracle VM Guest as root user.
Create a partition using the following command:
parted /dev/xvdb (parted) mklabel msdos (parted) mkpart primary 0 -1MiB (parted) quit
Format the partition using the following command:
mkfs -t ext3 /dev/xvdb1
Create a new directory (/u02) by entering the following command, if it does not exist:
# mkdir -p /u02
Mount the RAID1 on this directory by entering the following command:
# mount /dev/md2 /u02
Update the /etc/fstab on Oracle VM Guest to remount the device when guest is rebooted:
Edit the /etc/fstab on Oracle VM Guest:
vi /etc/fstab
Add the following line:
/dev/xvdb1/u02 ext3 defaults 0 0
Note:
This section is for existing Exalytics virtualization customers that are already running application software components. New Exalytics virtualization customers, proceed to Chapter 6, "Installing Software on an Exalytics Machine."Depending on your deployment, upgrade and patch newly certified application software components for this release.
Before you upgrade and patch the application software components, ensure you are installing the latest Exalytics certified software application versions. See Oracle Exalytics Certification Matrix for the latest certifications. The Oracle Exalytics Certification Matrix is located at:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
The process of upgrading and patching application software components on virtual machines is similar to upgrading and patching them on the non-virtualized Exalytics Machine. For more information, see the following:
Note:
This section is for existing customers that are upgrading or patching Oracle Business Intelligence software. New customers, proceed to Chapter 6, "Installing Software on an Exalytics Machine."To ensure that Oracle Business Intelligence Enterprise Edition and Oracle TimesTen data type mapping and other optimizations are consistent and can be leveraged, you must complete postinstallation steps for the following Oracle Exalytics components:
This section contains the following topics:
To ensure Oracle Business Intelligence Enterprise Edition sets the Oracle TimesTen checkpoint frequency, perform the following configuration steps after upgrading Oracle TimesTen In-Memory Database. Failure to perform this configuration may adversely affect Oracle TimesTen performance.
To configure Oracle TimesTen checkpoint frequency:
Open the timesten-install-dir/info/sys.odbc.ini file.
Find the DSN entry for the schema used for Aggregate Persistence.
Do one of the following:
If you are loading data in Oracle TimesTen database using aggregate persistence, edit the three parameters as follows:
CkptFrequency=-1
CkptLogVolume=0
CkptRate=0
If you are loading data in Oracle TimesTen database without using aggregate persistence, use a different server DSN and edit the three parameters as follows:
CkptFrequency=30
CkptLogVolume=0
CkptRate=0
To complete other postinstallation steps in Oracle TimesTen:
Re-create existing datastores for Oracle TimesTen.
If you are installing Oracle Exalytics Release 2 on Oracle Exalytics Release 1 Patchset 5, then rebuild aggregates using the nqcmd utility. For more information, see "Creating and Persisting Aggregates for Oracle BI Server Queries" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
This section contains the following topics:
For faster aggregation and better performance, Oracle recommends that you edit the opmn.xml file to include the appropriate elements. Ensure that you edit the opmn.xml file on each Exalytics Machine that is configured in a highly available clustered environment.
To edit the opmn.xml file to improve aggregation and performance:
Open the opmn.xml file (which is located in MW_HOME/instances/instance1/config/OPMN/opmn).
Insert the following child elements under <ias-component id="coreapplication_obis1" inherit-environment="true"><environment>:
<variable id="ORACLE_BI_TT_DISABLE_REDO_LOGGING" value="1"/>
Creates faster aggregation.
<variable id="ORACLE_BI_TT_PARALLEL_INDEX_CREATION" value="1"/>
Creates indexes in parallel, thereby creating faster aggregation.
<variable id="ORACLE_BI_TT_BACKGROUND_CHECKPOINT_INTERVAL" value="6"/>
This BI Server controlled parameter determines the frequency of Oracle TimesTen datastores that are stored to disk (datastore persistence). The default value is every 10 seconds. The smaller the number of the "value", the more often Oracle TimesTen stores datastores to disk.
Stop and start the Notification Server.
Go to the following directory that contains the OPMN command-line tool:
MW_HOME/instances/instance1/bin
Enter the following command:
./opmnctl stopall
Stops OPMN and all Oracle Business Intelligence system components.
Enter the following command:
./opmnctl startall
Starts OPMN and all Oracle Business Intelligence system components.
For information about installing Oracle Business Intelligence Client Tools, see "Installing and Uninstalling Oracle Business Intelligence Client Tools" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
If you experience any problems after upgrading, then Oracle recommends that you roll back all Oracle Exalytics component patches. Do not rollback one or two individual component patches. Instructions for rollback are included in the component-specific ReadMe files.
If you encounter any issues while applying the upgrade, then contact Oracle Support.