Specifies the steps to perform after the installation.
After you run Oracle Universal Installer perform the following post-installation steps:
After you install Oracle Communications Data Model, obtain the IP Patch. To obtain the IP Patch for the latest information about Oracle Communications Data Model, patch sets, go to My Oracle Support at
Review the Security chapter in the Oracle Communication Data Model Implementation and Operations Guide.
Describes how to unlock the OCDM_SYS account and set a password on this account.
Unlocking the OCDM_SYS Account
At the end of the installation, the OCDM_SYS account is locked. To unlock this account:
The password is case sensitive.
alter user ocdm_sys account unlock identified by password;
Enter a password for the OCDM_SYS account that is secure, according to the password guidelines described in Oracle Database 2 Day DBA. Do not to use OCDM_SYS as a password.
If you installed the sample reports, you need to also perform several postinstallation steps.
If you installed the Oracle Communications Data Model sample reports, then perform the following steps:.
Describes how to unlock the OCDM_SAMPLE account.
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:
The password is case sensitive.
alter user ocdm_sample account unlock identified by <password>;
Enter a password for the OCDM_SAMPLE account that is secure, according to the password guidelines described in Oracle Database 2 Day DBA. Do not to use OCDM_SAMPLE as a password.
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 reasons, you may want to grant only select privileges to users who work with these reports.
Limiting User Privileges
To grant only select privileges, perform the following steps:
Describes installing the RPD file and deploying the Web Catalog.
If you installed the Oracle Communications Data Model sample reports, you need to deploy the Oracle Communications Data Model RPD and Web Catalog on the Oracle Business Intelligence Suite Extended Edition 12c 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
Unzip the Web Catalog
Before you deploy the Web Catalog, you need to unzip
Update the RPD Connection Pool
Do the following to update the RPD connection pool:
Open Oracle Business Intelligence Developer Client Tools and select File->Open->Offline...,
Browse to locate $ORACLE_HOME/ocdm/report/ocdm.rpd
Double click Connection Pool in ODWT at the Physical layer.
Update the Host, Port, Service and User name to point to Oracle Communications Data Model schema.
In addition, follow steps 2 and 3 to update the connection pool in OCDM_OLAP at the Physical layer.
Click OK to exit and then click Save.
Test the connection pool to check that it is successfully configured. Right click a table, such as
DWA_ACCT_DEBT_MO in the
ODWT.OCDM_SYS. Select, Update Row Count. If no errors are reported then the connection pool is successfully configured.
Deploy the RPD and Web Catalog
Perform the following steps to deploy the Oracle Communications Data Model RPD and Web Catalog:
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.
When you deploy the RPD you need to provide an RPD password. Contact Oracle Support to obtain a temporary RPD password.
Log in 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.
To set up a working OLAP environment for an Oracle Communications Data Model warehouse, configure the database with the specified parameter and configuration settings.
Configuring the Working OLAP Environment
sga_target to 35% of available memory.
35% of available memory
olap_page_pool_size=0. (This specifies dynamic page pool.)
olap_page_pool_hi=30 (that is, lower than default of
_olap_parallel_update_small_threshold to a high value (for example,
~2Gb.. 2147483647). These settings turn off parallel update for the analytic workspace.
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
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;
Perform these steps to load data into the Oracle Communications Data Model OLAP Analytical Workspace (depending on your hardware and configuration, the total expected time to complete these steps may be up to one hour).
The Oracle Communications Data Model Sample Reports installation loads an empty Analytical Workspace named OCDM into the sample schema
ocdm_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.
The Non-OLAP sample reports such as the data mining related sample reports and relational sample reports work without performing these OLAP Analytic Workspace steps.
ocdm_sampleschema through SQL*Plus or SQL Developer.
SQL>begin pkg_ocdm_olap_etl_aw_load.run; end; / SQL>
This load typically completes in 30-35 minutes (usually in less than one hour).
SQL> select cubename,load_status,error_dtl from dwc_olap_activity order by cubename; / SQL>
ACM COMPLETED-SUCCESS ADM COMPLETED-SUCCESS AGRMNT COMPLETED-SUCCESS APM COMPLETED-SUCCESS CCM COMPLETED-SUCCESS CHRN COMPLETED-SUCCESS CMSN COMPLETED-SUCCESS COM COMPLETED-SUCCESS CSM COMPLETED-SUCCESS IAM COMPLETED-SUCCESS INV COMPLETED-SUCCESS INVCM COMPLETED-SUCCESS RVN COMPLETED-SUCCESS SLS COMPLETED-SUCCESS
Describes the process of re-enabling Oracle Database Vault if before installing you disabled Oracle Database Vault, and then you want to re-enable Oracle Database Vault.
Re-Enabling Oracle Database Vault
If you are using Oracle Database Vault and disabled this option before installation then re-enable Oracle Database Vault by taking the following steps:
PATHare 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
In Oracle Database 12c, Oracle Enterprise Manager Database Express is built into the Oracle database. It requires no special installation or management.
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk dv_on make -f ins_rdbms.mk ioracle
sqlplus sys as sysoper Enter password: password SQL> STARTUP SQL> EXIT $ emctl start dbconsole $ lsnrctl start listener_name
For Oracle RAC installations, restart each instance as follows:
$ srvctl start database -d db_name
Describes recompiling all objects in
Recompiling Objects in OCDM_SYS
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 by issuing the following SQL statements:
If you want to use Oracle Data Miner with Oracle Communications Data Model to perform data mining, verify that the Oracle Data Miner Repository is available in the database instance and configure Oracle Communications Data Model for Oracle Data Miner.
Check that Oracle Data Miner Repository is installed in the database instance by running the following command as a user with SYSDBA privileges:
SELECT SUM(CASE WHEN username = 'ODMRSYS' THEN 1 ELSE 0 END ) AS schema_cnt FROM dba_users;
If schema_cnt is 0 after this command, then Oracle Data Miner Repository is not in the database. Install Oracle Data Miner Repository using SQL Developer Version 18.104.22.168 or higher. When you unzip the downloaded SQL Developer, it creates the
sqldeveloper directory. After installation the Oracle Data Miner scripts and the readme files are in the directory
SQL Developer is available at the site: http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html
If schema_cnt is 1, then Oracle Data Miner Repository exists in the database. The minimum version required is 22.214.171.124.3. To verify the version of Oracle Data Miner Repository, run the following command as a user with SYSDBA privileges:
SELECT property_str_value AS version FROM odmrsys.odmr_repository_properties WHERE property_name= 'VERSION';
If the version is equal to 126.96.36.199.3 or higher, then requirements fulfilled.
If version is lower than 188.8.131.52.3, upgrade the existing Oracle Data Miner Repository to 184.108.40.206.3 or higher. Upgrade Oracle Data Miner Repository using SQL Developer version 220.127.116.11 (http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html). When you unzip the downloaded SQL Developer, it creates
sqldeveloper directory. You can find Data Miner scripts and readme under
GRANT CREATE TABLE, CREATE VIEW, CREATE MINING MODEL, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TYPE, CREATE SYNONYM, CREATE ANY INDEX, CREATE JOB, CREATE RULE, CREATE RULE SET, CREATE EVALUATION CONTEXT, CREATE SESSION TO ocdm_sys; GRANT EXECUTE ON sys.dbms_random TO ocdm_sys; GRANT EXECUTE ON ctx_ddl TO ocdm_sys; GRANT EXECUTE ON ctxsys.ctx_ddl TO ocdm_sys; GRANT CTXAPP TO ocdm_sys; GRANT EXECUTE ON sys.dbms_lock TO ocdm_sys; GRANT EXECUTE ON odmrsys.odmr_workflow TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_messages TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_project_workflow TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_workflow_all TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_workflow_log TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_workflow_nodes TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_workflow_models TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_wf_clas_test_results TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_wf_regr_test_results TO ocdm_sys; GRANT SELECT ON odmrsys.odmr_user_wf_test_results TO ocdm_sys;
CREATE DIRECTORY ocdm_odm_workflow_dir AS '<$ORACLE_HOME>/ocdm/pdm/mining/src/odmr_gui_files/odmr_workflow_xml';
GRANT READ, WRITE ON DIRECTORY ocdm_odm_workflow_dir TO ocdm_sys;
conn ocdm_sys/<schema password> @<$ORACLE_HOME schema password> @<$ORACLE_HOME >/ocdm/pdm/mining/src/odmr_gui_files/pkg_ocdm_mining_odmr_util.sql;
conn ocdm_sys/<schema password>@<$ORACLE_HOME>/ocdm/pdm/mining/src/odmr_gui_files/ocdm_import_odm_workflow.sql;
Check the status of the workflows execution.
To improve performance ensure that the
PGA_AGGREGATE_TARGET is set to the proper value.
The value specified for
PGA_AGGREGATE_TARGET depends on the physical RAM of your Database Server.
Ensure that the
WORKAREA_SIZE_POLICY parameter is set to
PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the
WORKAREA_SIZE_POLICY parameter to
For information on tuning the
PGA_AGGREGATE_TARGET initialization parameter, see Oracle Database Performance Tuning Guide