Maintain Cube Not Working

Question

Brijesh,
I built my dimensions, levels and heirarchies successfully and also created cube. Now that I've built my measures and run the maintainance, I'm not seeing any values in them even though I know I should.
Based on my mapping, the keys from the fact are going to the right dimensions (and I even made a simplier, just one dimension --> measure cube as well), but no success. There are cases where I know I shouldn't get any data (based on selected values), but when I make valid selection I see only 0.00 being displayed.
Can you tell where I may have gone wrong here? Are the values made available for selection (the attributes) ONLY supposed to be the same one-to-one values available in the fact table?
**I'm using the simple SUM aggregate function for my measures, and pretty much all the default configurations given.
Brijesh Gaur
Posts: 416
Registered: 04/03/08
Re: where are dimension attributes in AWM - cube viewer?
Posted: Nov 10, 2009 3:21 AM in response to: mikeyp Reply
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
mikeyp
Posts: 14
Registered: 09/22/09
Re: where are dimension attributes in AWM - cube viewer?
Posted: Nov 13, 2009 1:24 PM in response to: Brijesh Gaur Edit Reply
Brijesh,
Thanks for your suggestions, and here are my results based on that.
1. No records rejected after running cube maintenance
2. I didn't limit my dimension to specific value as you recommended, but made my member the same as my Long and Short description attributes using AWM. (Its a flat dimension i.e. no level or hierarchy since the dimension only has one value/meaningful field.
Based on those steps, I still didn't get the results I was looking for. The fact table has five values for that one dimension and I'm seeing 0.00 for 4 of them, and an inaccurate value for the last one. (this after doing comparison with simple aggregate query against fact)
Do you have any other possible reasons/solutions?
**Loading the Global Schema into our dev environment is out of my hands unfortunately, so that's the reason for the prolonged learning curve.

Answer 1

Brijesh,
Here's the results of what you suggested:
1. Creating test dim and fact table with simple case you provided was successful, and AWM was able to map the same values to cube which was created on top of that model.
2. I took it a step further and changed dim values to be same like existing dim table
2.b. Also replaced test fact table values to mimic existing values as well so it would match what's available in dim table, and here's where the fun / mystery begins
Scenario 1:
I created fact like this...........select dim value, sum(msr) from <existing fact table>
As you can easily tell, my values were already aggregated in the table, and they also match perfectly in cube created by AWM - no issue.
Scenario 2:
Created fact like this............select dim value, msr from <existing fact table>
Quite clear is that my values are no longer aggregated, and broken down across multiple occurences of dim values; did this so that I can verify that the "sum" will actually work when used in AWM.
The results from scenario 2 lead me back to same issue being faced before - i.e. the values weren't being rolled up when the cube was created. No records were rejected, and there was only ONE measure value showing up (and it was still incorrect), and everything else was 0.00
I retrieved this error from the command program that runs in the background. This was generated right after running the maintain cube:
<the system time> TRACE: In oracle.dss.metadataManager.............MDMMetadataProviderImpl92::..........MetadataProvider is created
<the system time> PROBLEM: In oracle.dss.metadataManager.........MDMMetadataProviderImpl92::fillOlapObjectModel: Unable to retrieve AW metadata. Reason ORA-942
BI Beans Graph version [3.2.3.0.28]
<the system time> PROBLEM: In oracle.dss.graph.GraphControllerAdapter::public void perspectiveEvent( TDGEvent event ): inappropriate data: partial data is null
<the system time> PROBLEM: In oracle.dss.graph.BILableLayout::logTruncatedError: legend text truncated
Please tell me this helps shed some light on the main reason for no values coming back; we really need to move forward with using Oracle cubes where we are.
Thanks
Mike