This chapter describes how to install Oracle Utilities Data Model:
Before you install the Oracle Utilities Data Model, perform the following tasks:
Back up the Oracle Database.
Ensure that the software required for Oracle Utilities Data Model is installed, as described in "Ensuring Required Software is Installed".
Set the maximum processes initialization parameter, as described in "Changing the Default Value for the Maximum Processes Initialization Parameter".
Increase the maximum number of data files, as described in "Changing the Maximum Data Files Option".
If you are using Oracle Database Vault, disable the option, as described in"Disabling Oracle Database Vault".
Ensure that the tnsnames.ora
file includes a value for SERVICE_NAME
, as described in "Ensuring a Value is Set for the Service Name".
Ensure that the tnsnames.ora
file entry matches the SID, as described in "Oracle System Identifier (SID) and Service Name Parameter".
As discussed in "Software Requirements", you must have certain software installed before you can successfully install the Oracle Utilities Data Model component or the Oracle Utilities 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 Utilities 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 Utilities 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".
To check that the Oracle Data Mining and OLAP options are installed, log in as SYS
and enter the following SQL queries:
SELECT VALUE FROM V$OPTION WHERE PARAMETER ='Data Mining'; SELECT VALUE FROM V$OPTION WHERE PARAMETER ='OLAP';
To test that Oracle Business Intelligence Suite Enterprise Edition is installed, open the following link in a browser.
http://hostname:7001/analytics
The sample Oracle Business Intelligence Suite Enterprise Edition login window is displayed.
If Oracle Business Intelligence Suite Enterprise Edition is not installed, see "Oracle Business Intelligence Suite Enterprise Edition".
Note:
The7001
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.Oracle Utilities 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 to the Oracle Database as DBA, 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
Oracle Utilities 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 to the Oracle Database as DBA, 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
The Oracle Utilities Data Model installer requires additional steps on a Vault-enabled database. For an Oracle Database with the Oracle Database Vault enabled, take the following steps to disable Oracle Database Vault before you install Oracle Utilities 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 Oracle Database Vault is enabled.
To disable the Oracle Database Vault, do the following:
On UNIX systems, 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.
Shut down the database.
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
Disable Oracle Database Vault 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.
Startup the Oracle Database, Database Control console process, and listener. For example, on UNIX systems, 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 have installed Oracle Utilities Data Model, you reenable Oracle Database Vault, as described in "Reenabling Oracle Database Vault".
For more information, see Oracle Database Vault Administrator's Guide.
Ensure that in tnsnames.ora
file, the service name is provided. To do this, perform the following steps:
Go to the directory: $ORACLE_HOME/network/admin
.
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) ) )
During installation, in the Specify Database Connection Information page provide a Net Service Name. The following rules for tnsnames.ora
are mandatory for the Utilities Data Model option installation:
For an environment other than Oracle RAC, the installer sets the Oracle System Identifier (SID) to the value of the lowercase tnsnames entry chosen by the user (as the Net Service Name). Thus, the tnsnames entry must accurately reflect the Net Service Name supplied as a parameter during installation.
For example, if the SID is orcl11203
, you cannot set the tnsnames entry to OUDM_Test. If SID is orcl11203
, then tnsnames entry must be set to orcl11203
.
For an Oracle RAC environment, the SID is set to lowercase tnsnames entry chosen by the user (as the Net Service Name). Thus, the tnsnames entry should accurately reflect the SID for the system on which the product is installed in an Oracle RAC environment.
Modify the tnsnames.ora
entry name to match the SID of the database node for the system. After the installation, revert the tnsnames entry to the previous entry.
Follow the same procedure during deinstallation. When reinstalling or installing the Utilities Data Model option at a later stage, modify the tnsnames entry name.
For example, if the SID is orcl2
, you cannot set the tnsnames entry to localhost_orcl
. In this case, if the SID is orcl2
, then the tnsnames entry must be set to orcl2
.
Before you install Oracle Utilities Data Model, perform the necessary preinstallation tasks described in "Preinstallation Tasks".
Note:
You must install Oracle Utilities Data Model on the localhost where the database server is located. You can determine the value of your localhost by issuing the following command wheredb_name
is the name of your Oracle database.
tnsname db_name
Follow these steps to install Oracle Utilities Data Model:
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 Utilities Data Model as used to install the Oracle Database and Oracle Business Intelligence Suite Enterprise Edition.
Set the ORACLE_HOME
environment variable to the location of the database where you want to install Oracle Utilities Data Model.
For example, suppose Oracle home is in the directory /loc/app/oracle/product/dbhome
In a Bourne, Bash, or Korn shell, use these commands to set ORACLE_HOME
:
$ ORACLE_HOME=/loc/app/oracle/product/dbhome $ export ORACLE_HOME
In a C shell, use this command to set ORACLE_HOME
:
% setenv ORACLE_HOME /loc/app/oracle/product/dbhome
Start the installer from the directory that contains the Oracle Utilities Data Model installation files:
cd directory-containing-OUDM_installation-files
./runInstaller
The Welcome page is displayed. Click Next.
In the Select Installation Type page, select the type of Oracle Utilities Data Model installation that you want to perform:
If you want to install the Oracle Utilities Data Model component, select Utilities Data Model. Making this selection performs the installation as described in "Utilities Data Model Installation".
If you want to install the Oracle Utilities Data Model reports and sample data, select Sample Reports. Making this selection performs the installation as described in "Sample Reports Installation".
Oracle Utilities Data Model supports English. The option provided to add support for one language in addition to English is not used at the time of this release.
Click Next.
In the Specify Home Details page, verify that the Name and Path correspond to the database in which you want to install Oracle Utilities Data Model. You can click Browse to navigate to any valid local data file path.
Click Next.
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.
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 Utilities 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 theOracleHome
/network/admin/tnsnames.ora
file.Enter the Password for SYSTEM user of the Oracle Database where Oracle Utilities Data Model will be installed.
Click Next.
The Specify OUDM Schema Information page is displayed when you select to install the component, Utilities Data Model. In this dialog specify where all the data files that correspond to the Oracle Utilities Data Model tablespace should reside:
If you do not want to use 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 Utilities 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 Utilities Data Model data files.
Click Next.
The Specify OUDM Sample Schema Information page displays when you select to install the Sample Reports. In this dialog you specify where all the data files that correspond to the Oracle Utilities Data Model sample schemas should reside:
If you do not want to use 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 Utilities 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 Utilities Data Model data files.
Click Next. When you install the sample reports, the next page shows the installer Summary that summarizes the information that you specified, as shown in step 13.
In the Specify Calendar Date Range page, specify the calendar date range by providing values for Start Date and Number of Years. The installer uses this information to populate the calendar data. A recommended Number of Years value is 15 years. Specifying larger Number of Years values proportionally increases the time it takes to implement the partitioning portion of Oracle Utilities Data Model install activity. The start year specified with Start Date should be the lowest possible dates from your historical data load (lowest possible CDR date typically). There is no easy method to incrementally extend the time dimension, so your initial choice for Number of Years should be specified to meet your needs for a reasonably long time.
Start Date must be in the format YYYY-MM-DD
; for example, 2011-01-01 stands for January 1, 2011. Number of Years must be a whole number.
Note:
These calendar dates have nothing to do with the number of years you will effectively keep the data. The calendar as such is totally independent of the Information Lifecycle Management process you may use.Click Next.
In the Specify Partitions for reference and base tables page, specify the number of Second Level hash partitions for each entity, Organization, Customer, Party, Account, Agreement, MeterReading, InitialReading, FinalReading, ServiceQuantity, and Interval Partition Start Date. Specify a value for each field. If you enter an invalid value, then the installer shows a dialog displaying the valid values. For each value you specify, you should choose a value that is a power of 2 (for example: 4, 8, 16, 32, 64 and so on). Enter a date for the Interval Partition Start Date in the specified format (YYYY-MM-DD
).
Click Next.
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.
The Oracle Utilities 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 exit the installer.
After you exit the installer, perform any necessary postinstallation tasks described in "Postinstallation Tasks". Then install the other components that you need to create an Oracle Utilities Data Model warehouse, as described in Chapter 4, "Installation of Additional Components."
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.
Before performing a silent installation you must provide information specific to your installation in a response file. The installer fails if you attempt a to perform a silent 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 udm.rsp
is located in the /response
directory (located in the directory that contains the Oracle Utilities 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.
Note:
You must install Oracle Utilities Data Model on the localhost where the database server is located. You can determine the value of your localhost by issuing the following command wheredb_name
is the name of your Oracle database.
tnsname db_name
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 Utilities Data Model 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.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 silentInstall
Date_Time
.log
file contains the following line if the installation was successful:
The installation of Oracle Utilities Data Model was successful.
The corresponding installActions
Date_Time
.log
file contains specific information regarding installation.
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.
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.
After you install Oracle Utilities Data Model, perform following steps as appropriate for your particular installation:
Obtain the IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Utilities Data Model patch sets, go to My Oracle Support at https://support.oracle.com
.
Unlock the OUDM_SYS
account, as described in "Unlocking the OUDM_SYS Account".
If you installed the Oracle Utilities Data Model sample reports, then perform the following steps:
Unlock the OUDM_SAMPLE
account, as described in "Unlocking the OUDM_SAMPLE Account".
If 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"
Install the RPD and Web Catalog, as described in "Installing RPD and Web Catalog for Oracle Business Intelligence Suite Enterprise Edition".
Configure the OLAP working environment, as described in "Configuring the Working OLAP Environment".
If you want to enable Oracle Database Vault and you disabled it before installation, then reenable Oracle Database Vault, as described in "Reenabling Oracle Database Vault".
Ensure that the Oracle Utilities Data Model objects are valid, as described in "Ensuring Oracle Utilities Data Model Objects are Valid".
If necessary, change the values specified for PGA_AGGREGATE_TARGET
and WORKAREA_SIZE_POLICY
, as described in"Ensuring PGA_AGGREGATE_TARGET is Set to the Proper Value".
After performing these tasks, install other components that are required for your particular Oracle Utilities Data Model warehouse, as described in Chapter 4, "Installation of Additional Components."
After running the installer the OUDM_SYS
account is locked. To unlock this account:
Log in to the database as DBA.
Unlock the account by issuing the following SQL statement.
alter user oudm_sys account unlock;
After installing the Oracle Utilities Data Model sample reports, the OUDM_SAMPLE
account is locked. To unlock this account:
Log in to the database as DBA.
Unlock the account by issuing the following SQL statement.
alter user oudm_sample account unlock identified by password;
By default, when you perform a Sample Reports type of Oracle Utilities Data Model installation, the sample reports connect to OUDM_SYS
schema directly. For security reasons, you may want to grant only select privileges to users who will be working with these reports. To grant only select privileges, perform the following steps:
Create a dedicated reporting user (for example, OUDM_Report).
Grant select privilege for all Oracle Utilities 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 Utilities Data Model tables, which start with one of the following prefixes: DWA, DWB, DWD, DWR, DWL.
Create a view (or synonym) in OUDM_REPORT
schema, pointing to the OUDM_SYS
tables.
In the Oracle Business Intelligence Suite Enterprise Edition repository, change the connection information to point to the new schema.
To set up a working OLAP environment for an Oracle Utilities 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 the 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;
If you are using the Oracle Database Vault and disabled it before installation as described in "Disabling Oracle Database Vault", reenable Oracle Database Vault by performing the following steps:
Shutdown the database, Database Control console process, and listener. For example on UNIX systems, 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
Enable Oracle Database Vault.
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk dv_on make -f ins_rdbms.mk ioracle
Startup the Oracle Database, Database Control console process, and listener. For example, on UNIX systems, 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
For Oracle RAC installations, repeat these steps for each node on which the database is installed.
For more information, see Oracle Database Vault Administrator's Guide.
To ensure that all Oracle Utilities Data Model objects are valid, log in to the database as DBA and recompile all objects in oudm_sys
by issuing the following SQL statements:
exec utl_recomp.recomp_serial('OUDM_SYS');
For good performance, 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 Also:
For information on tuning thePGA_AGGREGATE_TARGET
initialization parameter, see Oracle Database Performance Tuning Guide.Note:
SettingPGA_AGGREGATE_TARGET
to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY
parameter to AUTO
.After Oracle Business Intelligence Suite Enterprise Edition is installed, follow these steps to install an Oracle Business Intelligence Suite Enterprise Edition catalog for Oracle Utilities Data Model:
Tip:
In these directions, replace BIEE_HOME with the name of the directory where Oracle Business Intelligence Suite Enterprise Edition is installed, and replace BIEE_DATA_HOME with the name of the directory where Oracle Business Intelligence Suite Enterprise Edition data is stored.Add a definition for oudm_db
for the Oracle Utilities Data Model repository to use when connecting to the database. Add this definition to the file $ORACLE_HOME/network/admin/tnsnames.ora
:
oudm_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.If you installed the Oracle Utilities Data Model Oracle sample reports, must deploy the Oracle Utilities Data Model RPD and Web Catalog on the Business Intelligence Suite Enterprise Edition 11g instance. For more information on deploying RPD and Web Catalog in BIEE, see 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 Web Catalog file in the $ORACLE_HOME/oudm/report
directory:
oudm.rpd
oudmwebcat.zip
Note:
You cannot deploy the RPD file from$ORACLE_HOME/oudm/report
directory. You need to update the connection pool information for each physical schema available in the RPD as follows:
Open repository oudm.rpd
using Oracle Business Intelligence Enterprise Edition.
Change the Data source name in connection pool of each physical schema in physical layer as appropriate for the system where you are deploying the Oracle Utilities Data Model RPD.
Before you deploy the Web Catalog, you must unzip oudmwebcat.zip
.
Perform the following steps to deploy the Oracle Utilities Data Model RPD and Web Catalog.
Use your browser to open the weblogic Enterprise Manager portal:
http://SERVERNAME:7001/em
Log in with the weblogic admin ID and password.
From the Business Intelligence tab select coreapplication, then select Deployment and click Repository. Next deploy the RPD and Web Catalog.
Note:
When you deploy the RPD you must provide an RPD password. Contact Oracle Support to obtain a temporary RPD password.Use your browser to open the weblogic console portal:
http://SERVERNAME:7001/console/login/LoginForm.jsp
Log in with your weblogic admin ID and password. Go to your security realm and create a user named oudm
and set a password for this user.
Follow the instructions to "Refreshing User GUIDs" to update the GUIDs. For more information, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.