Preface
The Oracle Big Data SQL User's Guide describes how to use and manage the Oracle Big Data SQL product.
Audience
This guide is intended for administrators and users of Oracle Big Data SQL, including:
-
Application developers
-
Data analysts
-
Data scientists
-
Database administrators
-
System administrators
The guide assumes that the reader has sufficient background knowledge about the database server and the particular Hadoop platform which will host the software in order to follow the instructions successfully.
Related Documents
See the Oracle Big Data SQL Installation Guide for instructions on installing the product.
See the Oracle Big Data Appliance Owner's Guide for information about using the Oracle Big Data SQL with Oracle Big Data Appliance.
Conventions
The following text conventions are used in this document:
Convention | Meaning |
---|---|
boldface |
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
italic |
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
|
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |
|
The pound ( |
Backus-Naur Form Syntax
The syntax in this reference is presented in a simple variation of Backus-Naur Form (BNF) that uses the following symbols and conventions:
Symbol or Convention | Description |
---|---|
[ ] |
Brackets enclose optional items. |
{ } |
Braces enclose a choice of items, only one of which is required. |
| |
A vertical bar separates alternatives within brackets or braces. |
... |
Ellipses indicate that the preceding syntactic element can be repeated. |
delimiters |
Delimiters other than brackets, braces, and vertical bars must be entered as shown. |
boldface |
Words appearing in boldface are keywords. They must be typed as shown. (Keywords are case-sensitive in some, but not all, operating systems.) Words that are not in boldface are placeholders for which you must substitute a name or value. |
Changes in Oracle Big Data SQL 3.2.1.1
Oracle Big Data SQL Release 3.2.1.1 includes the following changes.
New Database Compatibility Parameter for the Jaguar Installer
The configuration file that is passed to the Jaguar installer now accepts an optional database_compatibility
parameter:
This parameter gives you a way to save on system resources (particularly memory) if all databases connected to a cluster are of the same version of Oracle Database. Oracle Big Data SQL provides a different offloader process for each supported version of Oracle Database. In this release, there are offloader process for Oracle Database 12.1 and 12.2. By default, both are running. If you only need Oracle 12.1 connections or 12.2 connections, but not both, then you can use database_compatibility
to prevent start up of the offloader process that you do not need.
This parameter is within the cluster
section of the configuration file. We set compatibility to 12.1 in this example:
"cluster" : {
"database_compatibility" : [ "12.1" ]
}
Like any other configuration parameter, you can change this later by running a jaguar reconfigure
operation.
Installation Differences on Exadata Database Machine RAC Systems and non-Exadata Database Machine RAC Systems
Note:
The following apply only to Oracle Big Data SQL 3.2.1.1 and only for installations on RAC Systems running on commodity hardware (RAC systems that are not Exadata Database Machines).- Only Ethernet is supported for connections between Oracle Database 12.2 and the Hadoop cluster.
- There are special steps specific to Oracle Big Data SQL 3.2.1.1 that you must follow the first time that you install the database side of the software on the database nodes. The details are provided in Steps for Installing on Oracle Database Nodes in the installation guide.
Known Limitations Reported in Release 3.2.1 That are Resolved in 3.2.1.1
- JSON CLOB predicate pushdown is working in Release 3.2.1.1
- In Release 3.2.1, storage indexes for an Oracle Big Data SQL table may not be utilized where the following DDL operation is performed:
ALTER TABLE table_name PROJECT COLUMN REFERENCED;
This is also fixed in Release 3.2.1.1.