Oracle Prerequisites¶
Table of Contents
Introduction¶
This document includes the prerequisite steps for Oracle.
Operating System User¶
Gluent Data Platform must be installed as the same user that owns the Oracle Database software (assumed to be oracle for the remainder of this document).
Storage Requirements¶
A filesystem location must be created for Gluent Data Platform installation.
Gluent Data Platform occupies approximately 1GB of storage once unpacked.
During operation, Gluent Data Platform will write log and trace files within its installation directory. Sufficient space will need to be allocated for continuing operations.
The filesystem location must be owned by the same user that owns the Oracle Database software.
For Oracle Real Application Clusters environments install Gluent Data Platform into the same path on all Oracle Database servers.
Default Shell¶
The owner of the Gluent Data Platform software requires the Bash shell. The outcome of the following should be bash for that user:
$ echo $SHELL
Database Characterset¶
The database characterset should be noted as this will be needed during installation. This can be verified with:
SQL> SELECT value FROM nls_database_parameters WHERE parameter = 'NLS_CHARACTERSET';
Database Access¶
Access as the SYS database user is required during the following installation actions:
Tablespace¶
An object created during the Install Oracle Database Components install action utilizes SECUREFILE lobs. These must be stored in an Automatic Segment Space Management (ASSM) tablespace. Identify an ASSM tablespace to be used during this installation action.
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.
Easy Connect Naming Permitted¶
Gluent Data Platform connects to the Oracle Listener using the Easy Connect Naming method (EZCONNECT). Verify this method works (as oracle):
$ tnsping <db_host|vip>:<port>/<service>
Metadata Daemon OS User¶
In environments where there is a mismatch between the primary operating system group of the Oracle Database user process, and the operating system group of the Oracle Database binary, it is necessary to run the Metadata Daemon process as the root user.
The primary operating system group of the Oracle Database user process can be confirmed with (as oracle):
$ id oracle
The operating system group of the Oracle Database binary can be confirmed with (as oracle):
$ ls -l $ORACLE_HOME/bin/oracle
This information will be needed when configuring Metadata Daemon during installation.
Kerberos¶
If Kerberos is required to authenticate with a backend or for password-less SSH, verify the existence of the krb5-workstation RPM (as root):
# rpm -q krb5-workstation
If Kerberos is required to authenticate with a backend, additionally verify the existence of the cyrus-sasl-gssapi RPM (as root):
# rpm -q cyrus-sasl-gssapi
The following requirements must also be met:
A Kerberos principal must be created in the correct Kerberos realm
A Kerberos keytab file must be created for this principal. The keytab file must be accessible by the Gluent Data Platform software owner on the Oracle Database server(s)
The Oracle Database server(s) must be part of the Kerberos realm and be able to communicate with the Kerberos Domain Controller
Verify that a Kerberos ticket can be obtained for the principal and keytab created (as oracle):
$ kinit -kt <path_to_keytab_file> <principal_name>
$ klist