2 Installing Oracle Big Data SQL

Avoiding Kerberos Ticket Expiration

The system should run kinit on a regular basis, before letting the Kerberos ticket expire, to enable Oracle SQL Connector for HDFS to authenticate transparently. Use cron or a similar utility to run kinit. For example, if Kerberos tickets expire every two weeks, then set up a cron job to renew the ticket weekly.

You can download Oracle Big Data SQL from the Oracle Software Delivery Cloud

Services Running

The following services must be running at the time of the Big Data SQL installation

• HDP

• Ambari

• HDFS

• YARN

• Zookeeper

• Hive

• Tez

Packages

The following packages must be pre-installed before installing Big Data SQL.

• JDK version 1.7 or later

• Python version 2.6.

  OpenSSL version 1.01 build 16 or later

System Tools

• curl

• rpm

• scp

• tar

• unzip

• wget

• yum

Environment Settings

The following environment settings are required prior to the installation.

• ntp enabled

• iptables disabled

• Ensure that /usr/java/default exists and is linked to the appropriate Java version. To link it to the latest Java version, perform the following as root :

  $ ln -s /usr/java/latest /usr/java/default
  

If Oracle Big Data SQL is Already Installed

If the Ambari Web GUI shows that the Big Data SQL service is already installed, make sure that all Big Data SQL Cell components are stopped before reinstalling. (Use the actions button, as with any other service.)

Services Running

The following services must be running at the time of the Oracle Big Data SQL installation

• Cloudera’s Distribution including Apache Hadoop (CDH)

• HDFS

• YARN

• Zookeeper

• Hive

Packages

The following packages must be pre-installed before installing Oracle Big Data SQL. The Oracle clients are available for download on the Oracle Technology Network.

• JDK version 1.7 or later

• Oracle Instant Client – 12.1.0.2 or higher, e.g. oracle-instantclient12.1-basic-12.1.0.2.0-1.x86_64.rpm

• Oracle Instant JDBC Client – 12.1.0.2 or higher, e.g. oracle-instantclient12.1-jdbc-12.1.0.2.0-

• PERL LibXML – 1.7.0 or higher, e.g. perl-XML-LibXML-1.70-5.el6.x86_64.rpm

• Apache log4j

System Tools

• unzip

• finger

• wget

Environment Settings

The following environment settings are required prior to the installation.

• Ensure that /usr/java/default exists and is linked to the appropriate Java version. To link it to the latest Java version, perform the following as root :

  $ ln -s /usr/java/latest /usr/java/default
  

• The path to the Java binaries must exist in /usr/java/latest.

• The default path to Hadoop libraries must be in /opt/cloudera/parcels/CDH/lib/.

If Oracle Big Data SQL is Already Installed

If the Configuration Manager shows that the Big Data SQL service is already installed, make sure that all Big Data SQL Cell components are stopped before reinstalling.

• Extract the files from BIGDATASQL product bundle saved from the download (either BigDataSQL-CDH-<version>.zip or BigDataSQL-HDP-<version>.zip) then configure and run the Oracle Big Data SQL installer found within the bundle. This installs Oracle Big Data SQL on the local server.

• Run the database bundle creation script. This script generates the database bundle file that you will run on the Oracle Database server in order to install Oracle Big Data SQL there.

• Check the parameters in the database bundle file and adjust as needed.

After you have checked and (if necessary) edited the database bundle file, copy it over to the Oracle Database server and run it as described in Installing on the Oracle Database Server

Install Big Data SQL on the Cluster Management Server

To install Big Data SQL on the cluster management server:

1. Copy the appropriate zip file (BigDataSQL-CDH-<version>.zip or BigDataSQL-HDP-<version>.zip) to a temporary location on the cluster management server.

2. Unzip file.

3. Change directories to either BigDataSQL-HDP-<version> or BigDataSQL-CDH-<version>, depending up on which platform you are working with.

4. Edit the configuration file.

   Table 2–4 below describes the use of each configuration parameter.

   • For CDH, edit bds-config.json , as in this example. Any unused port will work as the web server port.

     {
       "CLUSTER_NAME" : "cluster",
       "CSD_PATH" : "/opt/cloudera/csd",
       "DATABASE_IP" : "10.12.13.14/24",
       "REST_API_PORT" : "7180",  
       "WEB_SERVER_PORT" : "81",
     }
     

   • For HDP, edit bds-config.json as in this example:

     {
       "CLUSTER_NAME" : "clustername",
       "DATABASE_IP" : "10.10.10.10/24",
       "REST_API_PORT" : "8080",
     }
     

   DATABASE_IP must be the correct network interface address for the database node where you will perform the installation. You can confirm this by running /sbin/ip -o -f inet addr show on the database node.

5. Obtain the cluster administrator user ID and password and then as root run setup-bds. Pass it the configuration file name as an argument (bds-config.json ). The script will prompt for the administrator credentials and then install BDS on the management server.

   $ ./setup-bds bds-config.json  
   

If the Oracle Big Data SQL Service Immediately Fails

If Ambari or Configuration Manager reports an Oracle Big Data SQL service failure immediately after service startup, do the following.

1. Check the cell server (CELLSRV) log on the cluster management server for the following error at the time of failure:

   ossnet_create_box_handle: failed to parse ip : <IP Address>
   

2. If the IP address in the error message is less than nine characters in length, for example, 10.0.1.4/24, then on the cluster management server, find this address in /opt/oracle/bd_cell/cellsrv/deploy/config/cellinit.ora. Edit the string by padding one or more of the octets with leading zeros to make the total at least nine characters in length, as in:

   ipaddress1=10.0.1.004/24
   

3. Restart the Oracle Big Data SQL service.

The need for this workaround will be eliminated in a subsequent Oracle Big Data SQL release.

Command Line Switches for setup-bds.sh

The setup-bds.sh script has several optional switches. These are not overrides of the configuration in bds_config.json. They change the behavior of setup-bds.sh as described in the table below. In each case, the bds_config.json filename is passed in as an argument, as in ./setup-bds.sh <switch> bds_config.json.

Manually Adding Resources if Download Sites are not Accessible to the BDS Database Bundle Creation Script

If one or more of the default download sites is inaccessible from the cluster management server, there are two ways around this problem:

• Download the files from another server first and then provide bds-database-create-bundle.sh with the alternate path as an argument. For example:

  $ ./bds-database-create-bundle.sh --yarn-conf-ws='http://nodexample:1234/config/yarn'
  

• Because the script will first search locally in /bds-database-install for resources, you can download the files to another server, move the files into /bds-database-install on the cluster management server and then run the bundle creation script with no additional argument. For example:

  $ cp hadoop-xxxx.tar.gz bds-database-install/
  $ cp hive-xxxx.tar.gz bds-database-install/
  $ cp yarn-conf.zip bds-database-install/
  $ cp hive-conf.zip bds-database-install/
  $ cd db
  $ ./bds-database-create-bundle.sh
  

Copying the Database Bundle to the Oracle Database Server

Use scp to copy the database bundle you created to the Oracle Database server. In the example below, dbnode is the database server. The Linux account and target directory here are arbitrary. Use any account authorized to scp to the specified path.

$ scp bds-database-install.zip oracle@dbnode:/home/oracle

Prerequisites for Installing on an Oracle Database Server

The information in this section does not apply to the installation of Oracle Big Data SQL on an Oracle Exadata Database Machine connected Oracle Big Data Appliance.

Required Software

See the Oracle Big Data SQL Master Compatibility Matrix (Doc ID 2119369.1) in My Oracle Support for supported Linux distributions, Oracle Database release levels, and required patches.

Recommended Network Connections to the Hadoop Cluster

Oracle recommends Ethernet connections between Oracle Database and the Hadoop cluster of 10Gb/s Ethernet.

Extract and Run the Big Data SQL Installation Script

Perform the procedure in this section as the oracle user, except where sudo is indicated.

1. Locate the database bundle zip file that you copied over from the cluster management server.

2. Unzip the bundle into a temporary directory.

3. Change directories to bds-database-install, which was extracted from the zip file.

4. Run bds-database-install.sh. Note the optional parameters listed in Table 2-5

   If bds-database-install.sh finds and updates /etc/oracle/cell/network-config/cellinit.ora, then the installation is complete. If not, then the following prompt displays:

   Please run as root:  
   <temporary location>/bds-root-cluster-cellconfigdir.sh  
   Waiting for root script to complete. Press <Enter> to continue checking or press q<Enter> to quit.
   

   This prompt appears only if the network-config directory and/or cellinit.ora are not found at /etc/oracle/cell/network-config/cellinit.ora . The installation is temporarily suspended so that you can take the following corrective action. (You can press q and then Enter to cancel the installation if you do not want to continue at this time.)

5. Star another shell and run the secondary scriptbds-root-cluster-cellconfigdir.sh as root or via sudo.

   The script will create the complete path if needed. If cellinit.ora is missing, it will create the file and populate it with a temporary IP address that will allow the installation to continue.

6. When bds-root-cluster-cellconfigdir.sh has finished, return to the original shell and press Enter to resume the installation.

   The installation will enter the correct IP address for the database and other required parameters into cellinit.ora.

If You Need to Change the Configured Database_IP Address

The DATABASE_IP parameter in the bds-config.json file identifies the network interface of the database node. If you run bds-database-install.sh with no parameter passed in, it will search for that IP address (with that length, specifically) among the available network interfaces. You can pass the ––ip-cell parameter to bds-database-install.sh in order to override the configured DATABASE_IP setting:

$ ./bds-database-install.sh --ip-cell=10.20.30.40/24

Possible reasons for doing this are:

• bds-database-install.sh terminates with an error. The configured IP address (or length) may be wrong.

• There is an additional database node in the cluster and the defined DATABASE_IP address is not a network interface of the current node.

• The connection is to a multi-node database. In this case, perform the installation on each database node. On each node, use the ––ip-cell parameter to set the correct DATABASE_IP value.

/sbin/ip -o -f inet addr show

Uninstalling the Software from the Hadoop Cluster Management Server

• From the bds-database-install directory, run the following command as root.

  # ./setup-bds --uninstall bds-config.json
  

The script will return the following to standard output. Annotations and name alterations are included for the purposes of this example.

Big Data SQL  //including the version
Big Data SQL: Loading Configuration File
Big Data SQL: Configuration File Loaded Successfully
Big Data SQL: Beginning API setup, you will be asked for your Ambari admin user and password.
Big Data SQL: REST API port is 8080
Big Data SQL: Identifying protocol for connection..
Big Data SQL: REST API version is v1

Ambari Admin User:   //or Configuration Manager admin user 
Password:

Big Data SQL: API setup finished successfully.
Big Data SQL: Cluster myclusterexample verified.
Big Data SQL: Big Data SQL service was detected. Beginning uninstall
Big Data SQL: Stopping Big Data SQL service in order to begin uninstall.
Big Data SQL: Executing Asynchronous Command....
Big Data SQL: Asynchronous Command Completed!
Big Data SQL: Big Data SQL service Stopped!
Big Data SQL: Cell nodes: myclusterexample-adm.myregion.mydomain.com,mybdanode08-adm.myregion.mydomain.com,mybdanode09-adm.myreqion.mydomain.com
Big Data SQL: Executing Asynchronous Command...
Big Data SQL: Asynchronous Command Completed!
Big Data SQL: Deleted previous Big Data SQL service.
Big Data SQL: Beginning Cleanup of the Ambari Server Node.
Big Data SQL: Stack root directory found: /var/lib/ambari-server/resources/stacks/HDP/2.4/services
Big Data SQL: Removing Big Data SQL Stack directory
Big Data SQL: Removing Big Data SQL Log directory
Big Data SQL: Cleaning up installation...
Big Data SQL: Finished!

Uninstalling the Software from an Oracle Database Server

• On any database server where you want to uninstall Oracle Big Data SQL, run the appropriate command below as the database owner (usually the oracle user).

  # ./bds-database-install.sh --uninstall-as-secondary
  

  or

  # ./bds-database-install.sh --uninstall-as-primary
  

If you use the --uninstall-as-secondary switch to uninstall the software from the primary node, cleanup of database objects will be incomplete. This can be remedied by running the uninstall again. Error messages may appear if your run a second uninstall for cleanup purposes, but the cleanup should complete successfully.

The following example show the output of bds-database-install.sh --uninstall-as-primary. The output for --uninstall-as-secondary is similar. In this case, the command is run on a CDH cluster, but the differences in the output on an HDP cluster are minor.

oracle@mynode42bda06$ ./bds-database-install.sh --uninstall-as-primary
bds-database-install: platform is               : Linux
bds-database-install: setup script started at   : Wed May 25 11:49:07 PDT 2016
bds-database-install: cluster type              : cdh
bds-database-install: cluster name              : myclusterexample
bds-database-install: hive version              : hive-1.1.0-cdh5.7.0
bds-database-install: hadoop version            : hadoop-2.6.0-cdh5.7.0
bds-database-install: bds version               : Big Data SQL 3.0.1
bds-database-install: bds install date          : Fri May 13 10:45:59 PDT 2016
bds-database-install: bd_cell version           : bd_cell-12.1.2.0.100_LINUX.X64_151208.1100-1.x86_64
bd_cell-12.1.2.0.100_LINUX.X64_160511.1100-1.x86_64
bds-database-install: cell config dir           : /etc/oracle/cell/network-config
bds-database-install: configured cell network   : 10.101.4.13/20
bds-database-install: allow multiple subnets    : _skgxp_ant_options=1
bds-database-install: use UDP protocol          : _skgxp_dynamic_protocol=2
bds-database-install: cellaffinity.ora file     : missing
bds-database-install: configured DB network     : 10.245.129.72/21
bds-database-install: action                    : uninstall
bds-database-install: crs                       : true
bds-database-install: db resource               : orcl
bds-database-install: database type             : SINGLE
bds-database-install: cardinality               : 1
bds-database-uninstall: removing: oracle-hadoop-sql.jar ora-hadoop-common.jar oraloader.jar kvclient.jar orahivedp.jar
bds-database-uninstall: removing: client jars hadoop-2.6.0-cdh5.7.0
bds-database-uninstall: removing: client jars hive-1.1.0-cdh5.7.0
bds-database-uninstall: mta setting agent home as : /u03/app/oracle/product/12.1.0/dbhome_1/hs/admin
bds-database-uninstall: stopping crs resource     : bds_orcl_myclusterexample
CRS-2673: Attempting to stop 'bds_orcl_myclusterexample' on 'mynode42bda06'
CRS-2677: Stop of 'bds_orcl_myclusterexample' on 'mynode42bda06' succeeded
bds-database-uninstall: deleting crs resource     : bds_orcl_myclusterexample
bds-database-uninstall: removing /u03/app/oracle/product/12.1.0/dbhome_1/hs/admin/initbds_orcl_myclusterexample.ora
bds-database-uninstall: dropping mta related db links
catcon: ALL catcon-related output will be written to /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon_catcon_5$51.lst
catcon: See /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon*.log files for output generated by scripts
catcon: See /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon_*.lst files for spool files, if any
catcon.pl: completed successfully
catcon: ALL catcon-related output will be written to /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon_catcon_5$01.lst
catcon: See /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon*.log files for output generated by scripts
catcon: See /u03/app/oracle/product/12.1.0/dbhome_1/install/bdscatcon_*.lst files for spool files, if any
catcon.pl: completed successfully
bds-database-uninstall: uninstalled               : myclusterexample