Dimension hiearchies in awm

Hi I am using 10g and using awm.
I have a view that populates a dimension.
This has:
YEAR ACCOUNTING_TIME_CODE
FY2008 FY2008
FY2008 Q1.2008
FY2008 Q2.2008
FY2008 Q3.2008
FY2008 Q4.2008
These dimensions have a hiearchy of year and then accounting time code. When I load this into the cube, the cube has problems with it as it seems to get the instance when the year and the accounting time code are the same muddled. I have tried naming the year column something different to the accounting_time_code but its not really acceptable for the end user.
Does anyone know of any way to get around this issue?

Attribute is something related to dimension. They are purely the property of the dimension and not the fact. Now you said the data is not visible in the cube and you are getting 0.00 even with a simplier case(one dimensional cube). There are many causes of the value not shown in the cube and some are mentioned below
1. All records are rejcted in the cube maintaince process. For this you can check olapsys.xml_log_log table and see if you can find any rejected records.
2. There is some breakage in the hierarchy of the dimension. It also prevents data from summing up.
Did you tried with the global sample available on OTN? That should be good starting point for you.
You can check the cube as below to find out it is loaded or not. Consider your one dimensional cube. Find out a member which is existing in the dimension and also has some fact value associated with it.
1. Now limit your dimension to that value like this
lmt <dim name> to '<value>'
For compressed composite cube
2. Now check data in the cube like this
rpr cubename_prt_topvar
for uncompressed cube you should do
rpr cubename_stored
#2 should show the same value which is available in the fact.
Thanks,
Brijesh

Similar Messages

Is it possible to create dimension roles in AWM?

Hi,
Is it possible to create dimension roles in AWM like the way we have in OWB ?
If yes, please direct on the way to do this.
Many thanks in advance for your kind inputs.
Piyush

I think what you need is to use the ALIAS option that is part of the DEFINE DIMENSION statement
DEFINE DIMENSION ALIASOF
The DEFINE DIMENSION ALIASOF command defines a dimension alias for a simple dimension. An alias dimension has the same type and values as its base dimension. Typically, you define an alias dimension when you want to dimension a variable by the same dimension twice.
Additionally, You can use a LIMIT statement to limit alias dimensions and define variables and relations using an alias dimension. However, you cannot maintain an alias dimension directly; instead you maintain its base dimension using MAINTAIN.
Syntax
DEFINE name DIMENSION ALIASOF dimension [TEMP] [AW workspace] [SESSION]
Arguments
name
The name of the object you are defining. For general information about this argument, see the main entry for the DEFINE command.
DIMENSION ALIASOF
If you look at this example if provides a great example of how to use this feature:
http://download.oracle.com/docs/cd/B19306_01/olap.102/b14346/dml_x_decimal006.htm#ABC1485326
But of course the main issue here is how to generate the standard form metadata required to support this feature and make the dimension alias avaliable and visible within AWM. That is the difficult (and I would say impossible) part of the process since this feature is not supported by the AW XML API (at least I don't think it is, you could check the API docs to see if this is supported). if it is not supported then the management of this feature would all have to be controlled via OLAP DML commands (load dimension members etc) but you would still not be able to include it within a cube definition and then maintain that cube using AW XML API.
Does that help?
Keith

In-between joins between 2 dimension levels in AWM

Hi, I have a many-to-many relationship between products and category, as these tables:
PRODUCTS(product_key, name)
CATEGORIES(category_key, name)
PROD_CAT(product_key, category_key, catalog)
I'd need to create a Product dimension with 2 levels, Category -> Product (child level), making this join through the PROD_CAT bridge table... is it possible in AWM?
thanks!

Think about it logically, if you add a key field, how would you lose data, since the primary key is now longer than before? Only if you remove key fields, you might lose data during table adjustment due to duplicate primary keys.
Make sure all other field names remain unchanged.
Try it in dev system first, check the results. For even more confidence, why not download the data first as a backup, "just in case".
Thomas

Dimension create error - AWM

Hello,
I am trying to create dimension in AWM 11.2.0.1.0A and I get the following error:
(Version of Oracle is 11.2.0.1.0)
DPR: cannot create server cursor, Generic in TxsOqDefinitionManager::generic<CommitRoot>
INI: XOQ-01801: CREATE privilege is required for object "DF" in schema "ADW_TEST".,Generic in TxsOqTopLevelObject::lockExclusive
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 me on this error..

*Yes
*Yes
    ADW_TEST
       ADW3_USER
         ALTER SESSION
         CREATE CLUSTER
         CREATE DIMENSION
         CREATE EXTERNAL JOB
         CREATE INDEXTYPE
         CREATE JOB
         CREATE MATERIALIZED VIEW
         CREATE OPERATOR
         CREATE PROCEDURE
         CREATE SEQUENCE
         CREATE SESSION
         CREATE SYNONYM
         CREATE TABLE
         CREATE TRIGGER
         CREATE TYPE
         CREATE VIEW
         DEBUG CONNECT SESSION
       OLAP_USER
         ADVISOR
         ALTER ANY TABLE
         ALTER SESSION
         ANALYZE ANY
         ANALYZE ANY DICTIONARY
         CREATE ANY JOB
         CREATE ANY TABLE
         CREATE ANY VIEW
         CREATE CLUSTER
         CREATE CUBE
         CREATE CUBE BUILD PROCESS
         CREATE CUBE DIMENSION
         CREATE DIMENSION
         CREATE INDEXTYPE
         CREATE JOB
         CREATE MATERIALIZED VIEW
         CREATE MEASURE FOLDER
         CREATE OPERATOR
         CREATE PROCEDURE
         CREATE SEQUENCE
         CREATE SESSION
         CREATE SYNONYM
         CREATE TABLE
         CREATE TRIGGER
         CREATE TYPE
         CREATE VIEW
         DROP ANY TABLE
         DROP ANY VIEW
         EXECUTE ANY PROCEDURE
         GLOBAL QUERY REWRITE
         MANAGE ANY QUEUE
         QUERY REWRITE
         RESUMABLE
         SELECT ANY DICTIONARY
         SELECT ANY TABLE
       SELECT ANY DICTIONARY Edited by: user13372643 on 2010-07-26 04:47
Edited by: user13372643 on 2010-07-26 04:48
Edited by: user13372643 on 2010-07-26 04:49

Where are dimension attributes in AWM - cube viewer?

Hi -
Built my first cube and I am looking at the data with AWM's cube viewer.
I can drill down a hierarchy, but I cannot get at the attributes that were created for the product dimension. The attributes were defined at all levels of the hierarchy.
Does the AWM cube viewer allow you to access the attributes of a dimension?
Thanks,
Frank.

Attribute is something related to dimension. They are purely the property of the dimension and not the fact. Now you said the data is not visible in the cube and you are getting 0.00 even with a simplier case(one dimensional cube). There are many causes of the value not shown in the cube and some are mentioned below
1. All records are rejcted in the cube maintaince process. For this you can check olapsys.xml_log_log table and see if you can find any rejected records.
2. There is some breakage in the hierarchy of the dimension. It also prevents data from summing up.
Did you tried with the global sample available on OTN? That should be good starting point for you.
You can check the cube as below to find out it is loaded or not. Consider your one dimensional cube. Find out a member which is existing in the dimension and also has some fact value associated with it.
1. Now limit your dimension to that value like this
lmt <dim name> to '<value>'
For compressed composite cube
2. Now check data in the cube like this
rpr cubename_prt_topvar
for uncompressed cube you should do
rpr cubename_stored
#2 should show the same value which is available in the fact.
Thanks,
Brijesh

Bug when maintaining dimension data i AWM 10g

Hi,
I have been playing around with AWM 10g since the release and generally I'm very impressed with it. Easy and logical to work with.
I have found what I believe is a bug though. The second time I load data to a dimension through the maintenance wizard and if I check the "Delete all attribute values of the selected dimensions" some dimensions start to behave wrong when trying to drill up and down.
This can be replicated with the global dataset. I create the AW from the "Global Star Mapped" template. The first time I load data to all dimensions and cubes everything works correct. When I run the maintenance wizard again for all dimensions and cubes and check "Delete all attribute values of the selected dimensions" (without actually touching the source data) the result is that the Product and Channel dimensions don't work correct anymore. If I view the data of one of these dimensions it is not possible to drill by clicking the + to the left of the values. When viewing the cube in AWM and trying to drill down in those dimensions the only thing that happens is that the drill arrows disappears.
The Time and Customer dimension are not affected so something must be different between these and the other dimensions. When I tried with one of my own test datasets all the dimensions malfunctions after the second load.
The only way I have found to get it to work again is deleting the affected dimensions and starting again.
Bent

Yep, I confirmed the behavior on my configuration too. Bizarre... I did notice you can still drill if you use the pull-down menu rather than directly clicking on the + to the left of the values.
Typically, a user would select this option if they would like the dimensional attributes in the analytic workspace to match the relational source. For example, your relational source has changed and you do not want these previous values to persist within the analytic workspace. In this case with the GLOBAL sample schema, the data source is the same so something funky is going on.
By the way, if I encounter sudden odd behavior with the View Data feature (random known issue we are working on), I usually disconnect from the database and reconnect. Usually the behavior disappears. However, in this case it does not.
I'll enter this into the bug system. Thanks for all the details. Much appreciated.

Dimension refresh by awm - spoils aggregation?

I have a cube with a few dimensions. Dimensions are simple flat hierarchies. There are no precomputed aggreagtions defined.
When i create new workspace and refresh all dimensions, everything works fine.
But when i want to reload the cube using:
DBMS_AWM.REFRESH_AWDIMENSION D1
DBMS_AWM.REFRESH_AWDIMENSION D2
DBMS_AWM.REFRESH_AWCUBE
something goes wrong.
The D1 Dimension doesn't want to aggregate at the higher levels (there are no precomputed aggregation so the cube should summarize everything on the fly) - the value for a higher levels of that dimension are NULL (other dimensions are ok).
The cube is dimensioned by a composite with all dimensions within it.
When i try to inspect where the problem is i checked:
-in the composite there are all combinations of the lowest level members (and that is what i expected_.
-there are no any higher level members at all in the composite (as i expected)
-when i change refresh order then the problem occurs in the second dimension (always in the first refreshed dimension in a batch)
-refreshing the same dimension twice almost resolved problem.
What could be the problem?
Why refreshing dimension causes that cube forgets how to aggregate that dimension?
Raf
PS: i work with 9iR2

Could it be something with the fact i use AGGMAP with the AGGINDEX set to NO?
I thought it only matters when using models.
But i'm not using models.
Im just trying to use:
SHOW measure_formula
where measure_formula is AGGREGATE function
When i changed AGGINDEX to YES - the above SHOW command executes for ages... (the cube isn't big - abut 300 000 cells in a composite and about 10 dimensions)
Raf

AWM Set Aggregation Operator based on Measure instead of Dimension?

Is there anyway to base an operator of a measure over a dimension on the measure instead of the dimension? In AWM, I notice that each Measure has an Aggregation tab that summarizes its operator over each dimension, but it is greyed out. The way I'd like it to work is to have one Measure be summed over the Dimensions, while another Measure is averaged over the Dimensions.

Found my answer: Not only do I need to make sure my cube is not compressed, but I also need to select "Override the Aggregation specification of the cube" under each Measure's General tab. This results in the contents of the Aggregation tab no longer being grayed out.

Drilling, Hierarchies, Dimensions, AWM

Hi,
I'm new to OLAP, cubes, star schemas...
I'm using Analytic Workspace Manager Version 10.2.0.1.0.
Is it possible to drill down without creating hierachies ?
Once hierarchies are created and i want to do the mapping, it seems that every level needs to have a key, am I wrong ?
Therefore, if I take a Time table that I have to map, I should have this king of physical structure :
year_id, year_desc,
quarter_id, quarter_desc,
month_id, month_desc.
Another example, if I have a Product table, I should have this kind of physical structure :
product_id, product_desc,
category_id, category_desc...
Thank you for your help.

The dimension members have to be unique in OLAP.
You can concatenate level id with the dimension member to make dimension members unique at each level of OLAP dimension. This is a common practice.
Lets say one row in your relational TIME dimension table is:
year_id = 1
year_desc = '2011'
quarter_id = 1
quarter_desc = 'Q1-2011'
month_id = 1
month_desc = 'Jan-2011'
and you level ids in olap are defined as 'YR_LVL', 'QTR_LVL', MTH_LVL'
This can be loaded into your OLAP time dimension as 3 time dimension members:
time = 'YR_LVL_1'
time_long_description = '2011'
time = 'QTR_LVL_1'
time_long_description = 'Q1-2011'
time = 'MTH_LVL_1'
time_long_description = 'Jan-2011'
You can either do the concatenation setting in OLAP time dimension definition in AWM (without making any change in relational table or view)
or in your source sql view that is "mapped" to OLAP time dimension.

Oracle DB 10g and BI Discoverer for OLAP - Dimension Attributes

Hi,
We are using Oracle Database 10g release 1 with partitioning, data mining and OLAP options and Analytic Workspace Manager 10.2.0.1.0A to create the multidimensional objects. For the user dimensions created using AWM we have custom attributes like HireDate, StartDate, Sales Personnel Role etc., For reporting purposes we are using Discoverer for OLAP. In this Discoverer version, I don't see an explicit provision to drag these attributes onto the worksheet. We are only able to filter based on these attributes and capture the measures...
Can someone throw light on this? Also, if there is a possibility to drag these attributes onto the worksheet can that be expounded?
Thanks in advance!

Again this depends on what you are trying to achieve. If you define an attribute against a dimension it takes very little space as it is not directly connected to a cube and so no data is stored against that attribute.
If, however, you have a 4D revenue cube (product, geography, channel, time) with products attributes COLOR and PACK SIZE and you want to view revenue additionally borken-out by COLOR and PACK SIZE as well as the other four dimensions then your schema will require additional storage space. However, 10g compressed cubes and sparsity options do help to manage the explosion of data points as the number of dimensions increases. This should allow you to easily add attributes as dimensions into your cube.
One thing to remember is that most users start to struggle when confronted with more than 9 dimensions. So although Oracle OLAP can create extremely large dimensional models, users prefer their cubes to have 9 or fewer dimensions.
Hope this helps,
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 while populating Dimension

I am unable to populate the dimension I am getting the below error message
INI: XOQ-01711: Aggregation path for hierarchies on a dimension "ACCOUNT" is inconsistent, Generic at TxsOqStdFormCommand::execute
I am creating a Account Dim with the following hierarchy and Levels
All_Accounts
Account_Type
Account_Group
Account_no
Regards
Ishaq

Please find the details of the dimension
Environment Details :- AWM (11.1.0.7 B).
Data Base 11.1.0.7
Details Regarding the Dimension
Cost Center Dim
Levels
ALL_Cost_centers
Cost_Center_Group
Cost_Center_Sub_Group
Cost_Center
Hierarchy
Cost_Center_Hier
ALL_Cost_centers
Cost_Center_Group
Cost_Center_Sub_Group
Cost_Center
Cost center Attribute created and last level is checked (the lowest level)
Attribute Mappings
Hierarchy
Account_Hier
All_Cost_Centers
Member --> 'ALL_COST_CENTERS'
Long Desc --> 'All Cost Centers'
Short Desc --> 'All Cost Centers'
Cost_Center_Group
Member --> Cost_Center_Dim.Code_B_Group
Long Desc --> Cost_Center_Dim.Code_B_Group
Short Desc --> Cost_Center_Dim.Code_B_Group
Cost_Center_Sub_Group
Member --> Cost_Center_Dim.Code_B_Sub_Group
Long Desc --> Cost_Center_Dim.Code_B_Sub_Group
Short Desc --> Cost_Center_Dim.Code_B_Sub_Group
Cost_Center_No
Member --> Cost_Center_Dim.Cost_B_Key
Long Desc --> Cost_Center_Dim.Code_B_Descrip
Short Desc --> Cost_Center_Dim.Code_B_Descrip
Cost_Center_No --> Cost_Center_Dim.Code_B
Code_B Table Data
CODE_B_GROUP CODE_B_SUB_GROUP CODE_B_KEY CODE_B CODE_B_DESCRIP
PRODUCTION 1 C0010 PRODUCTION
PRODUCTION PRODUCTION 2 C0011 PROCESS/RECOMBINING
PRODUCTION ENGINEERING 11 C0020 ENGINEERING
PRODUCTION MATERIAL MANAGET 20 C0030 MATERIAL MANAGEMEN
SALES 27 C0050 SALES & DISTRIBUTION
SALES SALES 28 C0055 SALES
SALES SALES 29 C0056 SALES & MARKETING - GENERAL - H/O
SALES MARKETING 33 C0060 MARKETING
FINANCE 40 C0080 FINANCE & ADMINISTRATION
FINANCE ADMINISTRATION 44 C0100 ADMINISTRATION
FINANCE IT 51 C0110 INFORMATION TECHNOLOGY (IT)
I have also checked metalink it points to the below bug 7606712 - DIMENSION MAINTENANCE ERRORS OUT WITH MULTIPLE HIERARCHIES UNDER 11G

Is there possibility to add dimension value into hierarchy using dml or spl

1 Is there possibility to add dimension value into hierarchy using dml or spl?
If such possibility exists how to do that.
2 Is it possible to sort dimension values inside one branch of the hierarchy?

What version of OLAP are you using and how did you create your AW (e.g., AWM)?
Assuming that you're used either AWM or the Java API for AWs in 10g, there isn't an OLAP DML for adding a dimension member to a dimension (and have all the meta data kept in sync); you must load dimension members using AWM the Java API for AWs.
So, make your changes in the the dimension table and process that table.
For sorting, you can add a sort attribute to the dimension. Add the sort attribute to the model, indicate that it's used for sorting, add the sort attribute to your dimension table and maintain the dimension.

AWM mapping : "SCHEMA.TABLE_NAME.COLUMN" invalid

Hi,
I have Views in my database that I use as dimensions .
In AWM, I create dimensions, I try to map with my views ... And I get the following error :
*"SCHEMA.TABLE_NAME.COLUMN" invalid*
I chekked the database, everything seems to be okey ! And I can't find a clue
Any Idea ? Thanks all !

Are you able to query from the database View without the error, and as the same login you use in AWM? Is the View valid/compiled?
Edited by: Dave O on Dec 18, 2012 4:59 PM

OWB and AWM for loading DWH

Hello,
I am on the following version:
DB: Oracle 10.2.0.1 (both source DB and target DWH)
OWB : 10.2.0.1
AWM : 10.2.0.1
I have the following process:
From the source DB I use OWB to load relational dimensions (SCD 2). I use AWM to load data from these dimensional tables to a Analytic workspace. I use OWB because I need to track changes (SCD) and use AWM because OWB currently does not support Parent-Child dimensions where as AWM supports. I would love to load AW from OWB directly if it had parent-child support.
My question is:
All the load should be trigger-based, When my process (SQL) completes on the source table the OWB process of loading the relational dimension should start which is not a problem, I using the run_owb_code.sql for this. once the run_owb_code is complete, I want the AWM's maintain data process to start. I don't know how to do it. I tried saving the maintenance task to script and tried executing it, it doesn't seem to work. I don't want to AWM and run cube maintenance every time the cube needs to be refreshed.
Please note I don't have a cube in the relation world. My fact(cube) in the AW is a direct load from a table (as I don't need SCD here) so basically use OWB just to load the dimensions alone. AWM creates the actual cube with the dimension tables loaded using OWB and the fact table from source, So I don't think I can use the "dbms_awm.refresh_awcube(...".
Can somebody please help me in automating this load process
Thanks a lot in advance!
Maruthi

Hello,
I am sorry, after some research, I came across this post
Re: Cube and dimension refresh proactively
As per the above post, the script that is generated using AWM will work if the AW is not attached by any user.
I detached the AW and executed the script and the cube was populated with data.
Thanks,
Maruthi

Deleting dimension members

We have an AW with cubes refreshing every day. Fast solve of these cubes with incremental set of data finishes usually within an hour or two.
Our recent requirement needs for us to remove some old facts as well as a few dimension members. The facts can be cleared but we noticed that deleting dimension members (using synch load) is causing a full cube solve due to changed relations. With the amount of data existing in this AW, full solve takes about 2 days to complete. Deleting dimension members for which we never ever loaded any facts also causes the same result as above.
I was wondering if there is any way we can delete these dimension members without triggering a full cube solve.
Another question is if it is possible to update dimension primary keys inside of the AW?
Any help is really appreciated.
Database Version 11.2.0.3

These types of questions have been answered in the past by David Greenfield.
There are two ways to delete a dimension member through commands.
(1). OLAP dml command "REMOVE_DIMENSION_MEMBER" explained here: http://docs.oracle.com/cd/E11882_01/olap.112/e17122/dml_commands_2042.htm#OLADM2692
OR
(2). dbms_cube.build command:
exec dbms_cube.build(q'! "TIME" USING (DELETE FROM DIMENSION WHERE MEMBER = 'APR-2011') !');
Take a look at this old post, where David Greenfield explained it.
https://forums.oracle.com/message/9426946
There is no way to rename a dimension member in a standard-form analytical workspace. There is "MAINTAIN RENAME" olap dml command, but it will not work with dimensions created through AWM. You can add the new dimension member, then copy cube data associated with old/existing member to the new member and then delete the old member.
For cube copy data example, take a look at these old (15-Feb-2011, 16-Feb-2011 and 17-Feb-2011) posts by David Greenfield:
https://forums.oracle.com/thread/2176409

Dimension hiearchies in awm

Similar Messages

Maybe you are looking for