Oracle Installation

Introduction

This document includes the installation steps for Oracle.

This document assumes that the owner of the Oracle Database software is oracle.

Unpack Software

Perform the following actions as oracle.

Unpack the install tarball (gluent_offload_<version>.tar.bz2):

Note

When unpacking, an offload directory will be created if it does not exist. The offload directory is referred to as <OFFLOAD_HOME> and an environment variable ($OFFLOAD_HOME) will be set when offload.env is sourced.

$ cd <Gluent Data Platform Base Directory>
$ tar xpf <Gluent Data Platform Installation Media Directory>/gluent_offload_<version>.tar.bz2

Install Oracle Database Components

As part of the Gluent Data Platform database component installation, three Oracle Database users are created (default: GLUENT_ADM, GLUENT_APP and GLUENT_REPO). The installation procedure prompts for the profile for these Oracle Database users, a default tablespace and tablespace quota for Gluent Metadata Repository.

Move to the setup directory (as oracle):

$ cd $OFFLOAD_HOME/setup

Connect to your database as an appropriately privileged account and run install_offload.sql as shown below.

Note

  1. Grants as SYS are required, however, the installation can be run as a DBA user and you will be prompted to run the required grants as SYS in another session

  2. The tablespace to use for the GLUENT_REPO user must be an Automatic Segment Space Management tablespace

SQL> @install_offload.sql

You will be prompted as below (default values shown in square brackets):

Gluent database user prefix [GLUENT]:
Profile for Gluent database users [DEFAULT]:
Base directory path for OFFLOAD_BIN/OFFLOAD_LOG database directories [/u01/app/gluent/offload]:
Full directory path for OFFLOAD_DATA database directory [/u01/app/gluent/offload/data]:
Existing tablespace to use for GLUENT_REPO user [USERS]:
Tablespace quota to assign to GLUENT_REPO (format <integer>[K|M|G]) [100M]:

Warning

The default profile of DEFAULT is inappropriate for production installations unless it has been modified from the Oracle supplied configuration.

Ensure a profile that satisfies your security requirements is specified.

See also

See Security for details of the privileges granted to the Oracle Database users created.

Set Passwords for Gluent Oracle Database Users

The installation procedure creates GLUENT_ADM, GLUENT_APP and GLUENT_REPO users in Oracle with 30 character random passwords as a security precaution. These passwords should be changed to values known to the administrator.

Access to UTL_FILE

Gluent Data Platform’s database administration owner schema requires EXECUTE privilege on the UTL_FILE package.

A default Oracle Database installation will grant this privilege publicly. However, if this grant has been revoked it will need to be granted to the Gluent Data Platform’s database administration owner schema after the Install Oracle Database Components action.

Create Oracle Hybrid Schema(s)

Each application owner schema that contains tables to be offloaded by Gluent Offload Engine or requires access to remote tables presented by Gluent Offload Engine will require an associated hybrid schema. A hybrid schema is created as follows.

Move to the setup directory (as oracle):

$ cd $OFFLOAD_HOME/setup

Connect to your database as SYS and run prepare_hybrid_schema.sql with the name of the application owner schema that requires the corresponding hybrid schema as shown below. Optionally provide a tablespace name and tablespace quota. If you intend to enable the Incremental Update feature this tablespace will be used to store the required objects. In the absence of user-provided values, the default will be the default permanent tablespace of the hybrid schema with a quota of 1G.

SQL> @prepare_hybrid_schema.sql schema=APPLICATION_OWNER_SCHEMA_NAME [tablespace=TABLESPACE_NAME quota=TABLESPACE_QUOTA]

Note

Repeat these instructions to create each hybrid schema that is required.

Note

The maximum supported length for APPLICATION_OWNER_SCHEMA_NAME is 28 characters for Oracle Database versions <= 12.1 and 126 characters for Oracle Database versions >= 12.2.

Note

The prepare_hybrid_schema.sql script grants the GLUENT_OFFLOAD_ROLE role to the application owner schema, allowing it to query objects in the hybrid schema(s). Schemas other than the application owner schema who wish to query objects in the hybrid schema(s) must be granted this role manually.

Installation on Additional Oracle RAC Nodes

Perform the following actions on each additional Oracle RAC node as oracle.

Unpack the install tarball (gluent_offload_<version>.tar.bz2):

Note

When unpacking, an offload directory will be created if it does not exist. The offload directory is referred to as <OFFLOAD_HOME> and an environment variable ($OFFLOAD_HOME) will be set when offload.env is sourced.

$ cd <Gluent Data Platform Base Directory>
$ tar xpf <Gluent Data Platform Installation Media Directory>/gluent_offload_<version>.tar.bz2

Documentation Feedback

Send feedback on this documentation to: feedback@gluent.com