3 Installing and Configuring the Oracle Database

This chapter describes the process of installing the Oracle database and configuring the Oracle Database for Oracle Communications Network Integrity.

Oracle Database Installation

Network Integrity must be installed in an Oracle Database tablespace. See Table 2-2, "Required Server-Side Software" for database requirements.

For information on installing Oracle Database, see the Oracle Database installation documentation.

Note:

Configure the Oracle Database with the XDB component.

Oracle Database Configuration

The Oracle database must be configured for Network Integrity. Specifically, this section covers the following:

Creating a Tablespace for Network Integrity

Create a Network Integrity specific tablespace according to the Oracle Database documentation. See Table 2-10, "Network Integrity Hardware Planning Guideline" for tablespace sizing guidelines.

Setting the Database Time Zone

Oracle Database must have the correct time zone setting, because Network Integrity uses the datatype TIMESTAMP WITH LOCAL TIME ZONE in its database schema.

See Oracle Database Globalization Support Guide for information and instructions on setting the time zone.

Note:

After Network Integrity has been installed, the database time zone cannot be changed. Ensure the time zone is correctly set before installing Network Integrity.

Creating the Database (MetaData) Schema for Network Integrity

The MetaData schema is an Oracle Fusion Middleware component that is required by Network Integrity. You create the schema using the Repository Creation Utility (RCU).

Note:

A new schema must be created for all new Network Integrity installations. Upgrade installations will use the schema created during the installation of that Network Integrity instance.

The Repository Creation Utility can run on the Linux (32 bit) and Microsoft Windows platforms. A Linux or Windows system can be used to remotely access and configure the database.

To create the schema for Network Integrity using RCU:

  1. Export the environment variables by running one of the following commands:

    export JAVA_HOME=$JDK_HOME 
    

    or

    export ORACLE_HOME=$mw_home
    
  2. Run the following command:

    ./MW_Home/oracle_common/bin/rcu
    

    where MW_Home is the installation directory of Oracle Fusion Middleware.

    The Welcome screen of the Repository Creation Utility appears.

  3. Click Next.

    The Create Repository screen appears.

  4. Select Create Repository and click Next.

    The Database Connection Details screen appears.

  5. Do the following:

    1. From the Database Type list, select Oracle Database.

    2. In the Host Name field, enter the database system host name or IP address.

    3. In the Port field, enter the port number for the system hosting the database.

    4. In the Service Name field, enter the service name.

    5. In the Username field, enter the user name for the database user.

      Note:

      This user account must have the following privileges: CATALOG, CONNECT, Create User, Create Session, Grant Any Privilege, Grant Any Role, Select Any Table, Select any Dictionary.

      Caution:

      You must use the same user name and password when providing database user information during Network Integrity installation.
    6. In the Password field, enter the password for the database user.

    7. From the Role list, select SYSDBA.

    8. Click Next.

      The Checking Global Prerequisites screen appears, displaying the progress of establishing the connection with the specified database.

    9. Click OK.

    The Select Components screen appears.

  6. On the Select Components screen, do the following:

    1. Select Create new Prefix and enter the prefix value.

      The prefix is any appropriate name for your schema. RCU adds a suffix to this name.

    2. Expand Oracle AS Repository Components.

    3. Expand AS Common Schemas and select Metadata Services, Audit Services, Audit Services Append, Audit Services Viewer, and Oracle Platform Security Services.

      Note:

      The Service Table (prefix_STB & prefix_WLS) schema is a default selection and you cannot change this selection.

      where:

      prefix is the prefix that you define in step 6a.

    4. Click Next.

      The Checking Component Prerequisites screen appears, displaying the progress of the component prerequisites check before the schemas are created.

    5. Click OK.

    The Schema Passwords screen appears.

  7. Select Use same passwords for all schemas.

  8. In the Password field, enter the password for the schema.

  9. In the Confirm Password field, enter the password for the schema again and click Next.

    The Map Tablespaces screen appears.

  10. Review the entries on the Map Tablespaces screen and click Next.

    The Summary screen appears.

  11. Review and verify the information you have provided and click Create.

    The Completion Summary screen appears, displaying details of the newly created repository.

  12. Click Close.

Installing and Configuring Database Real Application Clusters

Oracle recommends Oracle Real Application Clusters (RAC) for high availability and scalability if your network data requires multiple databases for storage purposes. Refer to the Oracle Real Application Clusters documentation on the Oracle Help Center.

Tuning the Database

Table 3-1 and Table 3-2 provide the recommended database parameters for tuning your database for the Network Integrity installation. These are the minimum requirements for Network Integrity.

Table 3-1 Database Creation Parameters

Parameter Recommended Value

SGA+PGA

At least 4 GB in total.

Oracle recommends that you use as much memory as you have available in the system, and also use Automatic Memory Management.

Processes

2000

Connection mode

Dedicated server

Redo log file size

1024 MB


Table 3-2 Database Initialization Parameters

Parameter Recommended Value

db_file_multiblock_read_count

16

distributed_lock_timeout

7200

dml_locks

9700

job_queue_processes

10

log_buffer

31457280

open_cursors

5000

parallel_max_servers

640

plsql_code_type

NATIVE