Convert metadata from Analytic Workspaces to CWMLite

Hi,
I'm trying to connect to Oracle OLAP using Dynasight. DynaSight Developer, which seems to use ODBO/MDX architecture, only can "see" SH-schema (Sales History) cubes. I have tried Oracle versions 9.2.0.7, 10.2.0.1 and 10.2.0.2 but only CMWLite data can be queried.
In order to be able to "see" and query the cubes using Dynasight we must create a catalog and add objects to this catalog. The metadata created can be checked at the following tables from OLAPSYS schema:
CWM2$MRALL_CATALOGS
CWM2$MRALL_CATALOG_ENTITY_USES
Is there any API to create cwmlite/CWM1 metadata? I think dimensions and cubes can be created using the Enterprise Manager (in Oracle 10g cubes can only be created using the Enterprise Manager Web) but I don't know how to create the catalog metadata (I still haven't tried Oracle Warehouse Builder).
AWM 10.2.0.2 is very nice but the analytic workspace created can not be queried using Dynasight. Is there any way to "translate/convert" the metadata from the AW to CWM1?
If there's any way to do this then which could be the best way to deploy the objects created between our environments (dev, QA, prod)?
Also, same question using AWM: which is the best way to deploy objects between environments? I saw we can create templates in XML format or export objects to a EIF file, any other options?
Thanks,
Rubén Martí.

Scott,
the Dynasight connector for Oracle OLAP has a very bad performance and returns wrong data (we are waiting for feedback from Dynasight support). On the other hand, the Oracle OLAP DML connector works fine and let us see the AW in object view mode (not in model view mode). Also, the cubes created using AWM can not be accessed using Dynasight connector.
Your comment about setting up the AWs to be queriable through relational views sounds very interesting. Could you please provide the steps required to do so? Will this allow us to see the dimensions, cubes, etc.(metadata) or it will materialize the cubes using snapshots (so that we won't have metadata)?
Cheers,
Rubén.
P.S.: I had to change the OTN user to this because I lost my password when trying to change the email (which is not possible, but I realized too late!)

Similar Messages

How to create OLAP Catalog Metadata from Analytic Workspace

Hi,
How to create OLAP Catalog Metadata objects automatically from Analytic Workspace, not using CWM2_OLAP_AW_OBJECT package.
Is there tool for it?

Analytic Workspace Manager is the supported tool from Oracle for creating OLAP catalog metadata (plus the SQL views required for BI Beans). Hopefully this should be out in June as an additional download following the 9.2.0.3x patch.
However you might want to look at IAF Software's "Coaster" product (http://www.iafsoft.com/products/coaster.htm) which also contains functionality to create the OLAP Catalog. We've had a play around with it and have been impressed.
regards
Mark Rittman

Exploring AW (analytic workspace) in Java

Hello,
I am creating a java program that can retrive data from analytic workspace that is also built with java program, but I don't know how, so I have a couple of questions for those that can help me.
1. Is there anyway that I can insert data into aw dimension with java program?
2. If not how can I map existing tables within Database with analytic workspace dimension?
3. Is there any posibility to connect to aw dimension with MdmDimension class and retrive data with that class ?
4. Can anyone provide any example programs on this?
5. Can anyone provide me a simple example how to explore data within the analytic workspace in Java. I want to retrive data from aw cube or dimension if it is posible.
I appreciate any help,
Thanks

Have you considered using the BI Beans? Just a thought...
Regarding your questions, 1 and 2 are probably best addressed with the OLAP Analytic Workspace API (a.k.a. AW/XML). You might want to take a look at the Javadoc. You can find the latest Oracle OLAP documentation at the following OTN site:
http://www.oracle.com/technology/products/bi/olap/olap.html
As for the other questions, here is some help from an OLAP API developer:
3. Is there any possibility to connect to AW dimension with MdmDimension class and retrieve data with that class?
The simple answer is no. The OLAP API divides functionality into metadata and data. The Mdm and Mtm classes deal with metadata. These classes represent the relationships between AW objects. The Source and Cursor classes deal with data. They are used to define queries and retrieve data. But the getSource() method can be used on just about any Mdm object to get a Source.
4. Can anyone provide any example programs on this?
The "Developer's Guide to the OLAP API" has a lot of examples. But here's a brief example of getting the member IDs of a dimension.
// given objects
DataProvider dp;
MdmPrimaryDimension dimObj;
// we will commonly work with hierarchies rather than dimensions
MdmHierarchy hierObj = dimObj.getDefaultHierarchy();
// get the Source for the hierarchy
Source hier = hierObj.getSource();
// get a Cursor
CursorManagerSpecification cursorManagerSpec =
dp.createCursorManagerSpecification(hier);
SpecifiedCursorManager cursorManager =
dp.createCursorManager(cursorManagerSpec);
Cursor cursor = cursorManager.createCursor();
// retrieve the values
do {
System.out.println(((ValueCursor) cursor).getCurrentValue());
} while (cursor.next());
5. Can anyone provide me a simple example how to explore data within the analytic workspace in Java. I want to retrieve data from AW cube or dimension if it is possible.
The preceding is one example of exploring data from a hierarchy. Getting data from a dimension is nearly identical -- don't call getDefaultHierarchy(), and call getSource() on dimObj. Getting data from a cube is a little more involved. Again, there are excellent
examples in the documentation, but here's a brief one:
// Given objects
DataProvider dp;
TransactionProvider tp;
MdmMeasure salesObj; // dimensioned by customer and time for this example
MdmHierarchy customerHier;
MdmHierarchy timeHier;
// Get Sources
Source sales = salesObj.getSource();
Source customer = customerHier.getSource();
Source time = timeHier.getSource();
// Create the query. We must join the measure to its dimensions.
Source query = sales.join(customer).join(time);
// We have created a new Source, so we need to commit the OLAP API
transaction.
tp.prepareCurrentTransaction();
tp.commitCurrentTransaction();
// Create the Cursor. This Cursor has a more complex shape because the query is more complex.
CursorManagerSpecification cursorManagerSpec =
dp.createCursorManagerSpecification(hier);
SpecifiedCursorManager cursorManager =
dp.createCursorManager(cursorManagerSpec);
CompoundCursor cursor = (CompoundCursor) cursorManager.createCursor();
// retrieve the values
do {
Iterator iter = (cursor.getOutputs().iterator();
boolean first = true;
while (iter.hasNext()) {
if (!first)
System.out.print(", ");
System.out.print(((ValueCursor) iter.next()).getCurrentValue());
first = false;
System.out.print(": ");
System.out.println(cursor.getValueCursor().getCurrentValue());
} while (cursor.next());
Hope this is helpful.

Is it possible to create relational view on Analytic Workspace in Oracle 9i Release1

Hi All,
We are in the initial stages of Oracle 9i OLAP prototype. Since the current version of BIBeans 2.5 does not work with Release 2 of Oracle 9i OLAP, we are planning to use Oracle 9i OLAP Release 1. So can you please answer the following questions.
1. Is it possible to create relational view on Analytic Workspace(like in Release 2) and populate the OLAP catalog, if so can you give me guidance to get the appropriate user guide. The OLAP DML guide in Release 1 talks about creating OLAP catalog metadata for Analytic Workspace using a metadata locator object.
2, Is it advisable to use Oralce 9i OLAP Release 1? Does the Analytic Workspace and the corresponding BIBeans work in Release 1?
Thank you,
Senthil

Analytic Workspaces (Express/multidimensional data objects and procedures written in
the OLAP DML) are new to Oracle9i OLAP Release 2, you cannot find them in Release 1.
BI Beans will soon (within a week) introduce a version on OTN that will work with Oracle9i OLAP Release 2.

Analytic Workspace Manager 11.2.0.3.0a and Oracle11g 11.2.0.4

Hello!
I'm trying to connect from Analytic Workspace Manager, version 11.2.0.3.0a (latest one), to Oracle server ver. 11.2.0.4. Connection fails with following message "This version of Analytic Workspace Manager is incompatible with the database instance.". Is there a way to make this work? The solution I'm aware of is to downgrade a server. Maybe someone knows other solutions?
Best regards
Bart

hello bart,
try with oracle client 12C Oracle Database 12c Release 1 for Microsoft Windows (x64)
Oracle client 12C contains awm 12C
regards
jean marc

How can I query analytical workspace ?

Hello,
I am using EBS module ODP which uses Analytical workspaces.
I do not know at all technical subject about Analytical workspaces and OLAP.
In ODP , I create measures. And ODP provides some report to display and update data stored in my measures.
I would like to extract data from my measures. How can I do this ?
=> How can I find the internal measure name, the measure column or attribute ...
=> Are there functions to extract the data (like sql language to read in tables )
=> Can anyone give me some commands, and examples to start extracting simple data from my measures(I have had a look to Oracle documentation, but they are very technical and I don't know how to start).

There are views available in OLAPSYS schema which will give information about the Analytical workspaces and their objects.
For extracting data from Analytic workspaces you may use the TABLE FUNCTIONS.
You may refer 'B14346-01 - Oracle OLAP DML Reference 10g Release 2 (10.2)' for details.
Regards,
Maruthi

Invisible structure in Analytic Workspace Manager after importing from EIF

Hello,
I got problem with migration OFA structure (6.3.4) to Oracle OLAP. My Oracle Database is 11.2 Enterprise Edition
1. I've exported OFA database do eif file.
2. I've created user in Oracle database, grant olap_user and created directory
3. I installed Analytic Workspace Manager 11.2.0.3.0A
4. After connection on Analytic Workspaces I run 'Create Analytic Workspace from EIF file ...' -> The import was succeeded
Here is the problem - there is no visible imported structure in the tree under Analytic Workspaces. I think that structures were properly imported. That Analytic Workspace is in the sql results:
select dbal.owner||'.'||substr(dbal.table_name,4) awname, sum(dbas.bytes)/1024/1024 as mb, dbas.tablespace_name from dba_lobs dbal, dba_segments dbas where dbal.column_name = 'AWLOB' and dbal.segment_name = dbas.segment_name group by dbal.owner, dbal.table_name, dbas.tablespace_name order by dbal.owner, dbal.table_name
I've also tried using Analytic Workspace Manager Worksheet.
AW CREATE OFA_TEST
IMPORT ALL FROM EIF FILE 'c/baza.eif' DATA DFNS
UPDATE
COMMIT
The results are the same :(
What else should be done ? can anyone pls help me on this??
Grzegorz

Grzegorz,
OFA to OLAP is not an easy thing if you are trying to do it by hand. That is why we built an OFA conversion utility into our product. Example time for Full OFA to OLAP/Escendo conversion is about three days for an OFA system of 300-400Gb, including data, processes (Solves) reports, saved selections etc.)
Part of the problem is that OFA is an application which uses a ton of back end catalogs which drive everything. It also makes very heavy use of saved selections internally which makes straight export and import tough.
The overall process is that all of the visible structures need to be created within OLAP so that they are visible. We support both 'public' (ergo visible, metadata based) objects as well as 'back end' structures which are not visible to the front end. If you need business logic translated over it can get complicated to do by hand as well, since things don't map directly into the way Oracle does things in AWM now, due to some differences between the architectures.
One of the great things about putting your OFA into OLAP is that everything becomes available to any standard SQL reporting application.
Our IDE is a full mulit-developer environment which allows multiple developers to work even within the same AW, for any operation, including creation of dimensions, measures etc. as well as the editing of code in programs & models.
Are you just trying to get the data in? or are you wanting to use the system like you would use OFA?
Karl

Analytic Workspace Manager now available on OTN

The Analytic Workspace Manager can now be downloaded from OTN at http://otn.oracle.com/software/htdocs/devlic.html?http://download.oracle.com/otn/java/olap/awm920.zip. It's 217MB and i've got it downloading now...
It requires the 9.2.0.4.1 patch which can be downloaded from Metalink, using patch number 3084634
To apply the 9.2.0.4.1 patch, you also need to have installed the 9.2.0.4 database patch beforehand, which can be downloaded from metalink using patch number 3095277.
regards
Mark

I've managed to install the AWM + requisite patches now, and it's converting a relational star schema as I speak. Some points to note (not all steps listed here BTW)
1. I first applied the 9.2.0.4 patch to an existing 9.2.0.1 database installation, which was installed alongside 9iAS R2, 9iDS, OWB9.2 and 9.0.4, and Express Server 6.3.4. The installer failed at an early stage with a 'resource bundle' error, and therefore I removed all Oracle software from my laptop, reinstalled just the Database 9.0.2.0.1, and started again from there.
2. Follow the steps in the readme to drop the XMLCONCAT function, shutdown the database, and stop all services (including the database) in the ORACLE_HOME. Make sure you exit out of SQL*Plus before moving on.
2. Run the 9.2.0.4 patch installer, install the new OUI, then install the 9.2.0.4 patch.
3. Find the init.ora file (in my case named init.ora.962003152553 and located in C:/9ir2/admin/markr/pfile), and amend the file setting java_pool_size and shared_pool_size > 150M. You may need to set sga_max_size to a figure that is greater than these two amounts to fit this in. The figures I used were;
sga_max_size=500000000
java_pool_size=160554432
large_pool_size=8388608
shared_pool_size=160331648
4. Startup the listener (lsnrct start), and the database (using 'startup migrate)
5. set spool on, then run catpatch.sql
6. run @ %ORACLE_HOME%/rdbms/admin/utlrp.sql
7. Unlock the OLAPSYS account, then connect as OLAPSYS, then run @ %ORACLE_HOME%/cwmlite/admin/postamd.sql. When I ran this script, I got an error saying that a column I tried to add ('IS_AGGREGATABLE') already existed, but the rest of the script ran ok.
8. I then unzipped the 9.2.0.4.1 patchset
9. Run the One-Off patch that comes with the 9.2.0.4.1 patchset (in the /oneoffs directory) before you install the main 9.2.0.4.1 patch
10. Once this has installed, start up the OUI that comes with Oracle 9i and select the products.jar file that comes with the patch. Install the patch as normal.
11. cd $ORACLE_HOME/olap/admin, then connect as sqlplus "/ as sysdba", then run @olapu92041.sql
12. Now the patches have all installed, unzip the awm920.zip file to a directory, run the installer, and the AWM will appear under the '%ORACLE_HOME%/Integrated Management Tools' start menu entry.
I'm now in the process of trying to create an analytic workspace. I've submitted the COST_CUBE from the SH schema that comes with 9iR2 for conversion, although from what I understand this will not convert properly, and it has to be replaced by the BIBDEMO schema that comes with the BI Beans 9.0.3 download (http://otn.oracle.com/software/products/bib/download.html). The conversion's at 55% at the moment, so i'll see how it goes, and report back.

Creating Database Standard Form Analytic Workspaces

Just been looking through the new 9.2.0.4.1 documentation and came across the following. Thought it might be useful.
The 9.2.0.4.1 release of Oracle OLAP introduces a new concept known as �Database Standard Form� Analytic Workspaces. This is a way of constructing analytic workspaces in a standard way such that they can be used by tools such as the Analytic Workspace Manager, the Java OLAP API, and BI Beans.
When analytic workspaces are created from a relational star-schema using the Analytic Workspace Manager, it automatically creates the analytic workspace in standard form as part of the migration process. However, if you�re migrating an Express database to Oracle OLAP, the migrated database has to be processed to be in standard form before it is usable by any of the new Oracle OLAP GUI tools.
If you create an analytic workspace using PL/SQL or the OLAP Worksheet, of course you can create dimensions, variables, relations and so on in any form, just as you can create table structures, joins, views and columns in any form in a relational database. However, the database standard form requirement stipulates that;
Certain objects and properties need to be found in the analytic workspace, that are used by tools such as the Analytic Workspace Manager to perform tasks such as aggregation, data loads, and OLAP API enablement. OLAP DML views (beginning with AW$) need to created in the analytic workspace, to provide metadata and to identify relationships between objects in the analytic workspace. Objects need to be registered in the OLAP Catalog, and these registrations have to be kept in sync so that the OLAP tools are aware of changes to the base objects. Data that is migrated in to an analytic workspace, from a relational star-schema using the Analytic Workspace Manager, is already in database standard form and no further work is needed. However, some work is needed to get migrated Express databases into standard form, and Oracle have provided a utility with the 9.2.0.4.1 release of Oracle OLAP to help accomplish this.
This utility, known as CREATE_DB_STDFORM, is an OLAP DML program that takes existing Oracle Express Objects metadata in a migrated Express database, and uses this to create the additional metadata required to make the analytic workspace �database standard form�.
Once CREATE_DB_STDFORM has been used to create this additional metadata, it can also be used to import data into the workspace either from flat files, or from Oracle tables and views. If you don�t have Express Objects metadata in the Express database, CREATE_DB_STDFORM doesn�t work, and you�ll have to use Oracle Warehouse Builder 9.2 to initially create a relational star-schema that equates to the Express database, then use the OLAP Bridge within OWB to export the data into a database standard form analytic workspace.
CREATE_DB_STDFORM, once run, allows the migrated Express database to be accessed via BI Beans straight afterwards, as it creates all the OLAP Catalog entries required for the OLAP API. If the Express database only contains data at the lowest level (i.e. it hasn�t been rolled up), aggregation wizards in the Analytic Workspace Manager can be used to summarise the data as required.
CREATE_DB_STDFORM doesn�t do everything, however. First of all, you need to have created Oracle Express Objects metadata within the Express database, which is an additional step and not always appropriate for all systems. In addition, you need to create time dimensions in a particular way, which may require the data model to be adjusted to meet this requirement. Lastly, any Express language programs within the Express database may need to be adjusted to remove or change commands that have changed or become obsolete.
The new document, �Oracle OLAP Application Developers Guide Release 9.2.0.4.1�, available on metalink under note 251352.1, details how database standard form works, has code examples, and walks through the migration of the XADEMO Express database to an analytic workspace using database standard form.

In your message, you wrote "Certain objects and properties need to be found ... aware of changes to base objects". A large bit is represented by "...". Question is whether I have any commands or package functions that I can use to set up all the proper objects and relationships to make it have database standard form, short of regressing to a ROLAP star schema and usnig the AWM wizard. I have what appears to be working MOLAP activity, all created at the OLAP worksheet prompt, and loaded with DML program. Do I really have to put that all aside and start with a star schema? No way to put my AW in standard form for OLAP API without this?

Creating a DWMQY DIMENSION using Analytic Workspace Manager

Hi everyone,
I need some help creating a "time aware" (DAY, WEEK, MONTH, QUARTER, and YEAR) dimension using Analytic Workspace Manager.
Let me give you some background. I'm coming from a traditional "Oracle Express" OLAP background where all our data is stored in cubes and these are defined, populated and operated on using OLAP DML, there is no SQL or traditional relational tables involved.
I now want to pull data from relational tables into some OLAP cubes and am using Analytic Workspace Manager to do this (maybe this is not the best way?)
Let me explain what I'm trying to achieve. In OLAP worksheet I can type the following DML commands:
DEFINE MY_DAY DIMENSION DAY
MAINTAIN MY_DAY ADD TODAY '01JAN2011'
What this will do is create a "day dimension" and will populate it with values for each and every day between 1st Jan 2011 and today. It will be fully "time aware" and thus you can use date functions such as DAYOF to limit the MY_DAY dimension to all the Fridays etc. Similarly if I define a "month dimension" there will be an automatic implicit relationship between these two dimensions, this relationship and time aware cleverness is built into Oracle.
However, a dimension defined using DML commands (and indeed all objects created using DML language) is not visible in Analytic Workspace Manager (as there is no metadata for them?) and for the life of me I cannot work out how to create such a dimension using AWM. If I create a "Time Dimension" then, as far as I can tell, this is not a proper time dimension but merely a text dimension and I, presume, I have to teach it time awareness.
Can anyone help me? I have no issues creating, and populating cubes from relational tables using Analytic Workspace Manager, the only issue I have is creating a "proper" time aware dimension.
Many thanks in anticipation.
Ian.

When a dimension is of type "TIME" in AWM, then for each member of that dimension, you need END_DATE and TIMESPAN attributes in addition to the key column and description column.
So in your case, if there are 5 levels: DAY->WEEK->MONTH->QTR->YEAR
then you will need atleast 15 columns in your source sql table/view
or 20 columns if you have separate column for description.
For example the columns in your source table/view could be:
DAY_ID,
DAY_DESC,
DAY_END_DATE, (which will be that day's date)
DAY_TIMESPAN, (which will be 1)
WEEK_ID,
WEEK_DESC,
WEEK_END_DATE,
WEEK_TIMESPAN,
MONTH_ID,
MONTH_DESC,
MONTH_END_DATE,
MONTH_TIMESPAN,
QTR_ID,
QTR_DESC,
QTR_END_DATE,
QTR_TIMESPAN,
YEAR_ID,
YEAR_DESC,
YEAR_END_DATE,
YEAR_TIMESPAN
Just "map" this table/view to the 5-level time dimension in AWM.
NOTE that behind-the-scenes lot of useful structures are automatically defined to support time-series measures,
and there are lot of calculation templates available also.
Since you came from Express background, I have to say that try to use new OLAP Expression Syntax when creating calculated measures instead of OLAP DML.
Its very rare these days that we need OLAP DML.
Edited by: Nasar on Nov 22, 2012 12:11 PM

Creating a Analytic Workspace

hi,
i use the AWM 10.2.0.3.Now I want to create a analytic workspace without the AWM, but i want to see the things what I have created in him. I Know that I can use the dbms_aw package to create an aw and for the dimensions and so on the dbms_awm package. For the OLAP Catalog Metadata I want to use the cwm2 package. How I have understood I must first create the Metadata for the OLAP Catalog with the cwm2 package and then I can define the dimensions with the dbms_awm. Is that right???
At first I have defined a aw with the command: execute dbms_aw.execute ('aw create ''myaw''');
After this I want to create the OLAP Catalog Metadata for the dimension Placement, but by creating the mappings he brings an excepiton and I don't know why.
execute cwm2_olap_dimension.create_dimension('GLOBAL', 'Placement_DIM', 'Placement', 'Placements', 'Place', 'Placements');
exec cwm2_olap_dimension_attribute.create_dimension_attribute ('GLOBAL','PLACEMENT_DIM','Long Description','Long Descriptions','Long Desc','Long Product Descriptions',true);
exec cwm2_olap_dimension_attribute.create_dimension_attribute ('GLOBAL','PLACEMENT_DIM','Place_NAME_DIM','Placement Name','Place Name','Placement Name');
exec cwm2_olap_hierarchy.create_hierarchy ('GLOBAL','PLACEMENT_DIM','STANDARD','Standard','Std Placement','Standard Placement Hierarchy','Unsolved Level-Based');
exec cwm2_olap_dimension.set_default_display_hierarchy ('GLOBAL','PLACEMENT_DIM','standard');
exec cwm2_olap_level.create_level ('GLOBAL','PLACEMENT_DIM','L4','Placement ID','Placement Identifiers','Place Key','Placement Key');
exec cwm2_olap_level.create_level ('GLOBAL','PLACEMENT_DIM','L3','Placement Sub-Category','Placement Sub-Categories','Place Sub-Category','Sub-Categories of Placements');
exec cwm2_olap_level.create_level ('GLOBAL','PLACEMENT_DIM','L2','Placement Category','Product Categories','Place Category','Categories of Placements');
exec cwm2_olap_level.create_level ('GLOBAL','PLACEMENT_DIM','L1','Total Placement','Total Placements','Total Place','Total Placement');
exec cwm2_olap_level_attribute.create_level_attribute ('GLOBAL','PLACEMENT_DIM','Long Description','L4','Long Description','PLACEMENT_LABEL','L4 Long Desc','Long Labels for PLACEMENT Identifiers',TRUE);
exec cwm2_olap_level_attribute.create_level_attribute ('GLOBAL','PLACEMENT_DIM','Long Description','L3','Long Description','SUBCATEGORY_LABEL','L3 Long Desc','Long Labels for PLACEMENT Sub-Categories', TRUE);
exec cwm2_olap_level_attribute.create_level_attribute ('GLOBAL','PLACEMENT_DIM','Long Description','L2','Long Description','CATEGORY_LABEL','L2 Long Desc','Long Labels for PLACEMENT Categories', TRUE);
exec cwm2_olap_level_attribute.create_level_attribute ('GLOBAL','PLACEMENT_DIM','PLACE_NAME_DIM','L4','PLACE_NAME_LEV','Placement Name','Placement Name','Placement Name');
exec cwm2_olap_level.add_level_to_hierarchy ('GLOBAL','PLACEMENT_DIM','STANDARD','L4','L3');
exec cwm2_olap_level.add_level_to_hierarchy ('GLOBAL','PLACEMENT_DIM','STANDARD','L3','L2');
exec cwm2_olap_level.add_level_to_hierarchy ('GLOBAL','PLACEMENT_DIM','STANDARD','L2','L1');
exec cwm2_olap_level.add_level_to_hierarchy ('GLOBAL','PLACEMENT_DIM','STANDARD','L1');
--- Creating the Mappings -----
exec cwm2_olap_table_map.Map_DimTbl_HierLevel ('GLOBAL','PLACEMENT_DIM','STANDARD','L4','GLOBAL','PLACEMENTS','PLACE_ID');
exec cwm2_olap_table_map.Map_DimTbl_HierLevelAttr ('GLOBAL','PLACEMENT_DIM','Long Description','STANDARD','L4','Long Description','GLOBAL','PLACEMENTS','PLACE_DESC');
exec cwm2_olap_table_map.Map_DimTbl_HierLevelAttr ('GLOBAL','PLACEMENT_DIM','PROD_NAME_DIM','STANDARD','L4','PLACE_NAME_LEV','GLOBAL','PLAcEMENTS','PLACE_NAME');
exec cwm2_olap_table_map.Map_DimTbl_HierLevel ('GLOBAL','PLACEMENT_DIM','STANDARD','L3','GLOBAL','PLACEMENTS','PLACE_SUBCATEGORY');
exec cwm2_olap_table_map.Map_DimTbl_HierLevelAttr ('GLOBAL','PLACEMENT_DIM','Long Description','STANDARD','L3','Long Description','GLOBAL','PLACEMENTS','PLACE_SUBCATEGORY_DESC');
exec cwm2_olap_table_map.Map_DimTbl_HierLevel ('GLOBAL','PLACEMENT_DIM','STANDARD','L2','GLOBAL','PLACEMENTS','PLACE_CATEGORY');
exec cwm2_olap_table_map.Map_DimTbl_HierLevelAttr ('GLOBAL','PLACEMENT_DIM','Long Description','STANDARD','L2','Long Description','GLOBAL','PLACEMENTS','PLACE_CATEGORY_DESC');
exec cwm2_olap_table_map.Map_DimTbl_HierLevel ('GLOBAL','PLACEMENT_DIM','STANDARD','L1','GLOBAL','PLACEMENTS','PLACE_TOTAL');
After this procedures I want to create and refresh the dimensions with the command:
execute dbms_awm.create_awdimension ('GLOBAL','PLACEMENT','GLOBAL','MYAW','AW_PLACE');
execute dbms_awm.refresh_awdimension('GLOBAL','MYAW','AW_PLACE);
I hope someone can follow me what I want to do.
Thanks

1. Windows 7 x64
2. awm11.1.0.7.0B
3. Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
4. on my machine
5. This file contains a lot of information, I can not read it properly...
Dump file c:\oracle_db\app\jrq-\diag\rdbms\orcl\orcl\incident\incdir_31205\orcl_ora_6124_i31205.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.1 Service Pack 1
CPU                 : 2 - type 8664, 2 Physical Cores
Process Affinity    : 0x0x0000000000000000
Memory (Avail/Total): Ph:1435M/4082M, Ph+PgF:3822M/8163M
Instance name: orcl
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
Windows thread id: 6124, image: ORACLE.EXE (SHAD)
*** 2014-06-11 00:21:58.561
Dump continued from file: c:\oracle_db\app\jrq-\diag\rdbms\orcl\orcl\trace\orcl_ora_6124.trc
ORA-07445: exception encountered: core dump [kghfrf()+367] [ACCESS_VIOLATION] [ADDR:0x0] [PC:0x8ED8231] [UNABLE_TO_WRITE] []
ORA-03113: end-of-file on communication channel
========= Dump for incident 31205 (ORA 7445 [kghfrf()+367]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_WRITE] [ADDR:0x0] [PC:0x8ED8231, kghfrf()+367]
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
Process Id: 0x0000191c Thread Id : 0x000017ec    Time : Wed Jun 11 00:21:58
Excp. Code: 0xc0000005 Excp. Type: ACCESS_VIO    Flags: 0x00000000

Analytic Workspace Manager Release date

Does anyone know that release date for the analytic workspace manager?

I'm reluctant to start having a go at Oracle, because there's probably good technical reasons why AWM didn't come out last year, most probably due to 9i OLAP API changes invalidating much of the work the product team had done with the prototype of AWM. However, it's been about 18 months now, by my reckoning, since AWM was first talked about and it's still not generally available.
Of course, the features announced for the first version of AWM are only part of what we need 'out in the field' when working with 9i OLAP. We also need graphical tools to load analytic workspaces directly, rather than having to write OLAP DML dataloaders or go through an intermediate step of loading an Oracle star-schema, and in addition, migration tools for Express databases to help with the creation of OLAP Catalog metadata.
It's worth contrasting this with the release of OLAP Services when SQL Server 7.0 was released. There, Microsoft provided tools from the outset to create and manage OLAP cubes, which meant that users could get up and running immediately, not have to wait the best part of two years to get the most basic of tools to enable them to create OLAP databases.
As there's no doubt been quite a few technical challenges in delivering the 9i OLAP tools over the last couple of years, what would probably help the situation would be a more proactive communication strategy from the Oracle product team, in the way that the OWB team regularly post on their OTN forum and keep us all informed on how the product is progressing. Part of the frustration with 9i OLAP is the lack of any communication or updates on the product, leaving us guessing as to exactly when elements such as the AWM will actually come out. In addition, from what I can glean about OLAP support in 10g, there's some excellent news coming out, such as Multiwriter support, an XML interface for OLAP, Parallel support for aggregation and so on, which would be great news to hear and might make people 'hang on' rather than give up on the product.
Hopefully, as the last announcement from Oracle suggested, the AWM will be made available this month, and we can get on then with helping our customers and clients start taking advantage of the 9i OLAP platform.

Analytic Workspaces and Database Tablespace

Hi,
I am trying to understand the intricacies in the setup of Analytic Workspaces and their corresponding tablespaces in the database, and here is the background:
I created an Analytic Workspace, say AW1 in a database that had a tablespace, say TS1. After sometime, I created another Tablespace, TS2 in the same database and using the same schema as before, created an Analytic Workspace, AW2 in TS2.
However, AW2 seems to get created in TS1 even though I select TS2 explicitly at the time of creating AW2. Also, if I drop an AW created using TS2 and then import it again (in the same schema) from the template, it gets created in TS1 and not TS2 as I would expect.
In essence, it seems to me that all AWs get created in the TS that was the first TS of my database (TS1 in this case), irrespective of the fact that I created them in different Tablespaces. Also, for all these experiments, the database and the environment is the same.
Can anyone please explain this behavior?
For reference, the database in use is Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, Oracle Label Security, OLAP and Data Mining Scoring Engine options
and the AWs have been created using Oracle Analytic Workspace Manager (AWM) v10.2.0.3.0A.
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Piyush,
AWM lets you specify the tablespace for your AW which allows you to override the default tablespace for the user. However, this information is not recorded in the XML template. Therefore, if you create an AW in a non-default tablespace, save the definition to an XML template, drop the AW and use the XML template to rebuild the AW then the AW will get created in the default tablespace.
There are two workarounds to this (that I can think of)
1) Use a script to rebuild the AW from the XML template and alter the users default tablespace as part of the script and then set it back after the AW has been built.
2) Use the AW Create packages that do allow you to specify the tablespace for the AW, run the DML command to create the standard form metadata and then script the loading of the XML definitions for each dimension and all your cubes.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Deployment of Analytic Workspace

Hi,
I have a query regarding the deployment of an AW in various environments like dev, test and live.
When we first create the AW in dev environment, we specify an AW name and the tablespace to be allocated for that particular AW. For deploying the AW in different environment, we use the XML template that is exported from the AW using 'Export Analytic Workspace to Template' option. But while creating the AW from template, there is no option to specify the tablespace for the new environment.
Could anyone please help me how tablespace can be specified while deploying AW in other environments.
Thanking in advance,
Mainak

This is a bit of a hack, but it will work
Towards the end of the XML template file you should see an entry something like this.
<AW
Name="MY_AW"
Version="11.2">
</AW>The name of the AW will obviously be different, and the version may be different as well. It doesn't matter because you will just delete the section from the XML document.
Now in AWM you first create an empty AW using the simple "Create Analytical Workspace..." option. This will allow you to specify a tablespace. Once you have done this you select "Create Analytical Workspace From Template..." and import your objects into the AW you just created. Note that you must create an AW with the same name as the original as it is embedded into the XML for the cubes and dimensions.
The more sophisticated version of this is to delete the AW section above and then add a header to the XML template
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>Finally you replace all occurrences of your AW name with the string
&AW_NAME;For example, instead of
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="STAR_CONSISTENT"
AddUniqueKeyPrefix="False"
AW="MY_AW">you would have
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="STAR_CONSISTENT"
AddUniqueKeyPrefix="False"
AW="&AW_NAME;">You can see this type of XML if you export a single cube or dimension to a template. I don't know why AWM doesn't let you do the same thing for the whole AW.

MV vs. Analytic workspace

Good morning,
I read the document http://www.oracle.com/technology/products/bi/db/11g/pdf/comparision_aw_mv_11g_twp.pdf
and I not understand clearly the difference, this probably made due to a poor knowledge of English.
Someone just enlighten me?
AW generates views for the cubes and dimensions, allowing a SQL query, the MV too.
The MV directly contain any aggregates but it is also possible with cubes (you can define a level of aggregation total).
My assertions are they correct?
So what are the major differences between the MV and analytic workspace Oracle?
Thank you once again in advance,
David

The data for an 11g cube is stored in an AW. This includes both leaf and aggregate data.
This data in a cube can be accessed directly by an automatically generated SQL View. (This is sometimes called an 'ET View'.)
Optionally, the system can also generate an MV on top of the cube. This MV should be thought of as pure metadata on top of the cube -- the MV itself does not contain any data. The closest analogy is the
CREATE MATERIALIZED VIEW ON PREBUILT TABLE
statement. The MV defined on top of the cube provides a number of things.
(1) You can access the data directly by running SELECT * FROM <cube mv>. This is possible, but gives you nothing that you could not get by selecting from the ET View instead.
(2) It ties the cube back to the source tables so that the system will know if the data in the cube (i.e. the AW) is FRESH or STALE.
(3) It allows you to optimize the build of the cube by using FAST MV refresh if you change only a few rows in your fact table.
(4) It allows the system to rewrite queries against the source tables to access the cube directly.

Convert metadata from Analytic Workspaces to CWMLite

Similar Messages

Maybe you are looking for