Skip Headers

Oracle® Communications Data Model Implementation and Operations Guide 11g Release 2 (11.2) Part Number E15883-05 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# B Working with User Privileges in Oracle Communications Data Model

This appendix provides information about managing user privileges in Oracle Communications Data Model. It contains the following topics:

- Accounts Created for Oracle Communications Data Model

- When You Must Consider User Privileges in an Oracle Communications Data Model

- Granting Only Select Privileges to Users of the Sample Reports

## Accounts Created for Oracle Communications Data Model

Installing the Oracle Communications Data Model component creates two accounts: the ocdm_sys and ocdm_mining accounts. Installing the Oracle Communications Data Model sample reports create the ocdm_sample account. Ensure you unlock these accounts with new passwords following the post-installation steps provided in Oracle Communications Data Model Installation Guide.

See:

Oracle Communications Data Model Installation Guide for information on installing Oracle Communications Data Model and for unlocking the ocdm_sys and ocdm_mining accounts

The ocdm_sys and ocdm_mining accounts serve different purposes:

- `ocdm_sys` is the main schema for Oracle Communications Data Model. This schema contains all the relational and OLAP components of Oracle Communications Data Model.

  The Oracle Communications Data Model data mining result tables are also in this schema. The final output from the data mining models is saved back into `ocdm_sys` schema for easy integration with other components. With mining result tables in `ocdm_sys` schema, customer can run report joining relational content with Mining results much easily. For example, customer can query for revenue sum of customers belonging to a specific segment according to Customer Segmentation model.

- `ocdm_mining` is the data mining schema of Oracle Communications Data Model. This schema contains all the mining components of Oracle Communications Data Model except the final result tables.

## When You Must Consider User Privileges in an Oracle Communications Data Model

The installation process grants the necessary privileges required for users of both accounts. After installing the product, you only need to consider user privileges in the following situations:

- The `ocdm_mining` schema requires select privileges to only a small amount of tables in the `ocdm_sys` schema, (that is, only those tables used to hold the results of the data models shipped with Oracle Communications Data Model). If you decide to create additional data mining models that require more table access from `ocdm_sys` schema, grant the select privilege explicitly.

- The intra-ETL programs are executed inside the `ocdm_sys` schema, therefore, they require the full access to that schema. By default, the Oracle Warehouse Builder intra-ETL mappings for Oracle Communications Data Model connect to the `ocdm_sys` schema for intra-ETL execution.

- By default, the Oracle Communications Data Model sample reports connect to the `ocdm_sys` schema directly. For security reason, you may want to grant only select privileges to users of the sample reports by following the steps outlined in "Granting Only Select Privileges to Users of the Sample Reports".

## Granting Only Select Privileges to Users of the Sample Reports

To grant only select privileges to users of the sample reports, 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 OCDM_Report. (The easiest way to select privileges for these tables is to grant all Oracle Communications Data Model tables that start with a prefix of `DWA_`, `DWB_`, `DWD_`, `DWR_`, or `DWL_`.)

3. Create a view (or synonym) in `OCDM_Report` schema that points to the `ocdm_sys` tables.

4. In the Oracle Business Intelligence Suite Enterprise Edition repository for Oracle Communications Data Model, change the connection information to point to the new schema.