The procedure for upgrading the software is the same whether you are upgrading from one major release to another or just applying a patch set.
Note:The easiest way to patch and upgrade a cluster is through the Oracle Big Data Cloud Service console. See
The process upgrades all components of the software stack including the firmware, Oracle Linux Unbreakable Enterprise Kernel (UEK), CDH, JDK, and Oracle Big Data Connectors.
To upgrade only Oracle Big Data Connectors, and no other components of the software stack, contact Oracle Support for assistance.
Software downgrades are not supported.
Upgrading the Software
Follow these procedures to upgrade the software on an Oracle Big Data Cloud Service cluster to the current version.
You must know the passwords currently in effect for the cluster, which the Mammoth utility will prompt you for:
Upgrading to the Current Software Version
Making sure cluster services are healthy before upgrade, and especially after reboot is very important. Manual steps will be needed to resume.
Upgrade the Oracle Big Data Cloud Service software to the current software version as follows. This is a summary. Refer to My Oracle Support (MOS) Doc ID 2101906.1 for details, including prerequisites, further information on the steps below, and known issues.
Note:All Oozie jobs should be stopped before the upgrade. Failure to do this may cause the upgrade to fail.
Download and unzip the Mammoth bundle, as described in Downloading the Mammoth Software Deployment Bundle.. Mammoth is a command-line utility for installing and configuring the Oracle Big Data Cloud Service software.
You must be logged in as root to node 1 of the cluster.
Change to the
# cd /opt/oracle/BDAMammoth
mammothcommand with the -p option:
# ./mammoth -p
Mammoth automatically upgrades the base image if necessary.
After all nodes reboot, perform the following checks.
# dcli -C uptime
# dcli -C ls -ltr /root/BDA_REBOOT_SUCCEEDED
Note: Note: If there is no
BDA_REBOOT_SUCCEEDED, check for
Verify that the kernel and JDK are upgraded.
# dcli -C uname -a # dcli -C java -version
Check that all Cloudera Configuration Manager services are healthy. You may need to manually restart some services.
Note:During any upgrade, it is crucial that all services in Cloudera Manager are healthy after the reboot before continuing. Failure to do so will result in upgrade failures.
After the reboot and the post reboot checks, log on to node 1 of the cluster and rerun
mammoth -pin order to resume the upgrade.
# cd /opt/oracle/BDAMammoth # ./mammoth -p
When the upgrade is complete, perform the post-upgrade validation steps described in the MOS document (Doc ID 2101906.1).