My Oracle Support Banner

Upgrading Oracle Big Data Appliance Cluster to V4.14 with Mammoth (Software Deployment Bundle) Release V4.14 Frequently Asked Questions (FAQ) (Doc ID 2568347.1)

Last updated on MARCH 10, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.14.0 to 4.14.0 [Release 4.10]
Linux x86-64

Purpose

This document provides answers to frequently asked questions on how to upgrade and install an Oracle Big Data Appliance cluster to Oracle Big Data Appliance 4.14 using Mammoth (Software Deployment Bundle). 

 

Questions and Answers

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
Purpose
Questions and Answers
 Does Oracle Big Data Appliance 4.14 Support Oracle Linux 5?
 Questions on 4.13 and Oracle Linux 7
 On BDA V4.14 is it necessary to migrate Oracle Linux 6 or Oracle Linux 7?
 On BDA V4.14 is there a migration utility yet to migrate OL6 to OL7?
 Is it possible to install BDA V4.14 on a Oracle Linux 6 base image?
 On new 4.14 installs done on the OL7 4.10.0-<latest> base image is it expected that Step 3 to update the base image will require a reboot?
 After the reboot step of an upgrade to BDA V4.14 if there are mixed kernel versions due to one or more nodes not having their kernel upgraded is that going to be a problem?
 When performing an upgrade to Oracle Big Data Appliance (BDA) V4.14 is it ok to be in Maintenance Mode to avoid Cloudera Manager upgrade-related alerts?
 Do Mammoth installs and upgrades require internet access?
 If a cluster needs to be upgraded and expanded what activity is recommended to do first cluster upgrade or cluster expansion?
 If the BDA has been changed from its original layout will that be a problem during upgrade?
 What exactly is the rolling part of the rolling upgrade?
 Does the cluster need to be in "Good Health" before upgrading to Oracle Big Data Appliance (BDA) V4.14?
 Can you upgrade with a decomissioned node?
 What happens if ssh login of the 'oracle' user to BDA nodes has been disabled for security purposes?
 Will CM Host Inspector "warnings" impact upgrade?
 What Hadoop (CDH) version is on Oracle Big Data Appliance (BDA) V4.14?
 What does Cloudera 5.16.1 Enterprise include?
 Does BDA V4.14 continue to support security options for CDH Hadoop clusters?
 Are any new parcels included with BDA V4.14?
 Is it possible to bypass upgrading Spark2 during Mammoth upgrade to BDA 4.14 so that it remains at the pre-upgrade version?
 Are there any new recommendations regarding using Microsoft Active Directory to configure a cluster?
 Does the BDA upgrade to 4.14 impact existing sentry and Kerberos configurations?
 On BDA V4.14 can the R release and the Oracle R Advanced Analytics for Hadoop release be independently upgraded?
 On BDA V4.14 the Oracle Distribution for R be independently upgraded?
 On BDA V4.14 can Solr be upgraded to a higher version?
 On any CDH version is it possible to upgrade to a higher version of Solr?
 Regarding Big Data SQL will the Exadata prerequisites change in BDA V4.14  from previous releases?
 What version of NoSQL is on Oracle Big Data Appliance (BDA) V4.14?
 Are there two separate bundles for BDA 4.14 one for OL 6 and one for OL 7?
 How many zipfiles does the Mammoth deployment have in BDA V4.14?
 Is a BDA Base Image being released for V4.14.0?
 Can the second Mammoth bundle deployment zip file be used for reimaging?
 What new features does Oracle Big Data Appliance 4.14.0 include? 
 What about Scripts for Download & Configuration of Apache Zeppelin, Jupyter Notebook, and RStudio?
 What about improved Configuration of Oracle's R Distribution and ORAAH?
 What about support for Kerberos on a Kafka cluster?
 What about a custom Rprofile for BDA?
 Since a custom Rprofile is now set up on the BDA how do users know to copy the file from $R_HOME/etc/RBDAProfiles to $R_HOME/etc?
 What else is new in BDA V4.14?
 Are there any other Mammoth deployment changes?
 Based on the above new HA features what about MySQL HA?
 Is Big Data Manager supported on clusters secured by Active Directory?
 After an upgrade are the new kernel files copied into the Internal USB drive(/dev/sdm) automatically?
 Is Java upgraded in BDA V4.14?
 Regarding HTTPS/Network Encryption, how is that enabled after upgrade?
 What about upgrading with HDFS transparent encryption, KMS Proxy Servers, and Key Trustee Servers?
 Do CM, Hue and Oozie use HTTPS security by default?
 If the Oozie CM parameter "Enable TLS/SSL for Oozie" is off but the other configurations which are part of cluster_https_hue_oozie are enabled and bdacli cluster_https_cm_hue_oozie returns true will that cause any problems during Mammoth upgrade?
 Is there is an interactive bdscli utility on the BDA?
 Is Oracle Big Data Discovery supported on BDA V4.14 at this time?
 Are there any changes for installing/uninstalling the Enterprise Manager plugin on BDA 4.14?
 Can an upgrade to BDA V4.14 be performed from any previous BDA version?
 Does this mean that an upgrade from a pre-V4.1 can not go directly to BDA V4.14.0?
 Does this mean that an upgrade from a V2.4 will have a multiple upgrade path for example?
 If multiple upgrades are required to get to BDA 4.14 does the critical metadata need to be backed up each time?
 Will there be any problem upgrading BDA V4.14 from a supported BDA version if CDH has been upgraded from the default to one of the certified CDH versions?
 For example can the version of Oracle Instant Client be updated?
 In BDA V4.14 is TLS 1.0 (TLS v1) disabled by default?
 Does BDA V4.14 with CDH 5.16.1 support TLS Version 2 for Impala, Resource Manager, and Hiveserver2?
 During or after upgrade to BDA V4.14.0 can you rollback to a previous BDA version?
 Is it possible to dual boot a starter rack to have BDA V4.13 and V4.14 by using one system disk for BDA V4.13 and one for BDA V4.14?
 What about upgrading a CDH client, will that also require a two step approach?
 The BDA servers are at CDH 5.16.1 Is it a problem if client/ servers are running CDH 5.16.<x>?
 If a non BDA edge is removed from a cluster prior to BDA upgrade, how is its CDH version upgraded to that on the upgraded BDA cluster?
 If the BDA is running CDH 5.16.1 with Oracle Linux 6.10 for example can a non BDA edge node be added into the cluster if it is running RHEL 6.10?
 If an edge node is added into the cluster, does the edge node need to have the same kernel as the rest of the cluster?
 On a BDA cluster based on Oracle Linux 6 what Linux variants are supported on edge nodes?
 On a BDA cluster based on Oracle Linux 7 what Linux variants are supported on edge nodes?
 If a BDA cluster is running Oracle Linux 6 are edge nodes running Oracle Linux 7 ok?
 Are all nodes of the cluster, however,  required to have the exact same parcel version?
 Does BDA V4.14 support the BdaDeploy.json file?
 What version of the Oracle BDA Configuration Generation Utility is required for this release?
 Is Spark-on-YARN configured on the BDA V4.14 ?
 If a cluster is running Standalone Spark, what will the Mammoth upgrade do since Spark-on-YARN is now configured in BDA V4.14? 
 After upgrade is it possible to upgrade Spark-on-YARN or Standalone Spark?
 What about Impala and Search are they configured on the BDA V4.14?
 If Impala Llama was manually configured will that impact upgrade to BDA V4.14?
 Are all Impala table stats cleared when Impala is upgraded during a Mammoth upgrade?
 If the Mammoth upgrade fails do I have to create a SR and upload the diagnostic bundle generated?
 Where is the BDA V4.14 documentation?
 What is the direct link to the documentation "New features" section?
 Are there any deprecated features?
 Are there any Big Data Spatial and Graph deprecated features?
 After upgrade why is the Sqoop2 service in Cloudera Manager reporting "Sqoop2 is deprecated and will no longer be supported in CDH 6."?
 Where is the Big Data Connector's documentation?
 What happens if you need to upgrade the Oracle Data Integrator Application Adapter for Hadoop to a version higher than provided by Mammoth?
 What is the impact on upgrade of installing standalone ODI and then enabling Big Data Connectors (BDC)?
 What is the impact on upgrade if there are two separate ODI agents running on the same BDA one maintained by Mammoth and one standalone?
 If a patch is installed, will that be impacted by upgrade?
 Is the CDH Deployment still parcel based?
 When upgrading to BDA V4.14 do any one-off patches need to be applied?
 BDA V4.14 includes CDH 5.16.1.  Is it possible to upgrade to a higher CDH version?
 What about patching after the upgrade now that BDA V4.14 is parcel based?
 Is the expectation that the upgrade removes R packages or Connectors?
 When upgrading to BDA V4.14 if the cluster verification step fails can Mammoth be rerun?
 Does this mean that if the last step of the upgrade fails but re-running "mammoth -c" is successful then the upgrade is considered complete?
 Is it possible to run ./mammoth -c in the middle of an upgrade to see how things look?
 Is it possible to run ./mammoth -c after executing the run command i.e. BDAMammoth-CDH-ol6-<version>.run just to give a final check on cluster state?
 How can the last step run by Mammoth be found?
 If Mammoth upgrade or install fails, how is it possible to find the step to resume from?
 If there is a problem with a Mammoth step on upgrade or install is it possible to skip it?
 What can be done to resolve "Acquiring installation lock"  errors when adding a client/edge node back into a CDH cluster after upgrade?
 Can the client hostnames and/or priviate InfiniBand IP addresses be changed during the upgrade?
 After upgrade the user 'bdatestuser' was not available.  Why is that?
 Does Mammoth create an oracle user for general use?
 If a cluster is running AD Kerberos why is an AD Kerberos Admin password required?
 If a cluster is running AD Kerberos and the cluster verifications are run standalone is an oracle user required?
 After upgrade there is a problem using the 'hdfs' principal when AD Kerberos is enabled.   Why is that?
 What is the recommended way to integrate Kerberos with Active Directory (AD) on the BDA?
 Does the httpd service need to run on Node 1 during upgrade?
 Questions on Tomcat in BDA V4.14
 After upgrade how can the Tomcat version be identified?
 What is the Tomcat used for?
 Does Tomcat always run on the BDA on BDA V4.14?
 In the case of multiple clusters should the VLANs be the same in all clusters or could be different in every cluster?
 Now that 3 node clusters are supported is it possible to have a 3 node production cluster?
 Where is the Cloudera documentation on CDH 5.16?
 Where is the Cloudera documentation on CDH 5.16.1 Known Issues?
 If MS Active Directory is in trust with MIT Kerberos is Used is there a Way to Block Users from Connecting and Running Jobs or Batch Updates During an Upgrade?
 What about MegaCli64, any changes?
 Is a BDA upgrade possible if one of the servers is down?
 If one of the ILOMs is down is it possible that a BDA upgrade can proceed?
 Is it possible to upgrade the ILOM to the latest version outside of Mammoth?
 Will the BDA upgrade the ILOM firmware?
 Questions/Answers on handling predictive disk failures before/during upgrade.
 If any disks that exhibit "other" errors fail or get into a failing (predictive error) state, right before upgrade or during upgrade what problems will be faced?
 What about a disk that is in bad health right before upgrade?
 What about a disk that fails during upgrade?
 Should we remove any failing disks from CM from the DataNode Data Directory dfs.data.dir, i.e. remove the mount /u0x/hadoop/dfs from there?
 What is a summary of the failed/failing disk issue and upgrade?
 Can you expand a cluster if one of the new nodes has a bad disk?
 If MySQL replication is not working on the MySQL slave, Node 2 by default, is it ok to proceed with the upgrade?
 If a MySQL slave is in the process of a mysql import can upgrade proceed?
  If a cluster expansion is underway and MySQL replication is observed to be off  can it be enabled during the expansion?
 In BDA V4.14 what are the restrictions on extending a cluster?
 Will changing the root password after install is complete affect the system?
 Can Mammoth installation work when clusters span several racks?
 Is it possible to have different root passwords on different nodes prior to upgrade?
 If upgrading with AD Kerberos, why would there appear to be no user: hdfs@<REALM.NAME>?
 If Sentry is configured and Kerberos is not configured, is it ok to upgrade?
 Does the Mammoth upgrade manage Kafka on yarn?
 Does the Mammoth upgrade manage flume?
 The ASR password is requested on upgrade. What happens if it is unavailable?
 What is the correct firmware for the PDU, Cisco switches, Infiniband switches(spine/leaf), for Mammoth 4.13?
References

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