![]() Previous |
![]() Next |
The AW CREATE command creates a new workspace and make it the current workspace in your session.
Oracle OLAP automatically executes a COMMIT as part of its procedure for creating an analytic workspace. Previously attached workspaces move down in the list of attached workspaces to make room for the new one at the top of the list.
Also, if the current analytic workspace is creating a different analytic workspace and the current workspace contains a program named TRIGGER_AW, then the TRIGGER_AW program executes.
Note: Before you can create an analytic workspace you need the appropriate SQL GRANT privileges as outlined in "Privileges Needed to Create and Delete Analytic Workspaces". |
Syntax
AW CREATE workspace [position] [UNPARTITIONED|PARTITIONS n] -
[TABLESPACE tblspname [SEGMENTSIZE n [K, M, or G]]]
where position specifies the workspace's position in the workspace list and is one of the following values. (FIRST is the default.)
Parameters
The name of the analytic workspace. Workspace names:
Can be from 1 - 26 characters in length. All characters must come from the database character set and must be letters, numerals, or underscores.
Cannot begin with a numeral and cannot be reserved words in the DML. (Use RESERVED to identify reserved words.)
(Default) Makes the workspace you are attaching the current workspace.
Puts the workspace after the current workspace and before the EXPRESS
workspace. When there are other workspaces attached before the EXPRESS
workspace, the specified workspace is attached after them. When there are no workspaces before the EXPRESS
workspace, LAST makes the specified workspace the current one. LAST ignores any workspaces after the EXPRESS
workspace.
Specify the position of the newly attached workspace relative to an analytic workspace that is already attached. Use AFTER, rather than LAST, to attach an analytic workspace after the EXPRESS
workspace. When specifying BEFORE puts the workspace first, the workspace becomes the current one.
The order of the workspace list determines the order in which workspaces are searched when Oracle OLAP looks for programs or objects named in programs.
Specifies that the relational table that is the analytic workspace is not a partitioned table.
Specifies that the relational table that is the analytic workspace is a hash partitioned table with n partitions. Specifying a value of 0 (zero) for n is the same as specifying UNPARTITIONED. The default value of n is 8.
Specifies the name of an Oracle Database tablespace in which the analytic workspace is created.
Tip: Oracle suggests that you use the TABLESPACE argument to create your workspace in a tablespace that has been prepared for this purpose. Ask your DBA which tablespace use. |
With the CREATE keyword, this argument sets the maximum size of each segment for the workspace being created. When you do not specify K
, M
, or G
, the value you specify for n is interpreted as bytes. When you specify K
, M
, or G
after the value n, the value is interpreted as kilobytes, megabytes, or gigabytes, respectively.
Usage Notes
Analytic Workspace Permissions
You can add security to analytic workspaces at several levels:
At the relational table level using SQL GRANT
statements
At the analytic workspace level and workspace object level using different attachment modes and startup programs. See the AW ATTACH command and "Startup Programs".
Examples