Setting Up User Names - OLAP

To connect to the database, a user must present a user name and password that can be authenticated by database security. All users must have the CONNECT role. The additional privileges associated with that user name control the user's access to data. As a database administrator, you must set up user names with appropriate credentials for all users of Oracle OLAP applications.

You can define user names and grant them these rights from the Security folder of Oracle Enterprise Manager or by using SQL commands.
Two roles are defined on installation of the database explicitly to support Oracle OLAP:

  • OLAP_USER role provides users with the privileges to create and manage OLAP Catalog metadata and standard form analytic workspaces in their own schemas. Any OLAP user who will be performing these tasks should have the OLAP_USER role or equivalent privileges.
  • OLAP_DBA role provides a DBA or system administrator with privileges to create and manage OLAP Catalog metadata and standard form analytic workspaces in any schema. The OLAP_DBA role is granted with the DBA role. Care should be taken in extending this privilege to additional users.

SQL Access For DBAs and Application Developers

To create OLAP Catalog metadata, users must be granted the OLAP_USER role. To create analytic workspaces, users also need SELECT privileges on the source schema tables, and an unlimited quota on the tablespace in which the workspace is created. Example shows the SQL statements for creating the GLOBAL_AW user.

SQL Statements for Creating the GLOBAL_AW User

SQL Access for Analysts

To access an existing analytic workspace, users must have these access privileges on the table in which the workspace is stored:

  • To read from the analytic workspace, SELECT privileges.
  • To write to the analytic workspace, SELECT, INSERT, and UPDATE privileges.

Note that the name of the table is the same as the name of the analytic workspace, with the addition of an AW$ prefix. For example, the XADEMO analytic workspace is stored in the AW$XADEMO relational table. For users to access views of workspace data, they must be granted EXECUTE privileges explicitly on those views. Example shows the SQL statements that gives all users read-only privileges to the GLOBAL analytic workspace, and user SCOTT read/write privileges.

Granting Access Rights to the GLOBAL Analytic Workspace

Access to Database Objects Using the BI Beans

To connect to the database using the BI Beans, users must have the following access rights to the database:

  • CONNECT role
  • QUERY REWRITE system privilege
  • SELECT privileges on the database objects containing the data to be analyzed, whether the data is stored in an analytic workspace or in relational tables. Refer to the previous topic, "SQL Access for Analysts", for information about granting access to analytic workspaces.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

OLAP Topics