Analytical workspace for Oracle10g to use OLAP

hi
i have downloaded Oracle10g Release 2 from oracel website. i couldn find Analytical Workspace with this installation.
what should i do to work with AW manager.
very urgent please
rgds
karthi

Check this link
http://www.oracle.com/technology/products/bi/olap/index.html
Also go through this note on metalink Note:352598.1

Similar Messages

AWM: Enable Analytic Workspace for OLAP API

Hi,
I created an analytic workspace with Analytic Workspace Manager which is based on a relational star-schema.
Now I want to access this analytical workspace by normal SQL-Statements. For this I executed in AWM the 'Enable Analytic Workspace for OLAP API and BI Beans ...' routine which generated views that contain the fact and dimension data.
My problem is that these views are very huge, because they
apparently store all possible combintations of dimension- and fact records. Most of the records contain only NULL values in the fact columns. I also used Composite Dimensions for the fact table in order to reduce sparsity.
Is it normal to have such huge views with mostly NULL values? If yes, how can I handle this in order to get an acceptable performance.
Here an example of a small fact table I use:
A fact table with 5400 records with its two dimension tables (1129 and 233 rows, no hierarchies) produces 263057 rows in the view.
Thanks for any help.

Hi,
First of all, thanks for the quick response flavio.
Meanwhile I have found a solution to my problem:
I don't use the 'Enable Analytic Workspace for OLAP API and BI Beans ...' routine of AWM anymore. Instead, I write my own statement for creating a relational view for the analytical workspace. The statement looks like following:
create or replace force view costrate_cube as
SELECT producttype_number, producttype_description, machine_sk, notok_costrate, production_costrate
FROM TABLE(CAST(OLAP_TABLE(
'costrate_aw DURATION SESSION',
'costrate_table',
'FETCH producttype_dim_producttype_number,
producttype_dim_producttype_description,
produnit_dim_machine_sk, produnit_dim_module_sk,
notok_costrate_variable, production_costrate_variable
USING <costrate_cube_composite>','') as costrate_table));
The important part is the USING clause of the FETCH command. By using the composite of all dimensions of the cube, rows containing only null values in the fact columns are being eliminated. Now I get only the rows which are in my original relational fact table (which is what I wanted).
Werner

Are Analytic Workspaces suitable for very large data sets?

Hi all,
I have made many different tests with analytic workspaces and i have used the different features (compression,composites...). The results especially for maintenance are disappointing.
I have a star schema with 6 dimensions. The fact table has 730 million rows, the first dimension has 2,9 million rows and the other 5 dimensions have between 25 and 300 rows each.
My conclusion is that Analytic Workspaces don't help in situations like mine. The time for maintenance is very very bad not to mention the time for aggregations. I even tried to populate the cube in parts( 90 million rows for the first population) but nothing change. And there are some other problems with storage and tablespaces ( I always get the message unable to extent TEMP tablespace. The size of it is 54Gb).
Is there something i missing? Has anyone similar problem or different opinion?
Thank you,
Ilias

A few other tips to add to Keith's excellent advice:
- How many CPU's does your server have? The answer to this may help you decide the optimal level to partition at (in my experience DAY is too low and can cause different problems). What other levels does your time dimension have? Are you loading your cubes in parallel?
- To speed up your load, partition your underlying fact table with the same granularity as your cubes and place an index on the field mapped to the partition dimension
- Are you using 10.2.0.3? If so, be very careful with the storage data type you choose when creating your cubes. The default in 10.2.0.3 is NUMBER which has the capability of storing data to 38 significant figures. This usually exceeds what is required for most datasets. If your dataset allows you to use storage of 15 significant figures then you should create your cubes using the DECIMAL data type instead. This will use about one third of the storage space and significantly increase your build speeds (in my experience, more than 3 times faster)
- Make sure you have preallocated enough permanent and temporary tablespaces for your build. Autoextending can be very time consuming.
- Consider reducing the amount of aggregation you do in batch. It should not be necessary to pre-aggregate everything in order to get good query performance.
Generally, I would say that the volume should not be a problem. A single dimension with 2.9 million values is fairly big and can be slow (in OLAP terms) to query but that should not be an obstacle to building it in the first place.
Good luck!
Stuart

Cannot drop cube or analytic workspace due to ORA-37409

The error is ORA-37409: cannot delete or truncate AW used by CUBE ORGANIZED table.
This seems very closely related to the bug discussed in this thread: Drop cube organized table
We need to drop and rebuild a cube due to a design change. It looks like there are some CR$ tables related to the cube preventing the drop.
We cannot drop the CR$ table, nor can we drop the cube, nor can we drop the analytic workspace. We have tried disabling materialized view refresh on the cubes (which works but leaves the CR$ tables out there). We have tried the drop using dbms_aw.aw_delete and with dbms_cube.import_xml (to remove everything). No such luck.
Is there a workaround you can give me that will allow us to drop the CR$ tables? Or a workaround that will allow us to drop the workspace?

Update:
Our last attempt to drop the analytic workspace did remove almost all OLAP metadata. However, there were still rows in sys.olap_tab$ with object IDs relating the problem CR$ tables. In a test database, we confirmed that deleting these rows does allow us to drop the CR$ tables that cannot otherwise be dropped. However, running DML against a sys-owned table like this is unwise at best, and certainly an unsupported workaround (unless we can get Oracle's blessing to do it).
We may go through MOS and see if Oracle can provide a one-off patch for the bug listed above, to correct this situation. Or perhaps they may be able to provide some other direction.
This puts us in a situation where our only immediate option may be to uninstall the OLAP option and reinstall it.

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?

Deploying to analytic workspace ....

it would be great if someone can help me with this ...
Every link i have accessed regarding Oracle WarehouseBuilder 11g states that there is an option available for ROLAP dimensions (and cube) to be deployed to an analytic workspace. (I'm using an 11g EE Database).
Does anyone know how this can be done?
Using the "Deploy All" config setting does not seem to work since, when I open AWM, I cannot see my dimensions and cube.
What am i missing?
Thanks!

Hi
Are you using OWB 11gR1 or 10gR2? If so there are 2 storage options for dimensions and cubes;
ROLAP: relational storage
or
MOLAP:multidimensional storage
In OWB 11gR2 there is also a ROLAP with cube MV option (which is a mixture of both).
Essentially the dimensional model can have a relational (ROLAP) implementation or a multidimensional one based in an analytic workspace. So in the storage panel of the dimension or cube if you have defined it as ROLAP no matter whether you set deploy all or whatever, you will only get relational DDL and CWM2 api calls for dimensional/cube metadata. You will need the storage set ot Multidimensional storage giving you the dimension and cube persisted in an Analytic Workspace.
The AW name is defined on the storage panel in OWB. If no name is defined the name of the module is used.
Cheers
David

APEX SSO and Load balancing: Could not determine workspace for application

We had a single HTTP Server serving APEX in a 10.2.0.2 database configured with SSO to be used by the developers. APEX has been registered as a partner application and the login url has been CA Siteminder protected so that the SM_USER details are forwarded in the header for the application to use for authorization. Everything is fine so far.
Now we have added a HTTP Server on another host and have it all set up for APEX and its pointing to the same database. APEX_ADMIN access works as normal, but applications previously using SSO now get the following error after entering the URL.
Expecting p_company or wwv_flow_company cookie to contain security group id of application owner.
Error ERR-7620 Could not determine workspace for application ().
Using HTTP Watch I find that the application is not even trying to redirect to the login page.
What is wrong here?

APEX has been registered as a partner application as described in
http://www.oracle.com/technology/products/database/application_express/howtos/sso_partner_app.html
In the meantime I found metalink document 368746.1 which describes the cause of this problem. Please read carefully what I wrote, it all works when the the new APEX web server is turned off in the server farm on the load balancer and directed through the original web server. When running regapp.sql the hostname in the listener token was using the virtual hostname. This works fine if the request comes from the original APEX server which proofs that there is nothing wrong with the installation and set up of SSO. When directing the request to the new APEX web server the APEX_ADMIN page still works only existing work spaces using SSO don't seems to work anymore resulting in a error as described in the subject.
As for metalink document 368746.1 naming the causes of this error:
- there are no duplicate entries in WWSEC_ENABLER_CONFIG_INFO$
-LISTENER_TOKEN clearly works for requests coming from the first web server
-theoretically the web server listener port could be changed from 7777, but port 80 needs to be maintained here as production is mimiced as far down as possible.
Is there some cache table which can be cleared? How is it that the flows schema (apex engine) can not find the work space when the request comes from a new web server which can however access the APEX_ADMIN pages.
anyone?

Creating Dimension using template in Analytical workspace manager

Hi,
I am rajan, I am working with Oracle's Analytical workspace manager Release 2.
I am trying to create the dimension using the templates from the file. it throws the following error,
The following errors have occurred when loading contents:
Closed Connection
Note : I am referring the tutorial in the following URL,
http://st-curriculum.oracle.com/obe/db/10g/r2/prod/bidw/awm/awm_otn.htm and also i have downloaded the awm.zip file from the same URL and imported into my desktop.
Right now, I am working based on this tutorial only.
Kindly,help me to resolve this issue.
Thanks
Rajan

Francisco,
Query DBA_REGISTRY to verify the status of "OLAP Analytic Workspace" component.
Also, wait for the script to finish and check the status of the objects then.
Thanks,
Hussein

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

How to Export OLAP analytical workspaces

Hi, experts:
I am following Doc. Migrating OLAP From 32 Bits to 64 Bits or Across Platforms (Doc ID 352306.1) to export OLAP analytical workspaces.
I copied and pasted the step 2. as below. But I donot understand some of them. Hope you can help me.
1. What does this mean by: "(NOTE: this following statement is critical so everything in the AW is in STATUS)"?
2. "Replace ALIAS_DIR with a defined directory alias"   This ALIAS_DIR can be anything on current directory?
3. I have more 3 AW. So I have to run the following four scripts 3 times? I have to modify the export_file_name.eif file name for each run, right?
========
2.Use the following SQL commands, for EACH AW that was identified in step #1   (NOTE: All quotes are single quotes). Caution: If you attach multiple AWs and then run the   export command, ONLY the last- attached AW will be exported. --- Replace OWNER.AW_NAME with the the actual OWNER.AW_NAME name SQL> exec dbms_aw.execute('aw attach OWNER.AW_NAME rw'); -- (NOTE: this following statement is critical so everything in the AW is in STATUS) SQL> exec dbms_aw.execute('allstat'); --- Replace ALIAS_DIR with a defined directory alias --- Replace export_file_name.eif with a valid eif file name SQL> exec dbms_aw.execute('export all to eif file ''ALIAS_DIR/export_file_name.eif '''); --- Replace OWNER.AW_NAME with the actual OWNER.AW_NAME name SQL> exec dbms_aw.execute('aw detach OWNER.AW_NAME');
=======
Thank you very much for your help.

1. What does this mean by: "(NOTE: this following statement is critical so everything in the AW is in STATUS)"?
This is just a note to the readers and you can simply run the sql statement as it is in the doc.
2. "Replace ALIAS_DIR with a defined directory alias"   This ALIAS_DIR can be anything on current directory?
Correct but you need to create the directory first -- See Error - EBS DB importing OLAP from 32 bit to 64 for the commands.
3. I have more 3 AW. So I have to run the following four scripts 3 times? I have modify export_file_name.eif file name for each run, right?
Correct.
Thanks,
Hussein

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

Using Oracle Analytical Workspace With Excel

Hi i have created an analytical workspace on Oracle Analytical Workspace, Now suppose i want to access this workspace from Excel , is this possible ?? If so How

Hi,
I understand there are three Oracle plug-ins for Excel: OLAP, OBIEE, and Essbase. I presume the plug-in you are using is the OLAP plug-in, which only works with Oracle 10g or earlier. Starting in Oracle 11g, however, Oracle recommends you use the Simba MDX Provider for Oracle OLAP (http://www.oracle.com/us/corporate/press/036550 and http://www.oracle.com/us/corporate/press/173668).
If you use the MDX Provider, your application can connect directly to the Oracle OLAP cube. Since you are using Excel, your users don't need to connect through Oracle, and you do not need to manipulate the retrieved data before displaying it. Excel and its PivotTables will generate MDX queries against the Oracle database through the MDX Provider, so you don't need to use any plug-ins or APIs. This means you don't need to learn any new menus or APIs -- you just use native Excel functionality. Furthermore, your data is coming live from the Oracle database. Each time you open your workboook, you refresh your data with the Data -> Refresh button, and your spreadsheet data is current, not a stale copy.
Please let me know if I am missing something in your requirements. Feel free to contact me directly if you have any questions or concerns.
Mike

Where to find Analytic Workspace Manager for Oracle9i?

Hi,
I am looking for Analytic Workspace Manager for Oracle 9i. Could someone point me to the place it can be downloaded? On Oracle OTN there are only versions 10g and 11g. I couldn't find it on Metalink either.
Why I need so old version? We are about to upgrade our existing installation from 9i and I need it to see what's inside in our Oracle 9i database (9.2.0.6) before going into 10g.
Or maybe it is possible to use AWM 10g against database 9i? This would solve my problems.
Is it possible to upgrade analytic workspaces from oracle 9i into 10g with analytic workspace manager 10g?
Best wishes
Tomasz Michniewski

Hello Laura,
Well, I was looking for this 9i version of AWM, and I was even thinking that AWM does not exist for 9i. Especially that in 9i documentation AWM is not mentioned.
But in the meantime I have found some install from some our backup cd-rom. It says:
# Analytic Workspace Manager : 9.2.0.4.1
# DATE: September 26, 2003
# Platform Patch for : platform independent
# Product Version # : 9.2.0.4.1
# Product : Analytic Workspace Manager
# Platforms
# Analytic Workspace Manager uses a platform independent install and
# has been approved on the following platforms:
# - Windows NT 4.0, 2000 & XP
# - Solaris 32 & 64-bit
# - Linux 32-bit
# - AIX 64-bit
# - HP-UX 64-bit
# - Tru64
# Requirements
# The Analytic Workspace Manager client requires the following Oracle9i
# Database configuration:
# - Oracle 9.2.0.1.0 Enterprise Edition Database
# - RDBMS 9.2.0.4.0 patch set (PS# 3095277)
# - OLAP 9.2.0.4.1 patch (PS# 3084634)
So is it the AWM for 9i?
Best wishes,
Tomasz Michniewski

Which Analytic Workspace Manager version should I use?

hi
Right now I am using DB 9.2.0.8 with OLAP Analytic Workspace and OLAP Catalog. Then which version of AWM should I use if I would like to create some demo cube on the instance?
this one?
http://otn.oracle.com/software/htdocs/devlic.html?http://download.oracle.com/otn/java/olap/awm920.zip
Thanks,
Scott

I recommend you check out Werner Puschitz's site, as it's the best source of information for installing Oracle on Redhat.
Cheers, APC

OLAP Analytic Workspace Manager/Worksheet in Oracle 11g...

Hi,
In Oracle Client 10g .v2 the product OLAP Analytic Workspace Manager/Worksheet is included and installed.
However , it is not in Oracle 11g - the Oracle client of this version is included -
http://www.oracle.com/technology/software/index.html
Download page includes:
   - Client
   - Clusterware
   - Examples
   - GatewaysWill it be included in a seperate product Oracle11g Client...or else???
Does anybody know about this....???
Thanks...
Sim

AWM is now installed via the database Client CD, which was the case for 10g as well.
Keith Laker
Oracle EMEA Consulting
OLAP Blog: http://oracleOLAP.blogspot.com/
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
DM Blog: http://oracledmt.blogspot.com/
OWB Blog : http://blogs.oracle.com/warehousebuilder/
OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html

Analytical workspace for Oracle10g to use OLAP

Similar Messages

Maybe you are looking for