AW CREATE |
The AW CREATE command creates a new workspace and make it the current workspace in your session.
|
Note: Oracle OLAP automatically executes a COMMIT as part of its procedure for creating a 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, when a program named TRIGGER_AW exists in the analytic workspace, the execution of an AW CREATE statement automatically executes that program. |
Syntax
AW CREATE workspace [position] [UNPARTITIONED|PARTITIONS n] -
[SEGMENTSIZE n [K, M, or G]] [TABLESPACE tblspname]
where position specifies the workspace's position in the workspace list and is one of the following values. (FIRST is the default.)
Arguments
The name of the analytic workspace. You must specify the name. You cannot specify an alias because no alias is assigned when you are creating. When you create a workspace, keep in mind the following rules for workspace names: Workspace names can contain only letters, numerals, and underscores; they cannot begin with a numeral; they cannot be reserved words in the DML; and they can be no more than 26 characters in length. (Use RESERVED to identify reserved words.) All characters must come from the database character set.
(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 a workspace that is already attached. Use AFTER, rather than LAST, to attach a 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 will be 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.
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.
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 you should use. |
Notes
Security and 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 AW ATTACH and "Startup Programs".
Examples