Install > Installation > Install and configure database > Install Oracle Database and JDBC Drivers
Install Oracle Database and JDBC Drivers

Install Oracle Database and JDBC Drivers

Installing the Oracle database for CSA involves the following steps:

  1. Install the Oracle Database
  2. Download the Oracle JDBC Drivers
  3. Configure Oracle

Install the Oracle Database (Required)

For a list of supported database versions, see the Cloud Service Automation System and Software Support Matrix.

Guides are available on the HPE Software Support web site at: https://softwaresupport.hpe.com (this site requires a Passport ID). Select Dashboards > Manuals.

Install the database according to the manufacturer’s documentation. Database installation is typically done in partnership with a database administrator.

Configure multi-language support (Optional)

To support characters of any language worldwide, use Unicode (AL32UTF8) as Database Character Set (set property NLS_CHARACTERSET = AL32UTF8).

Set the property NLS_LENGTH_SEMANTICS = CHAR;

Work with your database administrator to set the parameter (or see the manufacturer’s documentation for more information).

Note: Once the database is created, national language support cannot easily be changed.

Download Oracle JDBC Drivers (Required)

For a list of supported JDBC driver versions, see the Cloud Service Automation System and Software Support Matrix.

Download a supported version of the JDBC.jar file or files and save them on the system on which CSA will be installed. Note the location where you save the file or files as you must provide this information when installing CSA.

Configure Oracle

Note: These tasks must be completed before installing CSA.

Separate database users are required for CSA and its components. You must create a separate database user for:

  • Identity Management component
  • CSA
  • Embedded Operations Orchestration (Optional)
Note: If you want to use external Operations Orchestration, no additional schema is needed.

Create Database Users for CSA

Work with the database administrator to create a database that is used by the embedded Operations Orchestration, CSA (if it has not already been created), and the Identity Management component. See the Operations Orchestration Database Guide for more information about database requirements for Operations Orchestration.

Caution: The database name and username cannot contain more than one dollar sign symbol ($). For example, c$adb is a valid name but c$$adb and c$ad$b are not valid names.

To create database users for CSA, follow these steps:

  1. Create a user for CSA (for example, csadbuser) with permissions to create sessions, tables, views, sequences and to store data to the default tablespace. (Replace the <csadbuser_password> token with your desired user password.)

    create user csadbuser

    identified by "<csadbuser_password>";

    grant CREATE SESSION, CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, UNLIMITED TABLESPACE to csadbuser;

    grant CREATE ANY SYNONYM to csadbuser ; -- optional - this step is needed only if you would like to use the reporting user (below).

    Provide this username and password when prompted for the CSA database information during the installation of CSA.

  1. (Optional) Create a read-only reporting user (for example, CSAReportingDBUser). The user is needed only if you want to use the reporting capabilities of CSA.(Replace the <CSAReportingDBUser_password> token with your desired user password.).

    create user CSAReportingDBUser

    identified by "<CSAReportingDBUser_password>";

    grant CREATE SESSION to CSAReportingDBUser_password;

    Provide this username and password when prompted for the CSA reporting user information during the installation of CSA.

  1. Create a user for the Identity Management component (for example, csaidmdbuser) with permissions to create sessions, tables and to store data to the default tablespace. (Replace the <csaidmdbuser_password> token with your desired user password.)

    create user csaidmdbuser

    identified by "<csaidmdbuser_password>";

    grant CREATE SESSION, CREATE TABLE, UNLIMITED TABLESPACE to csaidmdbuser;

    Provide this username and password when prompted for the Identity Management component database information during the installation of CSA.

  1. Create a user for the embedded Operations Orchestration (Optional - needed only if you want to install the embedded OO). For example, csaoodbuser with permissions to create sessions, tables, sequences and to store data to the default tablespace. (Replace the <csaoodbuser_password> token with your desired user password.)

    create user csaoodbuser

    identified by "<csaoodbuser_password>";

    grant CREATE SESSION, CREATE TABLE, CREATE SEQUENCE, UNLIMITED TABLESPACE to csaoodbuser;
     

    Provide this username and password when prompted for the Operations Orchestration database information during the installation or upgrade of CSA.

  2. Create a user for the Workflow Designer component (for example, csaooddbuser) ) with permissions to create sessions, tables and to store data to the default tablespace. (Replace the <csaooddbuser_password> token with your desired user password.)

    create user csaooddbuser

    identified by "<csaooddbuser_password>";

    grant CREATE SESSION, CREATE TABLE, UNLIMITED TABLESPACE to csaooddbuser;

    Provide this username and password when prompted for the Workflow Designer component database information during the installation of CSA.

    NOTE: If you are using Oracle 11g R2 or 11g R2 RAC, it is recommended to apply patch 20299013 before installing Operations Orchestration.

Create a Tablespace for LOBs (Recommended)

For performance reasons, HPE recommends that you create a new tablespace which stores LOBs for the CSA_DOCUMENT table. These tasks can be completed after CSA is installed. Create a new tablespace (for example, csadbuserlob). Work with your database administrator (or see the manufacturer’s documentation for more information). HPE recommends that the initial tablespace size should be at least 3 GB.

CREATE TABLESPACE csadbuserlob
DATAFILE 'csadbuserlob.dbf'
SIZE 3G AUTOEXTEND ON;

Modify the CSA_DOCUMENT table such that LOB segments are stored in the tablespace. For example:

ALTER TABLE csa_document
MOVE LOB(content)
STORE AS (TABLESPACE csadbuserlob);

Send Help Center feedback