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

Similar Messages

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.

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

Error in using AWM "Create Aggregation Plan Wizard"

HI,
I have 9205 database with OLAP option running on Linux ES3. I created 2 cubes & 7 dimensions using OWB and deployed it using the OWB Bridge. From there, I created AW & enabled the cubes using AWM. It also loaded data into dimensions and cube in AW and everything is visible in JDeveloper. Then I tried to create an aggregation plan for one of the cubes using the wizard & it gave me following error at the GET_LEVEL step. It is disconnecting the AW from AWM upon getting this error.
Can someone help?
regards
Suresh
java.sql.SQLException: ORA-03113: end-of-file on communication channel
at oracle.olap.awm.util.jdbc.SQLWrapper.execute(SQLWrapper.java:225)
at oracle.olap.awm.businessobject.aw.LevelBO.getOrderedLevelsForDimensionInAW(LevelBO.java:199)
at oracle.olap.awm.wizard.aggplanner.AggPlanSelectLevelPanel.initialiseDimensionLevelHashtable(AggPlanSelectLevelPanel.java:210)
at oracle.olap.awm.wizard.aggplanner.AggPlanSelectLevel.onEnterPage(AggPlanSelectLevel.java:125)
at oracle.olap.awm.ui.wizard.Wizard.wizardSelectionChanged(Wizard.java:157)
at oracle.bali.ewt.wizard.BaseWizard.processWizardEvent(Unknown Source)
at oracle.bali.ewt.wizard.BaseWizard.processEventImpl(Unknown Source)
at oracle.bali.ewt.LWComponent.processEvent(Unknown Source)
at oracle.bali.ewt.wizard.BaseWizard.selectPage(Unknown Source)
at oracle.bali.ewt.wizard.BaseWizard.doNext(Unknown Source)
at oracle.bali.ewt.wizard.BaseWizard$Action.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.Dialog.show(Unknown Source)
at java.awt.Component.show(Unknown Source)
at java.awt.Component.setVisible(Unknown Source)
at oracle.bali.ewt.wizard.WizardDialog.runDialog(Unknown Source)
at oracle.olap.awm.ui.wizard.Wizard.showInDialog(Wizard.java:95)
at oracle.olap.awm.wizard.aggplanner.AggPlanWizard.showInDialog(AggPlanWizard.java:129)
at oracle.olap.awm.app.AwmFrame.showAggPlanWizard(AwmFrame.java:1263)
at oracle.olap.awm.navigator.node.olapcatalog.AwCubeNode.actionPerformed(AwCubeNode.java:164)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

Whenever you see "end-of-file on communications file" it means something bad happened (A crash) and a trace file should have been generated in your dump directory. You'll need to open a TAR with that trace file to get development to look at it.

Dimension refresh fails with ORA-34034

Hi All,
We are currently experiencing a strange behaviour when we refresh one of our dimensions.
One of our dimensions is refreshed daily and has been working fine until yesterday when it fails with this error:
<ERROR>
<![CDATA[
XOQ-01601: error while loading data for Cube Dimension "OLAPUSER.PROD" into the analytic workspace
ORA-34034: 742 is already a value of SALES!PROD_CLASS_SURROGATE.
XOQ-01600: OLAP DML error while executing DML "SYS.AWXML!R11_LOAD_DIM"]]>>
</ERROR>
The PROD dimension is a balanced hierarchy and we've checked theren't any duplicate keys at every level of the hierarchy.
Any idea?
Thanks

I have seen this (in 11.1.0.7, I believe) when the metadata cache ("kgl") gets out of synch with the data dictionary. Specifically there is a flag that determines if prefixes get added to dimension members ("use surrogates" in AWM terms) that becomes false instead of true. If you look at the generated SQL in the OUTPUT column of the CUBE_BUILD_LOG you may find that sometimes a prefix is added to dimension members (e.g. "LEAF_LEVEL_" || dim_table.leaf_column) and othertimes it is not (e.g. just dim_table.leaf_column). A workaround if this is the case may be to execute the following (as dba) before building the dimension.
alter system flush shared_pool;

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

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

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.

Problem refreshing AW Dimension

I am trying to create an analytic workspace and I am using the AWM wizard for this job.
I want to build a cube that is based only on two dimensions. To this end, I have created OLAP catalog metadata for the two dimensions and the cube via OEM successfully.
Selecting on ALL_OLAP2_DIMENSIONS and ALL_OLAP2_CUBES returns that all objects are valid.
However when the AWM wizard runs I get the following error
when DBMS_AWM.REFRESH_AWDIMENSION is called for the first dimension:
Processing Refreshing Dimension : TC6ACCOUNT_DIM
Error Message from Server = Problem refreshing dimension:
TC6ACCOUNT_DIM
Failed to Build(Refresh) OLAPDUN.TESTCUBE6_AW Analytic Workspace. Error Validating Dimension Mappings TC6ACCOUNT_DIM.DIMENSION. Key Expression DUNMART.ACCOUNT_DIM.ACCNT_ID for Mapping Group TC6ACCOUNT_DIM.MARKET_SEGMENT_H.ACCOUNT_DIM_L.DUNMART_ACCOUNT_DIM_TC6ACCOUNT_DIM_MARKET_SEGMENT_H_ACCOUNT_DIM_L.DIMENSIONMAPGROUP, Level TC6ACCOUNT_DIM.ACCOUNT_DIM_L.LEVEL, Hierarchy TC6ACCOUNT_DIM.MARKET_SEGMENT_H.HIERARCHY is Incorrectly Mapped to RDBMS.
I dont know what I'm doing wrong. If there was an error in the hierarchy, then why do I get a valid state for these objects from the ALL_OLAP2 views?
I would appreciate it if anyone could help me out!
Nikos

Thanks Sharon for the tip. I have applied patch 10.1.0.3E and the dimensions were refreshed successfully.
Unfortunately now another error was raised during the cube refreshing.
More specifically I got the following error during the call:
execute DBMS_AWM.REFRESH_AWCUBE('OLAPDUN', 'TESTCUBE7', 'TC7TESTCUBE7', 'TESTThu Mar 10 16:10:19 EET 2005');
Error Message from Server = Problem getting dimensions for cube:
DUNMART
TESTCUBE7
Aggregation Definition TC7TESTCUBE7.TC7TESTCUBE7_DA.AGGREGATIONDEFINITION is Invalid. Aggregation Definition TC7TESTCUBE7.TC7TESTCUBE7_DA.AGGREGATIONDEFINITION can not be Compiled.
(AW$XML) AW$XML
In SYS.AWXML!__XML_HANDLE_ERROR PROGRAM:
SqlException = ORA-06502: PL/SQL: numeric or value error string
ORA-06512: in "OLAPSYS.DBMS_AWM", line 1213
ORA-06512: in line 1
Error Code = 6502
Sql State = 65000
All the cubes could not be added to the Analytic Workspace TESTCUBE7;
The following cubes could not be added : TESTCUBE7
java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error string
ORA-06512: in "OLAPSYS.DBMS_AWM", line 1213
ORA-06512: in line 1
Tidying Up
Failed to create the analytic workspace
Are there any suggestions for this error?
thanks,
Nikos

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.

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

Different aggregation operator for two measures in single cube

Hi,
I have three measures age_month and age_year,pages for which aggregation operator should be like this
for age_month and age_year
time - max
account - sum
sales org - sum
for pages
time - sum
account - sum
sales org - sum
I am creating MOLAP cube in OWB and deploying to AWM. I can create above structure in OWB but when I deploy it to AWM I see that for all the dimensions and all the measures aggregation operator as sum. Off course I can change the aggregation operator at cube level but it make changes to all underlying measures too.
Also I can see in XML of the cube and see the operator for two measures is as max but UI shows as sum. After load also I am seeing in report it is calculating as sum instead of max along time dimension.
Any help would be highly appreciated.
Thanks
Brijesh

If you have an existing cube (already defined and aggregation setup) then modifying the aggregation behavior like changing order of dimensions/aggregation operators is not very robust (likely to fail due to inability of internal objects to sync up to modified defintion). Its always better to take a backup of cube definition and drop/rebuild a fresh cube with new dim order/agg operators.
How can you have a compressed cube and also set the aggregation property per dimension?
I was under the impression that if it is a compressed cube, then not only is there a restriction that all measures have same aggregation properties (defined at cube level) but also the aggregation behavior defined at cube level should use the same operator (note: any one operator out of sum or max or min) for all dimensions.
Edited by: Shankar S. on Dec 19, 2008 11:54 AM
Perhaps this additional restriction is only required if we intend to use the Cube as a source for relational queries using Cube organized MVs.
Another way to do this is given below:
I'm assuming that when you say that you require Max along Time and Sum along other dimensions, you mean that you want LAST (chronological) along time at leaf level and SUM along other dimension. Also assuming that Time hierarchy has the following levels: DAY, MONTH, QUARTER, YEAR. Big assumption :) as finding out Max along time requires the help of the fact/measure whereas finding out last along time requires us to use the dimension (along with dimension metadata) alone.
Define 1 Cube: Cube1 ... Structure: Compressed Composite, datatype: DECIMAL
Set Aggregation: SUM along all dimensions
Create 3 stored measures ( age_m_sto, age_y_sto and pages)
You may want to set description for age_m_sto/age_y_sto as "******** INTERNAL: DO NOT USE ******** Stored Measure used for age_month/age_year"
Create 2 calculated measures - age_month and age_year defined as follows ...
olap expresssion to be given in AWM:
<age_month>: OLAP_DML_EXPRESSION('cube1_age_m_sto(time if time_levelrel eq ''DAY'' then time else statlast(limit(time to bottomdescendants using time_parentrel time(time time))))', DECIMAL)
<age_year>: OLAP_DML_EXPRESSION('cube1_age_y_sto(time if time_levelrel eq ''DAY'' then time else statlast(limit(time to bottomdescendants using time_parentrel time(time time))))', DECIMAL)
NOTE: The caculated measure performs the LAST along time action using the stored measure. For every higher level time dimension member, it reaches along the dimension to the last leaf level member and reads the stored measure for that lowest level time member.
Map and Maintain Cube.
From the SQL Cube View: Use only the columns corresponding to stored measure: pages and calculated measures: age_month, age_pages (ignore columns corresponding to age_m_sto, age_y_sto)
HTH
Shankar

How to map a cube to a non-leaf dimension level?

Hi,
I'm using AWM 11.2.0.1.0 and Oracle 11.2.0.2.0 on a CentOS 5.4 64-bit system.
I have a time dimension with levels Year, Month, Day, Hour, Half-Hour and several cubes mapping to the Half-Hour level. Now I'm trying to populate a cube using a time hierarchy Year/Month/Day, i.e., the mapping should be done at the Day level, not Half-Hour.
When adding the time dimension, although I specify that aggregation should be done only on the Year/Month/Day hierarchy, I still see all the levels in the mapping view. And when I try to map the Day level to the fact table, I get the following error:
The transaction is not committable: "Invalid Metadata Objects:
Invalid Object "OLAPIN.SSD_BALANCE.MAP1.DATETIME": "XOQ-01930: The cube dimensionality map has no mapped dimension."What is strange is that this used to work on version 11.1.0.7.0 (I have an example of it right in front of me). Am I supposed to do things differently with the new 11.2 version?
Thanks for your help!
Chris

My guess is that this is a result of
BUG 8264467 - REGRESSION FROM 10G : CANNOT LOAD CUBE DATA AT MULTIPLE LEVELS
This was fixed in 11.2.0.1 on the server and may appear to have nothing to do with your problem. Unfortunately there was a bug in the corresponding change in 11.2.0.1 AWM that can cause the symptoms you are having. It may be related to the following AWM bug.
BUG 8889693 - SUMMARY LEVEL MAPPING DOES NOT WORK IF USING DIMENSIONS WITH SURROGATE KEYS
There is an AWM "A Patch" for 11.2.0.1 (Patch 9672534: AWM 11.2.0.1A) that fixed the above bug and several other mapping related problems. You could try this to see if it fixes your problem.

Dimension refresh by awm - spoils aggregation?

Similar Messages

Maybe you are looking for