![]() Previous |
![]() Next |
Since an analytic workspace is physically stored as a table in an Oracle Database, you need SQL GRANT privileges to work with an analytic workspace. The privileges you need vary depending on whether the analytic workspace is in a schema that you own or in a schema that you do not own:
When you are the owner of the schema, you only need SQL GRANT privileges when you want to create an analytic workspace or attach an analytic workspace. The privileges you must be granted to perform these tasks and the OLAP DML commands that relate to these tasks are outlined in the following table.
When you are not the owner of the schema, you need SQL GRANT privileges to create an analytic workspace, to attach an analytic workspace in ASOF mode, to drop an analytic workspace, and to truncate an analytic workspace as shown in the following table.
Task | OLAP DML Command | SQL GRANT Privileges Needed |
---|---|---|
Create an analytic workspace | AW CREATE |
CREATE ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE |
Attach an analytic workspace AS OF | AW ATTACH with ASOF keyword | FLASHBACK ANY TABLE |
Delete an analytic workspace | AW DELETE | DROP ANY TABLE |
Truncate an analytic workspace | AW TRUNCATE |
TRUNCATE ANY TABLE |
Note that Oracle Database does not turn on roles when you run a named PL/SQL procedure. In this case, the you must have the CREATE TABLE privilege directly.