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 https://support.oracle.com
Review the Security chapter in the Oracle Communication Data Model Implementation and Operations Guide.
ocdm_sys
schema.PGA_AGGREGATE_TARGET
is set to the proper value.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:
Related Topics
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:.
ocdm_sys
schema directly. For security reasons, you may want to grant only select privileges to users who work with these reports.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:
Related Topics
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 $ORACLE_HOME/ocdm/report
directory:
ocdm.rpd
ocdmwebcat.zip
Unzip the Web Catalog
Before you deploy the Web Catalog, you need to unzip ocdmwebcat.zip
.
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.
Note:
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:
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
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;
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.
Note:
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.
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:
Related Topics
Describes recompiling all objects in ocdm_sys
schema.
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:
exec utl_recomp.recomp_serial('OCDM_SYS');
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 4.1.0.19 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 directorysqldeveloper\datminer\scripts.
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 12.1.0.2.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 12.1.0.2.3 or higher, then requirements fulfilled.
If version is lower than 12.1.0.2.3, upgrade the existing Oracle Data Miner Repository to 12.1.0.2.3 or higher. Upgrade Oracle Data Miner Repository using SQL Developer version 4.1.0.19 (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 sqldeveloper\dataminer\scripts
directory
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.
Setting PGA_AGGREGATE_TARGET
Ensure that the WORKAREA_SIZE_POLICY
parameter is set to AUTO
.
Note:
Setting PGA_AGGREGATE_TARGET
to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY
parameter to AUTO
.
See Also:
For information on tuning the PGA_AGGREGATE_TARGET
initialization parameter, see Oracle Database Performance Tuning Guide