Oracle Big Data Appliance 4.9 is focused on defect fixes and software stack version updates, including major updates to Oracle NoSQL, and Cloudera Enterprise (Cloudera Manager, CDH). There are few other customer-visible changes in this release.
The release includes following feature changes and software updates.
Software Updates
CM (Cloudera Manager) 5.11
CDH (Cloudera's Distribution including Apache Hadoop) 5.11
Cloudera Key Trustee 5.11
Oracle Big Data Connectors 4.9
Big Data SQL 3.1 (earlier releases are not supported)
Oracle Big Data Spatial & Graph 2.3
MySQL Enterprise Edition 5.7.18
Perfect Balance 2.10.0
Java JDK 8u131
Oracle Linux 6.9 UEK 4 (Oracle Linux Unbreakable Kernel, Release 4)
Mammoth v4.9.0 for Oracle Linux 5 is available (only for upgrades of clusters based on Oracle Linux 5).
Oracle Data Integrator Agent 12.2.1.1 (for Oracle Big Data Connectors)
Oracle R Advanced Analytics for Hadoop (ORAAH) 2.7.0
Oracle's R Distribution (ORD) 3.2.0
Oracle NoSQL Community Edition or Oracle NoSQL Database Enterprise Edition 4.4.6. Both optional.
Note that support is no longer available for Oracle NoSQL Database Community Edition.
Kudu 1.3
Kafka 2.1
Spark 2.1
The Cloudera parcels for Spark, Kudu, Kafka, and Key Trustee Server are included for your convenience, but are not deployed or configured by default.
See the Cloudera Documentation for information about CDH and Cloudera Manager 5.11.
Oracle Big Data Appliance Release 4.9 includes Oracle Big Data SQL 3.1 as a Mammoth installation option. You do not need to download this package from the Oracle Software Delivery Cloud.
Support for Migration From Oracle Linux 5 to Oracle Linux 6
The release includes scripts to assist with the upgrade to Oracle Linux 6, including file and configuration backup and restore.
At this time Oracle continues to fully support Oracle Big Data Appliance clusters on Oracle Linux 5 with no restrictions. We encourage customers to upgrade their clusters to Oracle Linux 6 to take advantage of increased stability and performance and a larger and more modern ecosystem of available applications. We will be phasing out support for Oracle Big Data Appliance clusters on Oracle Linux 5 over the next few releases and eventually no further upgrades of Oracle Linux 5 clusters will be supported.
See Migrating from Oracle Linux 5 to Oracle Linux 6 in the Oracle Big Data Appliance Owner’s Guide for details.
The network.json File is Being Replaced by Separate Files for Rack and Cluster Configuration (rack-network.json and cluster-network.json)
In all cases where you previously used network.json, you now should instead use rack-network.json and cluster-network.json. These two files together are functionally equivalent to network.json. In the current release, network.json is still supported. In a future release, support for network.json will be dropped.
When you generate a new configuration with the utility, copy rack-network.json and cluster-network.json to servers where you formerly would have copied network.json. For all configuration commands which formerly required network.json as a parameter, you should now specify rack-network.json and cluster-network.json together instead. For example, to re-image node 4 in a cluster, submit both files (comma-separated) as a parameter to the makebdaimage command:
# ./makebdaimage -usbint BDABaseImage-<version>_RELEASE.iso /opt/oracle/bda/rack-network.json,/opt/oracle/bda/cluster-network.json 4
Previously, this command expected network.json as the configuration file parameter:
# ./makebdaimage -usbint BDABaseImage-<version>_RELEASE.iso /opt/oracle/bda/network.json 4
This enhancement makes it easier to make network changes to a cluster of servers without affecting other servers on the same racks and makes it easier to make admin network changes to a rack without affecting the client or private networks.
Node Migration Requires Extra Step for Oracle Big Data SQL Support
If Oracle Big Data SQL is enabled, then you must disable it on the entire cluster prior to running bdacli admin_cluster migrate <node>. Re-enable it after the migration. Use the bdacli enable and disable commands.
Disable Oracle Big Data SQL across the cluster: bdacli disable big_data_sql
Perform the migration.
Re-enable Oracle Big Data SQL: bdacli enable big_data_sql
Deprecated or Discontinued Features
Oracle Audit Vault and Database Firewall not Installed or Supported
Oracle Audit Vault and Database Fireware (AVDF) has been dropped from the Mammoth installation and is not longer recommended for monitoring and auditing on Oracle Big Data Appliance 4.9. Cloudera Navigator is recommended as a replacement.
The Oracle Enterprise Manager Plug-In can no Longer be Enabled via bdacli
The bdacli command for enabling the Oracle Enterprise Manager Plug-in (bdacli enable em) is no longer available.
Oracle Big Data Discovery Installation on Oracle Big Data Appliance 4.9 not Supported
There is no build of Oracle Big Data Discovery that is compatible with Oracle Big Data Appliance 4.9 at this time.
Note:
The bdacli commands to check status and to disable AVDF and the Oracle Enterprise Manager Plug-in are still available.Previous Important Notices
The following notices were published for Oracle Big Data Appliance 4.8. If you did not install Release 4.8, you may not be aware of these changes:
Perfect Balance Auto-Invocation Discontinued
The Perfect Balance automatic invocation feature is no longer supported as of Perfect Balance 2.10. If you having been using automatic invocation, please switch to the Perfect Balance API.
Oracle NoSQL Database CE Support not Available
There is no longer an option to purchase support for Oracle NoSQL Database Community Edition.
TLS 1.0 (TLSv1) Disabled for Cloudera Configuration Manager and Hue – May Affect Some Browsers and Operating Systems
In order to improve security, Oracle Big Data Appliance has disabled TLS 1.0 for Cloudera Manager and Hue and also in the system-wide Java configuration. This can affect older browsers or operating systems.
It is recommended that you reconfigure or upgrade clients using TLS 1.0 to use newer encryption, but if necessary you can re-enable TLS 1.0 for Cloudera Manager and Hue.
For details, log on to My Oracle Support and search for BDA 4.8 Disables TLSv1 by Default For Cloudera Manager/Hue/And in System-Wide Java Configurations (Doc ID 2250841.1).
Configuring the Network on new Racks With an Installed Base Image Lower Than Oracle Big Data Appliance 4.5.0 Requires Special Configuration Steps
Log on to My Oracle Support and search for this document :Network Configuration Instructions for Shipped BDA racks with a BDA Base Image Less Than V4.5.0 (Doc ID 2135358.1).
Cross-Realm Trust to Microsoft Active Directory is Recommended Over Direct-Active-Directory
Oracle strongly recommends that customers using Oracle Big Data Appliance Clusters with Microsoft Active Directory configure their clusters to use cross-realm trust to Microsoft Active Directory and not use Direct-Active-Directory configuration for the Hadoop cluster.