Post-Installation Tasks

4.1 Validating the Installation With bdschecksw and Other Tests

The script bdschecksw.sh runs automatically as part of the installation, but you can also run it at any time.

This script gathers and analyzes diagnostic information about the Oracle Big Data SQL installation from both the Oracle Database and the Hadoop cluster sides of the installation. You can also run this script as a troubleshooting check at any time after the installation. The script is in $ORACLE_HOME/bin on the Oracle Database server.

$ bdschecksw --help

See Running Diagnostics With bdachecksw in the Oracle Big Data SQL User’s Guide for a complete description.
Also see How to do a Quick Test in the user’s guide for some additional functionality tests.

4.2 Checking the Installation Log Files

You can examine these log files after the installation.

On the Hadoop cluster side:

/var/log/bigdatasql 
/var/log/oracle

On the Oracle Database side:

$ORACLE_HOME/install/bds* (This is a set of files, not a directory) 
$ORACLE_HOME/bigdatasql/logs
/var/log/bigdatasql

Tip:

If you make a support request, create a zip archive that includes all of these logs and include it in your email to Oracle Support.

4.3 Installing and Configuring Oracle SQL Access to Kafka (OSAK)

You have the option to install and configure OSAK after completing the Hadoop and Oracle Database sides of the Big Data SQL installation.

After performing the Big Data SQL installation, see Installing and Configuring Oracle SQL Access to Kafka

4.4 Perform Network ACL Setup for Object Store Access

This topic applies to Oracle Database 18c and 19c environments only.

Run these scripts generated by the Oracle Big Data SQL installer (bds-database-install.sh) to enable access to object stores.

Notice the following messages in the bds-database-install.sh output:

bds-database-setup: Object Store scripts templates have been created
bds-database-setup: set_parameters_cdb.sql     should be executed in CDB$ROOT
bds-database-setup: allow_proxy_pdb.sql        should be executed on required PDBs

You can find these scripts in the installer staging directory (for example: $ORACLE_HOME/BDSJaguar-4.1.2/cdh510-6-node1.<cluster name>.<domain name>.com).

If you intend to support connects to object stores from Oracle Database 18c or 19c, run the corresponding script on the CDB and the other on PDBs. For example, on the CDB:

# @set_parameters_cdb.sql

Run these scripts after you perform the installation for each connection to a Hadoop cluster. If you reconfigure the database-side installation (./bds-database-install --reconfigure), the reconfigure operation prompts you to run the scripts again:

bds-database-reconfigure: Object Store scripts templates have been created
bds-database-reconfigure: set_parameters_cdb.sql     should be executed in CDB$ROOT
bds-database-reconfigure: allow_proxy_pdb.sql        should be executed on required PDBs

You can edit and the re-run the scripts to customize them for different roles and URLs.

4.5 Run bds_cluster_node_helper.sh to Get Information About the Oracle Big Data SQL Installation on a Node

The script bds_cluster_node_helper.sh aggregates information about a Hadoop cluster node that is useful for Oracle Big Data SQL maintenance purposes.

This script provides options to do the following:

Show Oracle Big Data SQL status information via bdscli, the Oracle Big Data SQL command line interface.
Collect and archive log data that is pertinent to Oracle Big Data SQL operations. There are three levels to the scope of the data collection.
Set some parameters that control the level of debug information in logs that are collected.

You can find this script at <Oracle Big Data SQL installation directory>/BDSJaguar. It must be run as root.

Usage

# bds_cluster_node_helper.sh [OPTIONS]

Table 4-1 Parameters for bds_cluster_node_helper.sh

Parameter	Description
`-h, --help`	Show usage information.
`-v, --version`	Show the Oracle Big Data Appliance release version.
`--skip-bdscli-info`	Skip bdscli information gathering. Default: `false`. Runs the following bdscli commands and returns the output: `bdscli -e "list bdsql" bdscli -e "list bdsql detail" bdscli -e "list offloadgroup" bdscli -e "list offloadgroup detail" bdscli -e "list quarantine"`
`--get-logs [--log-level=<1\|2\|3>] [--bundle-name=<name>] [--wrap, --envelop]`	Generates a gzipped tar file of logs. Default: `false`. Options: `--log-level=<supported value>` Specifies the log level. `--bundle-name=<name>` Names the `.tar.gz` created. `--wrap, --envelop` Prepares the bundle to be sent over email. Note: See the table below for more detail on each `-get-logs` sub-option.
`--set-debug=<on\|off>`	`--set-debug=<supported value>` Set or remove the `_cell_server_event` parameter from the `celllinit.ora` file. `--set-debug=on` In the files `/opt/oracle/bigdatasql/bdcell-12.1/bigdata-log4j.properties` and `/opt/oracle/bigdatasql/bdcell-12.2/bigdata-log4j.properties`, this sets the parameter value `log4j.logger.oracle.hadoop.sql=ALL`.In cellinit.ora, sets `_cell_server_event` as follows: `_cell_server_event="trace[CELLSRV_Disk_Layer] disk=highest, memory=highest"` `--set-debug=off` In the file `/opt/oracle/cell/cellsrv/deploy/config/cellinit.ora`, this setting remove the parameter whose prefix is `_cell_server_event="trace[CELLSRV_Disk_Layer]` In `bigdata-log4j.properties`, sets `log4j.logger.oracle.hadoop.sql=OFF`.

The table below provides full details on bds_cluster_node_helper.sh --get-logs sub-options.

Table 4-2 Sub-Parameters for --get-logs Option of bds_cluster_node_helper.sh

bds_cluster_node_helper.sh --get-logs sub-options Description

bds_cluster_node_helper.sh --get-logs sub-options	Description
`--get-logs --log-level=<1\|2\|3>`	Specifies the log level. Default: `1`. The scope of the recovery for each log level is as follows: `--get-logs`, or `--get-logs --log-level=1`: `/var/log/bigdatasql /opt/oracle/cell/.install_log.txt` `--get-logs --log-level=2`: Includes level 1 logging, plus: `/var/log/oracle /opt/oracle/cell/cellsrv/deploy/msdomain/servers/msServer/logs` `--get-logs --log-level=3` Includes level 1 and 2 logging, plus: `/var/run/cloudera-scm-agent/process (on Cloudera clusters) /var/lib/ambari-agent/data (on Hortonworks HDP clusters)` Example: `# bds_cluster_node_helper.sh --get-logs --log-level=2`
`--get-logs --bundle-name=<name>`	Give a name to the created `tar.gz` bundle. Default: `bds-<Oracle Big Data SQL version>-<YYYY-mm-dd-HH-MM-SS>`. For example, `bds_4.1.2_2020-05-01_23-55-03.tar.gz` The customer can use this option to specify a different name. For example: `# bds_cluster_node_helper.sh --get-logs --bundle-name=logs_from_node1.tar.gz`
`--get-logs [--wrap \| --envelop]`	Prepares the bundle for email transmission. Default: `false`. Examples: `# bds_cluster_node_helper.sh --get-logs --wrap # bds_cluster_node_helper.sh --get-logs --envelop` These sub-options are equivalent.

--get-logs --log-level=<1|2|3>

Specifies the log level.

Default: 1.

The scope of the recovery for each log level is as follows:

--get-logs, or --get-logs --log-level=1:

/var/log/bigdatasql
/opt/oracle/cell/.install_log.txt

--get-logs --log-level=2:
Includes level 1 logging, plus:
```
/var/log/oracle
/opt/oracle/cell/cellsrv/deploy/msdomain/servers/msServer/logs
```

--get-logs --log-level=3

Includes level 1 and 2 logging, plus:


/var/run/cloudera-scm-agent/process (on Cloudera clusters)
/var/lib/ambari-agent/data (on Hortonworks HDP clusters)

Example: # bds_cluster_node_helper.sh --get-logs --log-level=2

--get-logs --bundle-name=<name>

Give a name to the created tar.gz bundle.

Default: bds-<Oracle Big Data SQL version>-<YYYY-mm-dd-HH-MM-SS>. For example, bds_4.1.2_2020-05-01_23-55-03.tar.gz

The customer can use this option to specify a different name. For example:

# bds_cluster_node_helper.sh --get-logs --bundle-name=logs_from_node1.tar.gz

--get-logs [--wrap | --envelop]

Prepares the bundle for email transmission.

Default: false.

Examples:

# bds_cluster_node_helper.sh --get-logs --wrap
# bds_cluster_node_helper.sh --get-logs --envelop

These sub-options are equivalent.

4.6 Other Post-Installation Steps to Consider

Some additional steps that are recommended after installation are:

Read about measures you can take to secure the installation. (See Securing the Oracle Big Data SQL Installation.)
Learn how to modify the Oracle Big Data SQL configuration when changes occur on the Hadoop cluster and in the Oracle Database installation. (See Expanding or Shrinking an Installation.)
If you have used Copy to Hadoop in earlier Oracle Big Data SQL releases, learn how Oracle Shell for Hadoop Loaders can simplify Copy to Hadoop tasks. (See Additional Tools Installed.)