Novell Doc: Sentinel 6.1 Installation Guide - Configuring the Oracle RAC Database

C.1 Configuring the Oracle RAC Database

C.1.1 Creating the RAC Database

Perform the following steps to create an empty Oracle RAC database by using the Oracle Database Configuration Assistant (DBCA) utility for installing the Sentinel components.

Run the DBCA utility.
Select the Oracle Real Application Clusters database under Database Configuration Assistant. Click Next.
Select Create a database, then click Next.
To select all the nodes to create a cluster database, click Select All, then click Next.
From the list of templates, select a template. By default, General Purpose is selected. Click Next.
Specify the database name and SID (Oracle System Identifier), then click Next.
Make sure the Configure the Database with Enterprise Manager option is selected, then click Next.
You can use the same passwords for all user accounts or you can use different passwords. Select your option and specify the passwords, then click Next.
From the three storage mechanisms offered by the system (Cluster File System, Automatic > Storage Management, and Raw Devices), select your option. If you chose Raw Devices, specify the path to the Raw Devices mapping file. Click Next.
Specify a directory to store the database files on the storage system, then click Finish.
Retain the default selection in the Recovery options and Sample Schemas windows, then click Next.

You can create a Database Service or you can create the service later by using DBCA.
In the Database storage window, retain the default selection, then click Next.
From the Database creation options, select Create Database, then click Finish.

C.1.2 Creating the Sentinel Tablespaces

IMPORTANT:The Sentinel installation will be successful only if all the tablespaces mentioned in Table C-1 are created. You can use Oracle Enterprise Manager or an SQL query to verify the existence of these tablespaces.

Table C-1 Minimum Recommended Tablespace Size

Tablespace	Minimum Recommended Size with Autoextend Enabled	Comments
REDO	3 x 100MB	You should create larger redo logs if the event rate is high. A minimum of three redo log groups is required.
SYSTEM	500MB	Stores information about internal tables and indexes of the database.
TEMP	1GB	Used for temporary operations like sorting and storing temporary information of a session.
UNDO	1GB	Stores the information required for rollback and undo operations.
ESENTD	5GB	Stores the event data.
ESENTD2	500MB	Stores information about configuration, assets, vulnerability, and associations.
ESENTWFD	250MB	Stores information about iTRAC data
ESENTWFX	250MB	Stores information about iTRAC indexes
ESENTX	3GB	Stores information about event indexes
ESENTX2	500MB	Stores information about indexes for configuration, assets, vulnerability, and associations.
SENT_ADVISORD	15GB	Stores information about the Advisor data
SENT_ADVISORX	15GB	Stores information about the Advisor indexes
SENT_AUDITD	250MB	Stores information about the Sentinel audit data
SENT_AUDITX	250MB	Stores information about the Sentinel audit indexes
SENT_LOBS	100MB	Stores information about the database large objects This is the minimum value in a basic installation.
SENT_LOBS	2GB	This is the minimum value if the Sentinel installation is integrated with the identity management system enabled.
SENT_SMRYD	3GB	Stores the summary data for aggregation
SENT_SMRYX	2GB	Stores the summary indexes for aggregation
SYSAUX	100MB	Stores information about internal tables and indexes of the database for performance and other statistics. This tablespace is for Oracle 10g/11g (not Sentinel specific).

C.1.3 Creating the Sentinel Database User

The username for the Sentinel schema owner is esecdba. Most of the objects that are created by the Sentinel installer are owned by this user.

Locate the Sentinel createEsecdba.sh script on the Sentinel installation disk at disk1/sentinel/dbsetup/bin.
Run this script from any machine with the Oracle client installed.

You must set the ORACLE_SID value to the instance value of a particular node on which you are running the script. For example, in a two-node cluster, you can set ORACLE_SID = ESEC1. You might also need to edit the script to properly set the Oracle environment variables and the CONNECT AS string (by default, the script connects as sysdba).