Changes in Oracle Big Data SQL 3.2.1

F.1 Changes in Oracle Big Data SQL 3.2.1

Oracle Big Data SQL Release 3.2.1 includes several features that are not available in Release 3.2. There are no other enhancements or defect fixes in Release 3.2.1. Release 3.2 features are also included in this summary.

Support for Oracle Database 12.2.0.1

Release 3.2.1 can be installed on both Oracle Database 12.2.0.1 and 12.1.0.2. The same Oracle Big Data SQL 3.2.1 installation on a Hadoop cluster can connect to both Oracle Database 12.2.0.1 and 12.1.0.2.

Customers using Oracle Big Data SQL 3.2 do not need to upgrade to Release 3.2.1 if they connect to Oracle Database 12.1.0.2 only.

Note:

Patches must be applied on Oracle Database 12.x and Oracle Grid Infrastructure (when used). The applicable patches depend on the database version in use. Please refer to the Oracle Support Document 2119369.1 (Oracle Big Data SQL Master Compatibility Matrix) for details.

Exclusion of Edge Nodes

The installation now automatically excludes Hadoop edge nodes. In earlier releases, the BDS agent was installed on edge nodes in order to enable Copy to Hadoop. The BDS agent checks for installation prerequisites and these checks would sometimes fail on edge nodes. The BDS agent is no longer installed by default on edge nodes.

In addition, the Oracle Big Data SQL configuration file now has an optional excluded_nodes parameter where you can manually exclude nodes. It is possible, though not likely, that the installer may not identify a node as an edge node. You can use this parameter to manually identify missed edge nodes and then re-run the installer, but should rarely need to do so.

This parameter is in the network section of the configuration file.

   excluded_nodes :  [ "<fqdn_for_edge_node 1>","<fqdn_for_edge_node_2>","<fqdn_for_edge_node_3>" ]