3 Installation of Oracle Retail 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 Retail Data Model component or the Oracle Retail 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 Retail 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".

• Before you install the sample data and reports for Oracle Retail 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';

http://hostname:7001/analytics

Ensuring that Required Software Patches are Installed

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

Take the following steps to ensure the required software patches are installed:

• Install OLAP A PATCH FOR 11.2.0.3.0

Changing the Default Value for the Maximum Processes Initialization Parameter

Oracle Retail 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 Retail 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 Retail 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 Retail 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
   

After you install Oracle Retail Data Model, you re-enable the Vault, as described in "Re-Enabling the Vault Option on 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 (rdm.rsp) is located in the /response directory in the directory that contains the Oracle Retail 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 Retail 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 Retails 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 ORDM_SYS Account

At the end of the installation, the ORDM_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 accounts by issuing the following SQL statements.

   alter user ordm_sys account unlock;
   

Unlocking the ORDM_SAMPLE Account

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

Recompiling OLAP Views

After you unlock the ordm_sample account, login with this account and execute the following file in the sample schema:

$ORACLE_HOME/ordm/pdm/olap/ordm_olap_11_2_cubeview_extnd.sql

Limiting User Privileges for Sample Reports

By default, when you perform a Sample Reports Oracle Retail Data Model installation, the sample reports connect to ORDM_SYS schema directly. For security, 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, ORDM_Report).

2. Grant select privilege for all Oracle Retail 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 Retail Data Model tables, which start with one of the following prefixes: DWA, DWB, DWD, DWR, DWL. Also grant select privilege to ORDM_Report on all the ORDM_SYS views. Typically these views are either relational views starting with DWV or OLAP views ending with _VIEW.

3. Create synonyms in ORDM_Report schema pointing to relevant ORDM_SYS objects.

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

Running OLAP Builds to Load Data into Analytical Workspace

The Oracle Retail Data Model Sample Reports installation loads an empty Analytical Workspace named ORDM into the sample schema ordm_sample. You must load the sample schema data into the empty OLAP Analytical Workspace before you can run the reports or view data in the Sample Reports.

Note: the Non-OLAP sample reports such as the data mining related sample reports and relational sample reports work without performing the OLAP Analytic Workspace steps.

Perform the following steps to load data into the Oracle Retail Data Model OLAP Analytical Workspace (depending on your hardware and configuration, the total expected time to complete these steps may be up to two hours):

1. Go to the following directory containing the OLAP source files including the OLAP load scripts:

   cd $ORACLE_HOME/ordm/pdm/olap
   

2. Review the scripts ordm_cube_historical_load.sql and ordm_cube_incremental_load.sql. These scripts contain comments and hints in the which you can use to guide the OLAP load process. For sample schema OLAP loads, you do not need to make any changes to these scripts.

3. Login to ordm_sample schema through SQL*Plus or SQL Developer and verify the entries in the table DWC_OLAP_ETL_PARAMETER. The entries in the table suitable for HISTORICAL load are:

   process_name='ORDM-OLAP-ETL'
   build_method='C'
   cubename='ALL'
   maxjobqueues=4
   calc_fcst='Y'
   no_fcst_yrs=2
   fcst_mthd='AUTO'
   hist_st_mo='BY 2010 M1'
   fcst_st_mo='BY 2012 M1'
   other1=NULL
   other2=NULL
   build_method_type='HISTORICAL'
   

   For more information on the entries in the DWC_OLAP_ETL_PARAMETER table, see Oracle Retail Data Model Reference.

4. Run the script ordm_cube_historical_load.sql from SQL *Plus to execute the HISTORICAL load.

   SQL> Prompt Running the HISTORICAL load
   SQL> @ordm_cube_historical_load.sql
   

5. After the load completes, review the contents of the file ordm_olap_hist_load.log created in directory where you ran the script shown in step 4. This load typically completes in 40-50 minutes (usually in less than one hour). The typical output from a successful HISTORICAL load run is as follows:

   --Typical Output of the full load. :--
   Running the Historical load with build method 'C':- PROMPT
   Historical load attempts to load Non-Forecast and Forecast cubes ...
   
   21-JUL-12 02.17.48.905132000 PM -07:00
   14:17:49 : Loading Non-Forecast Cube:ALL in mode:C
   14:17:50 : Building Non-Forecast Cube:ORDM_SAMPLE.AR,ORDM_SAMPLE.ASSET,ORDM_SAMPLE.CC,ORDM_SAMPLE.CO,ORDM_SAMPLE.CRFMP,ORDM_SAMPLE.CRFMPDC,ORDM_SAMPLE.CSSR,ORDM_SAMPLE.EL,ORDM_SAMPLE.EWGP,ORDM_SAMPLE.IA,ORDM_SAMPLE.INV,ORDM_SAMPLE.IR,ORDM_SAMPLE.IU,ORDM_SAMPLE.LIABILITY,ORDM_SAMPLE.OBUH,ORDM_SAMPLE.OBUT,ORDM_SAMPLE.POLIS,ORDM_SAMPLE.POS,ORDM_SAMPLE.RTEW,ORDM_SAMPLE.SLS,ORDM_SAMPLE.SLSQR,ORDM_SAMPLE.SU,ORDM_SAMPLE.VC in method:CCCCCCCCCCCCCCCCCCCCCCC
   15:00:28 : Clear Dimensions - Done
   15:00:28 : Running Forecast programs and Building Forecast Cubes: SLS_FCST, INV_FCST
   15:00:28 : Building All Forecast Cubes in method:AUTO
   15:00:28 : Building Sales Forecast Cubes using program:SLS_FCST_PROGRAM ''BY 2010 M1'' ''BY 2012 M1'' 2
   15:00:28 : Building Inventory Forecast Cubes using program:INV_FCST_PROGRAM ''BY 2010 M1'' ''BY 2012 M1'' 2
   15:04:22 : output=0
   21-JUL-12 03.04.22.081362000 PM -07:00
   15:04:23 : Historical load has been completed successfully. All future loads can be run in incremental mode. Incremental loads are typically run on a daily schedule.
   15:04:23 : However the Forecast loads can be done on a monthly schedule using following values - Historical Start Month: BY 2010 M2, Forecast Start Month: BY 2012 M2
   15:04:23 : To run the load in incremental mode in future, please run or appropriately schedule the script: ordm_cube_incremental_load.sql
    
   PL/SQL procedure successfully completed.
    
   Elapsed: 00:46:35.59
   

   Note:

   The return value from the package shown in this output at time=15:04:22 is zero. The zero return value, output=0, indicates a successful execution (from a functional standpoint).

6. On successful execution, the HISTORICAL load sets up the data in DWC_OLAP_ETL_PARAMETER such that all subsequent loads can be performed in INCREMENTAL mode.

7. Verify the entries in the DWC_OLAP_ETL_PARAMETER table. The entries in the table suitable for INCREMENTAL load are:

   process_name='ORDM-OLAP-ETL'
   build_method='?'
   cubename='ALL'
   maxjobqueues=4
   calc_fcst='Y'
   no_fcst_yrs=2
   fcst_mthd='AUTO'
   hist_st_mo='BY 2010 M2'
   fcst_st_mo='BY 2012 M2'
   other1=NULL
   other2=NULL
   build_method_type='INCREMENTAL'
   

   For more information on the entries in the DWC_OLAP_ETL_PARAMETER table, see Oracle Retail Data Model Reference.

8. Run the script ordm_cube_incremental_load.sql from SQL *Plus to execute the INCREMENTAL Load:

   SQL> Prompt Running the INCREMENTAL  load
   SQL> @ordm_cube_incremental_load.sql
   

9. After the load is completes, review the contents of the file ordm_olap_incr_load.log created in same directory. This load typically completes in 20 minutes (usually completes in less that one hour). The typical output from a successful INCREMENTAL load run is as follows:

   --Typical Output of the incremental load. :--
   Running the Incremental load with build method '?':- PROMPT
   Incremental load attempts to load Non-Forecast and Forecast cubes and bring them up to date ...
   
   21-JUL-12 03.12.22.367283000 PM -07:00
   15:12:22 : Loading Non-Forecast Cube:ALL in mode:?
   15:12:22 : Building Non-Forecast Cube:ORDM_SAMPLE.AR,ORDM_SAMPLE.ASSET,ORDM_SAMPLE.CC,ORDM_SAMPLE.CO,ORDM_SAMPLE.CRFMP,ORDM_SAMPLE.CRFMPDC,ORDM_SAMPLE.CSSR,ORDM_SAMPLE.EL,ORDM_SAMPLE.EWGP,ORDM_SAMPLE.IA,ORDM_SAMPLE.INV,ORDM_SAMPLE.IR,ORDM_SAMPLE.IU,ORDM_SAMPLE.LIABILITY,ORDM_SAMPLE.OBUH,ORDM_SAMPLE.OBUT,ORDM_SAMPLE.POLIS,ORDM_SAMPLE.POS,ORDM_SAMPLE.RTEW,ORDM_SAMPLE.SLS,ORDM_SAMPLE.SLSQR,ORDM_SAMPLE.SU,ORDM_SAMPLE.VC in method:???????????????????????
   15:31:07 : Clear Dimensions - Done
   15:31:07 : Running Forecast programs and Building Forecast Cubes: SLS_FCST, INV_FCST
   15:31:07 : Building All Forecast Cubes in method:AUTO
   15:31:07 : Building Sales Forecast Cubes using program:SLS_FCST_PROGRAM ''BY 2010 M2'' ''BY 2012 M2'' 2
   15:31:07 : Building Inventory Forecast Cubes using program:INV_FCST_PROGRAM ''BY 2010 M2'' ''BY 2012 M2'' 2
   15:36:18 : output=0
   21-JUL-12 03.36.18.424586000 PM -07:00
    
   PL/SQL procedure successfully completed.
    
   Elapsed: 00:23:56.13
   

   Note:

   The return value from the package shown in this output at time=15:36:18 is zero. This zero return value, output=0, indicates successful execution (from a functional standpoint).

10. The Oracle Retail Data Model OLAP Analytical Workspace is now successfully loaded with the data in the underlying schema.

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 Retail Data Model Objects Are Valid

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

exec utl_recomp.recomp_serial('ORDM_SYS');

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 OBIEE Suite Catalog for Oracle Retail 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 Retail Data Model:

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

   ordm_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 OBIEE

If you installed the Oracle Retail Data Model Oracle sample reports, you need to deploy the Oracle Retail Data Model RPD and webcat on the Business Intelligence Suite Enterprise Edition 11g instance. For more information on deploying RPD and webcat in OBIEE, 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/ordm/report, in the following files:

ordm.rpd

ordmwebcat.zip

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

Perform the following steps to deploy the Oracle Retail 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 Retail Data Model rpd password in IP patch. For information on obtaining the IP Patch, see the Oracle Retail Data Model Release Notes.

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

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

   Go to enterprise console and configure the security realm for the installation and create users, groups, application roles and olap data security filters as described in Appendix A, "Configuration Steps for OBIEE 11g".

3. Following the instructions to "Refresh the User GUIDs" to update the GUIDs. For more information, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.