Oracle9i OLAP User's Guide Release 2 (9.2) Part Number A95295-01 |
|
Creating an Analytic Workspace From Relational Tables, 2 of 6
This chapter primarily describes a tool for creating analytic workspaces. The OLAP Catalog metadata defines a logical analysis model and a map to a physical source. If you cannot create OLAP Catalog metadata because your database does not conform to its requirements, you can still create an analytic workspace manually. The basic steps that parallel the stages performed by the CNV_CWM.TO.ECM
program are also described in this chapter.
The process that you will follow to create an analytic workspace from relational tables is contingent on the design of your schema.
If you have a star or snowflake schema, then you can use the tools described in "Creating an Analytic Workspace Using the CNV_CWM.TO.ECM Program".
Otherwise, follow the instructions in "Manually Creating an Analytic Workspace".
See Also:
Oracle9i OLAP Developer's Guide to the OLAP DML for information about OLAP Worksheet, creating analytic workspaces, aggregating data, and other multidimensional data manipulation techniques. |
The following steps describe how you might approach the task of creating an analytic workspace using the CNV_CWM.TO.ECM
program.
Note: To run the |
sales
in the olapts
tablespace:
AW CREATE sales TABLESPACE olapts AW DETACH sales
CNV_CWM.TO.ECM
will create an analytic workspace if one does not exist already, but it will be created in the default tablespace. The performance of an analytic workspace is better if it is stored in a tablespace that has been created specifically for that purpose.
CNV_CWM.TO.ECM
.
The following example attaches an analytic workspace named sales
and creates the dimensions, attributes, and hierarchies associated with the SALES_QUANTITY
measure.
CALL CNV_CWM.TO.ECM('sales' 'na' 'na' -
'MEASURE::SH::SALES_CUBE::SALES_QUANTITY')
See "CNV_CWM.TO.ECM Program" for the complete syntax.
The CNV_CWM.TO.ECM
utility loads only the base-level data stored in relational tables. It does not load any aggregate data.
AGGREGATE
command.
You now have an analytic workspace. SQL-based applications can use the OLAP_TABLE
function for direct access to the data.
GENSQLOBJS
program to generate SQL scripts for creating relational views of the analytic workspace data. (Optional)SQL-based applications can run directly against these views using standard SQL commands, and thus have access to the workspace data.
If your database design does not allow you to use the CNV_CWM.TO.ECM
program, then you can still develop an analytic workspace from relational tables. However, you will need to use the various programs and procedures that underlie CNV_CWM.TO.ECM
. Their use requires greater familiarity with the OLAP DML.
See Also:
Oracle9i OLAP Developer's Guide to the OLAP DML for information about creating analytic workspaces using the SQL command in the OLAP DML. |
The following are the basic steps.
sales
in the olapts
tablespace:
AW CREATE sales TABLESPACE olapts
DEFINE
command.SQL FETCH
or the SQL
IMPORT
commands.AGGREGATE
command.
You now have an analytic workspace. SQL-based applications can use the OLAP_TABLE
function for direct access to the data.
CWM2_OLAP_AW_ACCESS
PL/SQL package, as described in Chapter 15, "CWM2_OLAP_AW_ACCESS". (Optional)
SQL-based applications can run directly against these views using standard SQL commands, and thus have access to the workspace data.
|
![]() Copyright © 2001, 2002 Oracle Corporation. All Rights Reserved. |
|