To upgrade to Oracle Exalytics Release 2.2 from Oracle Exalytics Release 2.1, perform the following steps:
Step 1: Run the Oracle Exalytics Base Image Release 2.2 Upgrade Script
Run the upgrade script to upgrade Oracle Exalytics base image to 188.8.131.52.el6
If you are upgrading to Oracle Exalytics Release 2.2 from Oracle Exalytics Release 2.1 (Base Image 184.108.40.206.el6), the script installs new rpms without affecting your existing installation.
Before the upgrade, ensure that all yum channels are disabled, and the
/etc/yum.conf file does not cause restriction on updates.
To check if all yum channels are disabled, run the command
# yum repolist, and see if the output of the yum repository lists
To run the Oracle Exalytics Base Image Upgrade Script:
Stop and backup all Oracle Business Intelligence, Oracle TimesTen, and (if installed) Enterprise Performance Management services.
For information on stopping Oracle Business Intelligence services, see "Starting and Stopping Oracle Business Intelligence" in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
For more information on starting and stopping Enterprise Performance Management services, see "Chapter 12, Starting and Stopping EPM System Products" in Oracle Enterprise Performance Management System Installation and Configuration Guide at the following locations:
Oracle Enterprise Performance Management System Installation and Configuration Guide Release 220.127.116.11 at
Oracle Enterprise Performance Management System Installation and Configuration Guide Release 18.104.22.168 at
Navigate to My Oracle Support and download the required patch number:
Patchset Upgrade Utility for Exalytics Base Image 22.214.171.124.el6 for Linux x86-64: Patch number 26419001. The patch contains the p26419001_20002_Linux-x86-64_el6.zip file.
Unzip the patch file into a temporary (/tmp) directory.
Navigate to the temporary directory.
The zipped file contains the nodeupdate.sh located in the directory with the patch ID for upgrade and the bug number for compute node (For the release 126.96.36.199.0 it is /tmp/26419001/26419001/).
To validate the patch for the Exalytics Machine, enter the following command:
# ./nodeupdate.sh -v
To apply the patch and upgrade the Oracle Exalytics base image, enter the following command:
# ./nodeupdate.sh -a
After the patch is successfully applied, restart the Exalytics Machine using Oracle Integrated Lights Out Manager (ILOM).
Optional: View the log files at /var/log/exalytics/update-188.8.131.52.log and /var/log/exalytics/exalytics.log.
Restart the Oracle Business Intelligence, Oracle TimesTen, and Enterprise Performance Management services.
To confirm the base image, enter the following command as a root user:
The output looks similar to the following:
Image version : 184.108.40.206_el6 Creation timestamp : Wed 10 Jan 2018 04:53:35 PM EST Kernel version : 4.1.12-94.5.9.el6uek.x86_64 RPM versions: kernel-uek-4.1.12-124.17.2.el6uek.x86_64 exalytics-container-bm-220.127.116.11-2_el6.x86_64 exalytics-scripts-18.104.22.168-13_el6.noarch exalytics-flash-22.214.171.124-6_el6.x86_64 exalytics-domain-configure-126.96.36.199-4_el6.noarch exalytics-deps-exact-188.8.131.52-2_el6.x86_64 exalytics-deps-minimum-184.108.40.206-2_el6.x86_64
Even though the build numbers may be different than the ones listed above, ensure that the updated kernel version is the same as the one displayed above.
Step 2: (Optional) Configure ASR
To configure ASR:
If you upgrade to Oracle Exalytics Release 2.2 on a new machine, then configure ASR as follows:
Follow instructions detailed in "Installing Auto Service Request (ASR)" in Oracle Exalytics In-Memory Machine Owner's Guide Exalytics X2-4, X3-4, X4-4, X5-4, and X6-4, but change the following steps:
Replace Step 5 in "Section 9.3 Before You Begin" with the following steps:
Navigate to the /opt/exalytics/asr directory and add the following line to the /etc/inittab file
At the command line, enter the following command to initialize and start the bda_mon server
Replace the commands in Step 2 in "Section 9.7 Configuring Telemetry Sources" with the following commands:
# cd /opt/exalytics/asr
# ./setup_asr_ilom.pl -host <hostname OR ip>
If you upgraded to Oracle Exalytics Release 2.2 from Oracle Exalytics Release 2.1 and ASR is already configured, complete the following step to verify that ASR is running:
ps -ef | grep bda command to ensure that bda_mon_hw_asr_pl is running.
Step 3: (Optional) Configure Exalytics Host for Enterprise Manager Cloud Control Discovery
To configure Exalytics Host for Enterprise Manager Cloud Control Discovery:
If you installed Oracle Exalytics Release 2.2 on a new machine with Enterprise Manager Cloud Control (EMCC) deployed, then perform the following steps to configure EMCC to identify the Exalytics host.
Confirm that a SP System Identifier is set for the Exalytics Machine by performing the following steps:
Log on to Oracle Integrated Lights Out Manager (ILOM).
Expand System Information.
Confirm that a SP System Identifier is displayed.
Log on to ILOM and in the left pane of the ILOM, expand ILOM Administration, then select Identification. Ensure that the SP System Identifier value is populated with a unique value, such as "Oracle Exalytics AK00026925".
Log on to the Exalytics Machine.
Execute the command
chmod +x exalytics_configure_for_emcc.sh to grant execute permissions.
Execute the following command as a root user to create the file:
Review the output and ensure that the contents of the /var/exalytics/info/em-context.info file correctly displays the system identifier for the Oracle Exalytics machine. The system identifier should be identical to the system identifier you saw in Step (b) of this procedure.
If you upgraded to Oracle Exalytics Release 2.2 from Oracle Exalytics Release 2.1 with Enterprise Manager Cloud Control (EMCC) deployed, then complete the following step to verify that EMCC identifies the Exalytics host:
Review the contents of the /var/exalytics/info/em-context.info file and ensure that it correctly displays the system identifier for the Oracle Exalytics machine.
The system identifier should be identical to the system identifier displayed in the Oracle Integrated Lights Out Manager (ILOM) in Step (a) above.