Skip Headers
Oracle® Communications Data Model Installation Guide
11g Release 2 (11.2)

Part Number E15887-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Installation of Oracle Communications Data Model

This chapter describes how to install Oracle Communications Data Model:

Pre-installation Tasks

Before you install the Oracle Communications Data Model, perform the following tasks:

Ensuring that Required Software is Installed

As discussed in "Software Requirements", you must have certain software installed before you can successfully install the Oracle Communications Data Model component or the Oracle Communications Data Model sample data and reports.

Take the following steps to ensure that for each type of installation, the required software is installed:

Confirming that Oracle Data Mining and OLAP Options are Installed

To check that the Oracle Data Mining and OLAP options are installed, log in as SYS and enter the following SQL queries:

SELECT * FROM V$OPTION WHERE PARAMETER ='Data Mining';
SELECT VALUE FROM V$OPTION WHERE PARAMETER ='OLAP';

If these queries return TRUE, the options are installed.

Confirming that the OWBSYS Schema Exists

To check that OWBSYS schema exists, log in to the Database as DBA and issue the following statements:

SELECT COUNT(*) FROM DBA_USERS WHERE USERNAME='OWBSYS';

If this query returns a value larger than zero (0), OWBSYS schema exists.

If the OWBSYS schema does not exist, take the following steps:

  1. Go to the $ORACLE_HOME/owb/UnifiedRepos directory.

  2. Login to the Database as SYSDBA.

  3. Execute the following SQL statement.

    @cat_owb.sql
    
  4. When prompted to enter a tablespace name, input USERS

Confirming that Oracle Business Intelligence Suite Enterprise Edition is Installed

To test that Oracle Business Intelligence Suite Enterprise Edition is installed, open the following link in a browser. (Note that the 9704 value in the link is the value of the default Oracle Business Intelligence Suite Enterprise Edition port; if you specified a different port when you installed Oracle Business Intelligence Suite Enterprise Edition, use the value for that port.)

http://hostname:9704/analytics

The sample Oracle Business Intelligence Suite Enterprise Edition login window is displayed.

Use Administrator for both the user name (ID) and the password. (There is no password for the id Administrator.)

If Oracle Business Intelligence Suite Enterprise Edition is not installed, see "Oracle Business Intelligence Suite Enterprise Edition".

Changing the Maximum Data Files Option

Oracle Communications Data Model supports the partition of transaction-related fact tables according to your data volume estimation. You can specify the start year, end year and then the transaction related fact tables are partitioned by the date as one partition for each month.

In order to support the partition of transaction-related fact tables, you might need a different value for the maximum number of data files that is presently specified for the Database.

How to determine the value for maximum number of data files

Use the following formula to determine the value that you need for the maximum number of data files:

Maximum Datafiles = Default Value + 300 + ((End year) - (Start year) + 1) * 12 

How to determine the current value for the maximum number of data files

To determine the current value for the maximum number of data files, log in as DB with DBA account, and then execute the following SQL statement.

show parameter db_files 

In the results for this statement, the value column shows the current maximum number of data files.

How to change the value for the maximum number of data files

To change the value for the maximum number of data files, issue the following statements where new_number is the new value that you want to specify.

alter system set db_files = new_number scope = spfile; 
shutdown immediate 
startup

Disabling the Data Vault Option on the Database

The Oracle Communications Data Model installer requires additional steps on a Vault-enabled database. For an Oracle Database with the Vault option on, take the following steps to disable the Vault option before you install Oracle Communications Data Model:

  1. Shut down the Database.

  2. Issue the following commands.

    cd $ORACLE_HOME/rdbms/lib
    make -f ins_rdbms.mk dv_off ioracl
    
  3. Startup the Database.

Once you have installed Oracle Communications Data Model, you re-enable the Vault, as described in "Re-Enabling the Vault Option on the Database".

AIX Platform: Changing the Database Parameter

If you are installing Oracle Communications Data Model on AIX, apply the following Oracle Database parameter change:

  1. Login to the Database with DBA account.

  2. Execute the following statement:

    alter system set "_olap_parallel_update_small_threshold"=2147483647 scope=spfile;
    
  3. Restart the Database.

Installer Execution

Before you install Oracle Communications Data Model, perform the necessary pre-installation tasks described in "Pre-installation Tasks"

Follow these steps to install Oracle Communications Data Model:

  1. Log in using the user id that you plan to use to run the installation. You should use the same user id to install Oracle Communications Data Model as used to install the Oracle Database and Oracle Business Intelligence Suite Enterprise Edition.

  2. Set the ORACLE_HOME environment variable to the location of the Database on which to install Oracle Communications Data Model.

    For example, suppose that Oracle Home is in the directory /loc/app/oracle/product/11.2.0/

    In a Bourne, Bash, or Korn shell, use these commands to set ORACLE_HOME:

    $ ORACLE_HOME=/loc/app/oracle/product/11.2.0/
    $ export ORACLE_HOME
    

    In a C shell, use this command to set ORACLE_HOME

    % setenv ORACLE_HOME /loc/app/oracle/product/11.2.0/
    
  3. Start the installer from the directory that contains the Oracle Communications Data Model installation files:

    cd directory-containing-OCDM_installation-files
    ./runInstaller
    
  4. The Welcome page is displayed. Click Next.

  5. In the Select Installation Type page, select the type of Oracle Communications Data Model installation that you want to perform:

    • If you want to install the Oracle Communications Data Model component, select Communications Data Model. Making this selection performs the installation described in "Communications Data Model Installation".

    • If you want to install the Oracle Communications Data Model sample reports and sample data, select Sample Reports. Making this selection performs the installation described in "Sample Reports Installation".

    Oracle Communications Data Model supports English and 9 other languages. To add support for one language in addition to English, click Product Languages and select the language.

    Click Next.

  6. In the Specify Home Details page, verify that the Name and Path correspond to the Database in which you want to install Oracle Communications Data Model. You can click Browse to navigate to any valid local data file path. Click Next.

  7. In the Product-Specific Prerequisite Checks page, if one or more items are flagged, manually verify that your environment meets the minimum requirements. For details about performing this manual verification, click the flagged item and review the details in the box at the bottom of the page.

    When the status of all items are checked as Succeeded, click Next.

  8. In the Specify Database Connection Information page, provide the following information:

    • Select the Net Service Name which is the alias used for a connect descriptor to connect to the Oracle Database where Oracle Communications Data Model will be installed.

      Tip:

      A net service name is a simple name for a service that resolves to a connect descriptor. Net service names are populated from the OracleHome/network/admin/tnsnames.ora file.
    • Enter the Password for SYSTEM user of the Oracle Database where Oracle Communications Data Model will be installed.

    Click Next.

  9. In the Specify OCDM Schema Information page, specify where all of the data files that correspond to the Oracle Communications Data Model tablespace should reside:

    • If you do not want to use want to the Automatic Storage Management (ASM) feature in Oracle Database, but instead want to explicitly specify a folder name, select File System and enter a folder name. You can click Browse to navigate to any valid local data file path. Click Next.

    • If you have stored your Oracle database files using the Automatic Storage Management (ASM) feature, and you also want store Oracle Communications Data Model data files using ASM, select Automatic Storage Management (ASM). Click Next.

      In the Select ASM Disk Group page, select the disk group in which you want to install the Oracle Communications Data Model data files. Click Next.

  10. In the Specify OBIEE Home page, select the Oracle BI Home and the Oracle BI Data Home directories and on your system. You can click Browse to navigate to any valid local data file path. Click Next.

  11. In the Specify Calendar Data Range page, specify the calendar data range by providing values for Start Date and Number of Years. This information is used to populate the calendar data.

    Start Date must be in the format YYYY-MM-DD; for example, 2007-01-01 stands for January 1, 2007. Number of Years must be a whole number.

    Click Next.

  12. The installer summarizes the information that you specified. Check that this information is correct. If necessary, click Back to return to previous screens and make corrections. When you are satisfied with the information, click Install.

  13. The Oracle Communications Data Model component or sample reports are installed. If there are any problems, messages are displayed. After the installation finishes, the end of installation screen appears. Click Exit to end the installer.

After you exit the installer, perform any necessary post-installation tasks described in "Post-Installation Tasks". Then install the other components that you need to create an Oracle Communications Data Model warehouse, as described in Chapter 4, "Installation of Additional Components."

Silent Installation

A silent installation has no graphical output and no input by the user. It is accomplished by supplying Oracle Universal Installer with a response file and specifying the -silent flag on the command line. Use silent installation when you want the same installation parameter on more than one computer.

Selecting a Response File

Before performing a silent installation, you must provide information specific to your installation in a response file. The installer will fail if you attempt an installation using a response file that is not configured correctly. Response files are text files that you can create or edit in a text editor. The response file (cdm.rsp) is located in the /response directory in the directory that contains the Oracle Communications Data Model installation files. Edit the response file according to your requirements for silent installation. To use a response file, first copy it to your system.

Editing the Response File

Use any text editor to edit the response file to include information specific to your system. You must specify values for variables in your response file. Each variable listed in the response file is associated with a comment, which identifies the variable type. For example:

string = "Sample Value" 
Boolean = True or False 
Number = 1000
StringList = {"StringValue 1", "String Value 2"}

The values that are given as <Value Required> must be specified for silent installation. Remove the comment from the variable values in the response file before starting the Oracle Communications Data Model installation.

Specifying a Response File and Starting the Installation

Before you specify a response file, ensure that all values in the response file are correct. To make Oracle Universal Installer use the response file at installation time, specify the location of the response file as a parameter when starting Oracle Universal Installer. To perform a silent installation, use the -silent parameter as follows:

./runInstaller -silent -responseFile absolute_path_and_filename

Caution:

During installation, response files may be copied to subdirectories in the Oracle home. If you have provided passwords or other sensitive information in your response files, then for security purposes you should delete them after completing and verifying the installation.

Silent Installation Log Files

The success or failure of silent installations is logged in the installActions.log file. Additionally, the silent installation creates the silentInstall.log file. The log files are created in the /oraInventory/logs directory. The silentInstallDate_Time.log file contains the following line if the installation was successful:

The installation of Oracle Communications Data Modelwas successful.

The corresponding installActionsDate_Time.log file contains specific information regarding installation.

Security Tips for Silent Installations

The response file contains the installation password in clear text. To minimize security issues, follow these guidelines:

  • Set the permissions on the response files so that they are readable only by the operating system user performing the silent installation.

  • If possible, remove the response files from the system after the silent installation is completed.

Error Handling

Values for variables that are of the wrong context, format, or type are treated as if no value were specified. Variables that are outside any section are ignored. If you attempt a silent installation with an incorrect or incomplete response file, or if Oracle Universal Installer encounters an error, such as insufficient disk space, then the installation will fail.

Post-Installation Tasks

Once you have executed the Installer take the following steps to perform post-installation cleanup and configuration:

  1. Unlock the OCDM_SYS and OCDM_MINING accounts, as described in "Unlocking the OCDM_SYS and OCDM_MINING Accounts".

  2. If you installed the Oracle Communications Data Model sample reports, unlock the OCDM_SAMPLE_SYS account, as described in "Unlocking the OCDM_SAMPLE_SYS Account".

  3. If you installed the Oracle Communications Data Model sample reports and you do not want users to make changes to the schemas, grant only select privileges to those users as described in "Limiting User Privileges When You have Installed the Sample Reports".

  4. Configure the OLAP working environment, as described in "Configuring the Working OLAP Environment".

  5. Ensure that the Oracle Communications Data Model objects are valid, as described in "Ensuring That Oracle Communications Data Model Objects Are Valid".

  6. If you want to use the Database Vault Option and disabled it before installation re-enable the options, as described in "Re-Enabling the Vault Option on the Database".

  7. If necessary, change the values specified for PGA_AGGREGATE_TARGET and WORKAREA_SIZE_POLICY, as described in"Ensuring That PGA_AGGREGATE_TARGET is Set to the Proper Value".

After performing these tasks, install the other components that you need to create an Oracle Communications Data Model warehouse, as described in Chapter 4, "Installation of Additional Components."

Unlocking the OCDM_SYS and OCDM_MINING Accounts

At the end of the installation, the OCDM_SYS and OCDM_MINING accounts are locked. To unlock these accounts:

  1. Log in the Database with a DBA id and password.

    Note:

    The password is case sensitive.
  2. Unlock the accounts by issuing the following SQL statements.

    alter user ocdm_sys account unlock;
    alter user ocdm_mining account unlock;
    

Unlocking the OCDM_SAMPLE_SYS Account

At the end of the installation of the Oracle Communications Data Model sample reports, the OCDM_SAMPLE_SYS account is locked. To unlock this account:

  1. Log in the Database with a DBA id and password.

    Note:

    The password is case sensitive.
  2. Unlock the account by issuing the following SQL statement.

    alter user ocdm_sample_sys account unlock identified by ocdm_sample_sys;
    

Limiting User Privileges When You have Installed the Sample Reports

By default, when you perform a Sample Reports type of Oracle Communications Data Model installation, the sample reports connect to OCDM_SYS schema directly. For security reason, you may want to grant only select privileges to users who will be working with these reports. To grant only select privileges, take the following steps:

  1. Create a dedicated reporting user (for example, OCDM_Report).

  2. Grant select privilege for all Oracle Communications Data Model tables required for reporting to the user you created in Step 1. The easy way is to grant the select privilege for all Oracle Communications Data Model tables, which start with one of the following prefixes: DWA, DWB, DWD, DWR, DWL.

  3. Create a view (or synonym) in OCDM_Report schema, pointing to the OCDM_SYS tables.

  4. In the Oracle Business Intelligence Suite Enterprise Edition repository, change the connection information to point to the new schema.

Assigning Grants to OCDM_MINING

Log in to the database using an ID that has been granted the system privilege with the ADMIN OPTION or that has been granted the GRANT ANY PRIVILEGE system privilege.

Configuring the Working OLAP Environment

To set up a working OLAP environment for an Oracle Communications Data Model warehouse, configure the database with the following parameter and configuration settings:

  • Set sga_target to 35% of available memory.

  • Set pga_aggregate_target to 35% of available memory

  • Set olap_page_pool_size=0. (This specifies dynamic page pool.)

  • Set _olap_page_pool_hi=30 (that is, lower than default of 50).

  • Set _olap_parallel_update_threshold and _olap_parallel_update_small_threshold to a high value (for example, ~2Gb.. 2147483647). These settings turn off parallel update for the analytic workspace.

  • Set memory_max_target to value greater than SGA and PGA settings. This is maximum amount of memory used for both SGA and PGA. The SGA and PGA settings specified are the minimum settings. (Note that failure to set memory_max_target leads to failure of instance startup (the next time these settings are validated which occurs if spfile had an older and distinct setting for memory_max_target).

The following statements illustrate changing these settings.

alter system set sga_target=1365M scope=spfile;
alter system set pga_aggregate_target=1365M scope=spfile;
alter system set memory_max_target=3030M scope=spfile;
alter system set olap_page_pool_size=0 scope=spfile;
alter system set "_olap_parallel_update_small_threshold"=2147483647 scope=spfile;
alter system set "_olap_page_pool_hi"=30 scope=spfile;
alter system set job_queue_processes=5 scope=spfile;
shutdown immediate;
startup;

Re-Enabling the Vault Option on the Database

If you are using the Database Vault Option and disabled it before installation as described in "Disabling the Data Vault Option on the Database", re-enable the Vault option by taking the following steps:

  1. Shutdown the Database.

  2. Execute the following statements.

    cd $ORACLE_HOME/rdbms/lib
    make -f ins_rdbms.mk dv_on ioracle
    
  3. Start the Database.

Ensuring That Oracle Communications Data Model Objects Are Valid

To ensure that all Oracle Communications Data Model objects are valid, log in to the database with a DBA id and password and recompile all objects in OCDM_SYS and OCDM_MINING by issuing the following SQL statements:

exec utl_recomp.recomp_serial('OCDM_SYS');
exec utl_recomp.recomp_serial('OCDM_MINING');

Ensuring That PGA_AGGREGATE_TARGET is Set to the Proper Value

For good performance, you need to ensure that the PGA_AGGREGATE_TARGET is set to the proper value which depends on the physical RAM of your Database Server. You also need to ensure that the WORKAREA_SIZE_POLICY parameter is set to AUTO.

See:

For information on tuning the PGA_AGGREGATE_TARGET initialization parameter, see Oracle Database Performance Tuning Guide.

Note:

Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO.