Creating Flat Dimensions in AWM

Hi,
We have a proposed cube structure with 8 dimensions (apart from the TIME dimension) as follows:
3 Dimensions have a Level-Based Hierarchy
2 Dimensions have a Value-Based Hierarchy
3 Dimensions are flat with no levels or hierarchy.
We are using Oracle Analytic Workspace Manager v10.2.0.3.0A for formulating the cube structure.
We want to introduce a top level “All” column in all the dimensions so as to facilitate analysis of data by eliminating the dimension itself (by selecting its “all” level). Inclusion of such a top level “All” level seems intuitive for Level based and value based hierarchy as we can just introduce the new level.
However, we are not sure of how we can create a “flat” dimension and also have the top level “all” column in it by using AWM. Any insights on the process of creating a flat dimension in AWM would be much appreciated.
Thanks,
Piyush

I am not sure what the problem is? You simply create a dimension with two levels:
- Top level
- Base level
Assign an 'All Members" description to the top level and all all other members are assigned to the base level.
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/

Similar Messages

Error while creating user dimension in awm

Hi,
I am new to awm. I am trying to create a dimension in my workspace, but i receive an error after i click 'create'. When i check the detailed error, i think its something to do with the OLAP_TABLE. Please find the error message below,
===================================================
Your metadata changes have been saved, with the following errors
Invalid Metadata Objects:
Invalid Object "TAN.TICKERSYMBOL": "CREATE OR REPLACE VIEW "TAN"."TICKERSYMBOL_VIEW" AS    SELECT      "DIM_KEY",      "LEVEL_NAME",      "MEMBER_TYPE",      "DIM_ORDER",      "LONG_DESCRIPTION",      "SHORT_DESCRIPTION"   FROM TABLE(CUBE_TABLE('"TAN"."TICKERSYMBOL"') )
ORA-00902: invalid datatype "
====================================================
Please advise.

Which version of the database (not AWM!) are you using? (e.g. 11.2.0.3)
My guess is that there is a problem with your OLAP installation and that you will need to open a service request to get it resolved. But the following may help us to track down the problem.
alter session set events='902 trace name errorstack';
alter session set tracefile_identifier=OLAP;
SELECT
   "DIM_KEY",
   "LEVEL_NAME",
   "MEMBER_TYPE",
   "DIM_ORDER",
   "LONG_DESCRIPTION",
   "SHORT_DESCRIPTION"
FROM TABLE(CUBE_TABLE('"TAN"."TICKERSYMBOL"') )
Once you have run this (in a single session), look for a trace file containing the word OLAP in its file name. It should contain a stack trace that will tell us where the ORA-00902 is being raised. The trace file will be long, but the interesting part begins like this:
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
skdstdst()+29        call     kgdsdst()            7FFFADE14590 ? 000000000 ?
                                                   7FFFADDF6E50 ? 7FFFADDF6F68 ?
                                                   7FFFADE14C48 ? 7FFFADE14540 ?
ksedst()+112         call     skdstdst()           7FFFADE14590 ? 000000000 ?
If you can find this, please copy it in reply.

Error when I try to create dimension with AWM 11.1.0.7.0B

hello, I have installed Analytic workspace manager 11g, and I have created a connection to an oracle database, but when I try to create a dimension 2 errors appears:
1.the dimension must have at least one hierarchy
2.the dimension must have at least a level
i use sys as sysdba , as a user in AWM to resolve the problem of priviliege.plz any suggestions !!??

What version of the database and AWM are you using? The failure on the <Classification> tag suggests that you may have database version 11.1.0.6. If so, then I recommend that you upgrade the server to at least version 11.1.0.7.

Error when I try to create dimension with AWM 11g

hello, I have installed Analytic workspace manager 11g, and I have created a connection to an oracle database, but when I try to create a dimension 2 errors appears by alternate :
1/
La transaction ne peut pas être validée : "Erreur sur le serveur
Classe d'erreurs : Echec dExpress
Descriptions des erreurs du serveur :
DPR : Création impossible du curseur de serveur, Générique à TxsOqDefinitionManager::generic<CommitRoot>
INI : Impossible d'analyser la chaîne XML envoyée par le client au serveur, Générique à XML Parser Errors:
Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
Error processing tag: Classification:
Error returned by xsOqXmlParserExecute.
2/
Des erreurs se sont produites lors de lanalyse XML
<Ligne 3, Colonne 15> : <Line 3, Column 15>: XML-20210: (Fatal Error) Unexpected EOF.
help me stp.

Hi,
This question is missplaced in this forum.
Please ask this question again, the appropriate forum is found here:
OLAP
(OLAP forum)
thanks
Jorge

Encounter error after adding an attribute to a new dimension in AWM.

After I added an attribute to a new dimension, I encountered the error as below.
I also cannot read the metadata from Jdeveloper after I create a cube using AWM.
Please kindly help!!
BI Beans Diagnostics(v1.0.2.0) 2005/9/15
===============================================================================
JDEV_ORACLE_HOME .......................... = C:\jdev1012_base
JAVA_HOME ................................. = c:\j2sdk1.4.2_02
JDeveloper version ........................ = 10.1.2.0.0.1811
BI Beans release description .............. = BI Beans 10.1.2 Production Release
BI Beans component number ................. = 10.1.2.52.0
BI Beans internal version ................. = 3.2.1.0.13
Connect to database ....................... = Successful
JDBC driver version ....................... = 10.1.0.3.0
JDBC JAR file location .................... = C:\jdev1012_base\jdbc\lib
Database version .......................... = 10.2.0.1.0
OLAP Catalog version ...................... = 10.2.0.1.0
OLAP AW Engine version .................... = 10.2.0.1.0
OLAP API Server version ................... = 10.2.0.1.0
BI Beans Catalog version .................. = N/A; not installed in BI_TEST
OLAP API JAR file version ................. = "10.1.0.2.0"
OLAP API JAR file location ................ = C:\jdev1012_base\jdev\lib\ext
Load OLAP API metadata .................... = Successful
java.lang.NullPointerException
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.setDimAttributes(MDMMetadataDriverImpl_92.java:1733)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.getChildren(MDMMetadataDriverImpl_92.java:197)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.addChildren(MDMMetadataDriverImpl_92.java:2687)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92.fillOlapObjectModel(MDMMetadataDriverImpl_92.java:2571)
at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverIm
pl_92$LoadOlapObjectModel.run(MDMMetadataDriverImpl_92.java:3013)

I would post this on the OLAP forum as they should be able to help you diagnose this problem. The OLAP forum can be found at the following link:
OLAP
There is not much detail in your log, but I suspect that your OLAP mappings are incomplete or the maintenance of your dimension to load the new attribute data somehow failed. I would check the OLAP AWM build logs for more information.
Thanks
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Error when building dimension using AWM

Hi Gurus,
I am trying to build a dimension using AWM 11.1.0.7.0B Standalone. My Database version is _11.1.0.6.0._
The moment i start to create a New Dimension, i get the below error.
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::g
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
Error processing tag: Classification:
Error returned by xsOqXmlParserExecute.
+"+
+at oracle.olap.awm.dataobject.dialog.PropertyViewer.doCreateAction(Unknown Source)+
+at oracle.olap.awm.dataobject.dialog.CreateDialogHostActionThread.doAction(Unknown Source)+
+at oracle.olap.awm.ui.dialog.ThreadedDialogActionThread.run(Unknown Source)+
Please help!!!!!
+*Regards,*+
+*Ravi R*+

The initial release of OLAP in 11.1.0.6 was not stable. Please upgrade to at least database 11.1.0.7, and preferably 11.2.0.3. If you move to 11.1.0.7, then you should apply the "OLAP D Patch", #9147749. See the OLAP certification page for more details.
http://www.oracle.com/technetwork/database/options/olap/olap-certification-092987.html

Trying to create a Dimension returns ORA-36830 Error.

Hi All,
I am running OLAP on 11.1.0.7 DB Instance on AIX 6.1. Interaction is performed via AWM 11.1.0.7B.
I have created a user 'OLAPAW' and assigned all privileges as per OLAP Users Guide but for some unknown reason receive the following error when trying to create a Dimension :
Your metadata changes have been saved, with the following errors, CREATE OR REPLACE VIEW "OLAPAW"."BRAND_VIEW" AS
ORA-36830: Object OLAPAW.BRAND does not exist
The role 'OLAP_USER' is already defined as a default role for 'OLAPAW' user.
Regards,
Harry.

In addition to granting role OLAP_USER, can you confirm if you also have:
create session, create dimension, create materialized view, advisor, olap_xs_admin

How to Create a Dimension Table in OBIEE11g

Hello,
Chapter 9, page 221(if pdf) of the Build Repository manual of OBIEE 11g explains following.
Creating Dimensions in Level-Based Hierarchies
After creating a dimension, each dimension can be associated with attributes
(columns) from one or more logical dimension tables and level-based measures from
logical fact tables. After you associate logical columns with a dimension level, the
tables in which these columns exist appear in the Tables tab of the Dimension dialog.
To create a dimension with a level-based hierarchy:
1. In the Business Model and Mapping layer of the Administration Tool, right-click a
business model and select New Object > Logical Dimension > Dimension with
Level-Based Hierarchy.
Note that this option is only available when there is at least one dimension table
that has no dimension associated with it.I am still learning OBIEE, and I can not see the dimension menu item as per point 1 becuse i do not have dimension table associated with it. All I have done at this point is to create logical tables based on few physical tables in physical layer.
How do I create Dimension Tables? using BI Admin tool?
Thanks,R

Hi Rich,
If you are new to Oracle BI, you would better start with the Oracle Learning Library; http://apex.oracle.com/pls/apex/f?p=9830:41:0::NO:RIR:IR_PRODUCT,IR_PRODUCT_SUITE,IR_PRODUCT_COMPONENT,IR_RELEASE,IR_TYPE,IRC_ROWFILTER,IR_FUNCTIONAL_CATEGORY:,BI,,,,,
You create dimensions based on your logical tables. In a plain star-schema you would have one logical fact table and at least one or more logical dimension tabes attached (joined) to the fact table. Just follow the documentation and you would be good to go.
Good Luck,
Daan Bakboord
http://obibb.wordpress.com

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Duplicate attribute key found when creating a dimension

Good Afternoon,
I created a cube with dimesnions and all is working fine. I created three dimension ZONE,BLOCK and STREET and these are reltated to the FACT table and all is well. But i was thinking since these 3 dimensions are related and coming from the same table, why
not just create one dimension with ZONE as the primary key and the heirarchy as zone>block>streetname. In the DSV i created a named query.
SELECT DISTINCT ZONE, BLOCK, STREET
FROM dbo.MYTABLE
group by zone,block,street
order by zone,block,street
Please see the sample dataset as well, where when i process the DIMENSION fails with an error that the "Duplicate attribute key was found, column name:Zone, value:1). I know zone and also the other two columns when processed are repeated more than once
and hence this, is there a way to get what i want.
ZONE BLOCK STREET
1 0 Chesapeake
1 0 East Market
1 0 East Maryland
1 0 East Washington
1 0 North Capital
1 0 North Delaware
1 0 North Illinois
1 0 North Meridian
1 0 North Penn
1 0 South Delaware
1 0 South Illinois
1 0 South Meridian
1 0 South Penn
1 0 Virginia
1 0 West Georgia
1 0 West Jackson
1 0 West Market
1 0 West Maryland
1 0 West New York
1 0 West Washington
1 100 East Washington
1 100 East Market
1 100 East Maryland
1 100 East New York
1 100 East Ohio
1 100 East Washington
1 100 North Alabama
1 100 North Capitol
Thanks
SV

Thanks Richard and SS. This is what i did.
1) In the DSV i created a new named query, the same one i used.
2) Set Primary Key on Street.
3) Created a dimension STG_ZBS_DIM and while creating the heirarchy , i draged and dropped the fileds in the following order (zone>block>street).
4) Tired to process , but getting the same error, except this time at the street level.
What else i did was changed the primary key back to Zone, went into the attribute relations and set the relation from Zone to Block and then Block to Street, saved and processed and this time i got the error at the block level :-(
Thanks
SV

Can I create a DIMENSION object mappign without a Dimension table?

I understand how I can create a dimension object and it's associated table. However, can I map my enterprise data directly to the dimension object itself and skip the loading of the dimension table? The enterprise data for most of my reporting warehouse for the greater part is fairly simple and requires only joins to some reference data.

Matthew,
Like you stated, the dimension object in OWB will generate scripts for two object types. The first is a dimension object and the second is a table. In the dimension object the hierarchical structure(s) (meta data) is stored and the table stores the data. So you always have to load your enterprise data into the table.
Hope this helps.
With kind regards,
Bas Roelands

Can We Create Custom Dimension ontop of BI Infocube

Hello Guys,
I need help on below questions. i appreciate all your help in advance.
Can we create Custom Dimension ontop of SAP BI Infocube ? Does it support all functions like SQL and ORACLE database supports ? Can any body have list what kind of function it supports ? Does it support If..else ..if condition ??
Ex. If Account = 410000 and Profit center inlist 100,200,500,999 Then u201CSales Revenueu201D else ifu2026.etc., Can we write this kind of condition in Universe on top of SAP BI Infocube ?
Regards,
Komik Shah

Hi,
here are some examples of what you can create:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0a45246-ce76-2b10-e688-f5c8206203eb
Ingo

OWB 10g: Creating a dimension: error on hierarchy

Hi there,
i've created a very simple dimension, alike the channel dimension of the sh-samples.
However, when i validate my dimension, i get the error:
--> VLD-0350: In a hierarchy <name>, level relationship binding between parent level "total" and child level "channel" does not exist.
--> Within a hierary a level relationship between levels must be created using the surrogate key column of the parent.
I've created the dimension now several times but one way or the other this error always pops up. I've recreated the hierarchy, still the problem remains. Anybody has a clue how to create this binding?
Any help is very much appreciated!
Cheers
Sandra

Thanks for the quick reply, I have a Surrogate key on every level.
*** Problem solved ***, but still a mystery... I actually quite OWB
came back and everything was validating correctly...
Do any of you have such a problem? Things not working, exit come back
in an it works???
Here the problems that I had before the restart...
Here's a quick overview of what I have in the Data Object Editor:
Relational Tab:
I have my "source" table were my data is to fill the Dimension. Validates successfully.
Dimensional Tab:
I have my CUSTOMER_DIM, I did the Bind All I have 2 errors now:
VLD-0345 Level Attribute CUSTOMER ID is not bound to a column in
table or updateble view.
VLD-0350: In a hierarchy STANARD, level relationship binding between parent level
COUNTRY_HEIR and child level BASE_HIER does not exist. (Each level attribute must be bound to a column in a table or updateable view)
In the Object Editor, Dimensional Attributes, I have CUSTOMER_ID that is a Surrogate. In the "Choose the sequence that will populate the Dimension and Surrogate Keys:"
I have selected CUSTOMER_DIM_SEQ. (Within a hierarchy a level relationship between levels must be created using the surrogate key column of the parent.)
Thanks
Eric

Creating a dimension with Subtable type is better or maintaining heriarchy?

Hi BPC Gurus,
           In legacy system, client was having many GL items. Now with the implemntation of SAP, the FI has maintained those GL items as one group only. To be specific enough following is the example:
             Legacy system
Repairs of Buildings(Material)
Repairs of Micro Hydel(Material)
Repairs of Distribution(Material)
        SAP system
R/M of Materials.
In BPC, the client wants the planning at the line item level, whereas with SAP it can be planned at group level only. So to maintain the planning at line item level I have to take data from SAP-PM and FI. Now my question is can I have the line items in heirarchy way or I have to create a dimension of subtable type and maintain members in it.
SAP BPC P_ACCT(heirarchy)
R/M of Materials           ( GL Item - SAP FI)
      Buildings                                 ( SAP PM )
      Micro hydel                             ( SAP PM )
      Distribution.                             ( SAP PM)
Regards
Kumar MG
Edited by: KumarMG on Apr 15, 2011 12:10 PM

Hi Kumar,
Creating a Subtable type's Dimension will not solve the problem because that is the only type of dimension.
Hierarchy is the best solution for these type of situation.
Regards,
Anil

Is convenient to create a dimension table in this situation...?

I have Oracle 9.2.0.5
I have a table âFACT_OPERATIONSâ with 10.000.000 of records and these fields:
TABLE âFACT_OPERATIONSâ
Category VARCHAR2(40) (PK)
Type VARCHAR2(35) (PK)
Source VARCHAR2(50) (PK)
Description VARCHAR2(100) (PK)
CUSTOMER_ID NUMBER(6) (PK)
MODEL_ID NUMBER(6) (PK)
STATE_ID NUMBER(6) (PK)
TIME_ID NUMBER(8) (PK)
Quantity (PK)
I charge it from multiple fact_tables with a Merge Statement
I have the Dimensions tables: Dim_Customers, Dim_Models, Dim_States and Dim_Time.
The field Source have the name of the Fact_Table where I charge the information
The field Type is the father of the field Source.
and the field Category is father of the field Type.
For example:
Category: EVENT
Type: SALES
Source: SALES_VI_ZU
Category: EVENT
Type: SALES
Source: SALES_VI_AU
Category: EVENT
Type: MOVS
Source: MOV_SALES
The question is:
Is convenient to improve the query performance I create the dimension Source (It will contain the fields Category, Type, Source and so on). Then, I put in the FACT_OPERATIONS the field SOURCE_ID and delete the fields Category, Type and Source.
Now I do for example these queries for example:
select Category, Type, Source, count(*)
from FACT_OPERATIONS
group by Category, Type, Source
or
select *
from FACT_OPERATIONS
where CATEGORY = âEVENTâ
or
select *
from FACT_OPERATIONS
where TYPE = âSALESâ and SOURCE = âSALES_VI_AUâ
Â¿I will improve the performance with these changes or is the same?
Thanks!

Your queries would probably run more slowly if you moved the category and type to a dimension table, but having said that it is still the correct thing to do. If you need faster performance for those three queries then it would be apropriate to use a bitmap join index, or to create a materialized view to aggregate the data -- in fact query 1 could be satisfied very quickly using a materialized view.

Creating Flat Dimensions in AWM

Similar Messages

Maybe you are looking for