3 Installation of Oracle Communications Data Model

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:

• Before you install Oracle Communications Data Model:

  • Confirm that the required Database options are installed by following the steps outlined in "Confirming that Oracle Data Mining and OLAP Options are Installed".

  • Confirm that Oracle Warehouse Builder is installed by following the steps outlined in "Confirming that the OWBSYS Schema Exists".

• Before you install the sample data and reports for Oracle Communications Data Model, confirm that Oracle Business Intelligence Suite Enterprise Edition is installed as described in "Confirming that Oracle Business Intelligence Suite Enterprise Edition is Installed".

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

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

http://hostname:9704/analytics

Changing the Default Value for the Maximum Processes Initialization Parameter

Oracle Communications Data Model requires that the initial value for the PROCESSES initialization parameter be set to a value greater than the default database installation value.

How to determine the current value for the PROCESSES parameter

To determine the current value for the maximum processes parameter, log in as DB with DBA account, and then execute the following SQL statement:

show parameter processes;

How to change the value for the maximum processes

To change the value for the maximum processes, issue the following statements. Depending on your database options, the value specified for processes should be set to a minimum value greater than or equal to 250.

alter system set processes=250 scope=spfile; 
shutdown immediate 
startup

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.

To find out if the Oracle Database is Vault-enabled, do the following:

SELECT * FROM V$OPTION WHERE PARAMETER = 'Oracle Database Vault';

If this command returns true, then the Vault option is enabled.

To disable the Vault option, do the following:

1. On UNIX systems, ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set.

2. Log in to SQL*Plus as user SYS with the SYSOPER privilege.

3. Shut down the Database.

4. From the command line, stop the Database Control console process and the listener. For example:

   sqlplus sys as sysoper
   Enter password: password
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   $ emctl stop dbconsole
   $ lsnrctl stop listener_name
   

   For Oracle RAC installations, shut down each database instance as follows:

   $ srvctl stop database -d db_name
   

5. Disable the Oracle Database Vault option with the following commands (this is a UNIX system example):

   cd $ORACLE_HOME/rdbms/lib
   make -f ins_rdbms.mk dv_off
   cd $ORACLE_HOME/bin
   relink all
   

   For Oracle RAC installations, run these commands on all nodes.

6. Startup the Database, Database Control console process, and listener. For example, on UNIX, Log in to SQL*Plus as user SYS with the SYSOPER privilege and restart the database. Then from the command line, restart the Database Control console process and listener. For example:

   sqlplus sys as sysoper
   Enter password: password
   SQL> STARTUP
   SQL> EXIT
   $ emctl start dbconsole
   $ lsnrctl start listener_name
   

   For Oracle RAC installations, restart each database instance as follows:

   $ srvctl start database -d db_name
   

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.

Ensuring That a Value is Set for the Service Name

Ensure that in tnsname.ora, the service name is provided. To do this, perform the following steps:

1. Go to the directory: $ORACLE_HOME/network/admin.

2. Edit tnsnames.ora to make sure the "SERVICE_NAME" value is provided. For example:

   orcl11g =
   (DESCRIPTION =
   (ADDRESS = (PROTOCOL = TCP)(HOST = server1.us.oracle.com)(PORT = 1521))
   (CONNECT_DATA =
   (SERVER = DEDICATED)
   (SERVICE_NAME = orcl)
   )
   )
   

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.

tnsname db-name

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

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 Model was 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.

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 Account

At the end of the installation of the Oracle Communications Data Model sample reports, the OCDM_SAMPLE 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 account unlock identified by <password>;
   

Recompiling OLAP Views

After you unlock the ocdm_sample account, login with this account and execute the following statements to recompile the OLAP views in the sample schema:

ALTER VIEW CUST_RVN_VIEW_OLAPC COMPILE;
ALTER VIEW CUST_RVN_VIEW_FIN COMPILE;

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, Database Control console process, and listener. For example on UNIX, ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set. Log in to SQL*Plus as user SYS with the SYSOPER privilege and shut down the database. Then from the command line, stop the Database Control console process and listener. For example:

   sqlplus sys as sysoper
   Enter password: password
   SQL> SHUTDOWN IMMEDIATE
   SQL> EXIT
   $ emctl stop dbconsole
   $ lsnrctl stop listener_name
   

   For Oracle RAC installations, shut down each database instance as follows:

   $ srvctl stop database -d db_name
   

2. Enable the Oracle Database Vault option.

   cd $ORACLE_HOME/rdbms/lib
   make -f ins_rdbms.mk dv_on
   make -f ins_rdbms.mk ioracle
   

3. Startup the Database, Database Control console process, and listener. For example, on UNIX, Log in to SQL*Plus as user SYS with the SYSOPER privilege and restart the database. Then from the command line, restart the Database Control console process and listener. For example:

   sqlplus sys as sysoper
   Enter password: password
   SQL> STARTUP
   SQL> EXIT
   $ emctl start dbconsole
   $ lsnrctl start listener_name
   

   For Oracle RAC installations, restart each database instance as follows:

   $ srvctl start database -d db_name
   

4. For Oracle RAC installations, repeat these steps for each node on which the database is installed.

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.

Installing Oracle Business Intelligence Suite Enterprise Edition Catalog for Oracle Communications Data Model

Once Oracle Business Intelligence Suite Enterprise Edition is installed, follow these steps to install an Oracle Business Intelligence Suite Enterprise Edition catalog for Oracle Communications Data Model:

1. Add a definition for ocdm_db for the Oracle Communications Data Model repository to use when connecting to the database. Add this definition to the file $ORACLE_HOME/network/admin/tnsnames.ora:

   ocdm_db =
   (DESCRIPTION =
   (ADDRESS = (PROTOCOL = TCP)(HOST = hostname.domain)(PORT = port-number))
   (CONNECT_DATA =
   (SERVER = DEDICATED)
   (SERVICE_NAME = SID) # Change your SID, Hostname, and Listener PortNumber
   )
   )
   

   Tip:

   Be careful to split these commands properly when you add them to the file; for example, do not add them as one long concatenated line of code.

   Note:

   If you want to use another database name, you must change the tnsname in the Oracle Business Intelligence Suite Enterprise Edition repository. See the Oracle Business Intelligence Suite Enterprise Edition documentation for directions for defining a database connection in repository.

Installing RPD and WebCat for Business Intelligence Suite Enterprise Edition

If you installed the Oracle Communications Data Model Oracle sample reports, you need to deploy the Oracle Communications Data Model RPD and webcat on the Business Intelligence Suite Enterprise Edition 11g instance. For more information on deploying RPD and webcat in BIEE, see the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

After you use the installer to install the sample reports you can find the rpd file and the webcat file in the directory $ORACLE_HOME/ocdm/report, in the following files:

ocdm.rpd

ocdmwebcat.zip

Before you deploy the webcat, you need to unzip ocdmwebcat.zip.

Perform the following steps to deploy the Oracle Communications Data Model rpd and webcat.

1. Use your browser to open the weblogic Enterprise Manager portal:

   http://SERVERNAME:7001/em
   

   Login with the weblogic admin ID and password.

   Go to Business Intelligence --> coreapplication --> Deployment--> Repository

   and then deploy the rpd and webcat.

   Notice that when you deploy the rpd you need to provide the rpd password, you can find Oracle Communications Data Model rpd password in IP patch. For information on obtaining the IP Patch, see the Oracle Communications Data Model Release Notes.

2. Use your browser to open the weblogic console portal:

   http://SERVERNAME:7001/console/login/LoginForm.jsp
   

   Login with your weblogic admin ID and password. Go to your security realm and create a user named "ocdm" and set a password for this user.

3. Following the instructions to "Refresh the User GUIDs" to update the GUIDs. For more information, see Oracle Fusion Middleware Administrator's Guide.