Reporting and DTP-Forwarding not possible until aggregates are initiated?

[marco_simon2]

Hi specialists,

I'm a little bit curious about the following thing:

I (repeatedly) cleared all data from a cube (which has configured aggregages).

Then I loaded data to that cube again.

I expected that - as soon as the data-loading has finished - one could report on that cube.

But it seems that the cube is available for reporting earliest when the aggregates have been initiated/rolled-up. Can you confirm that? I expected that the cube would already be reportable even when the aggregates haven't been rolled up yet. The queries would be slowlier - but they should work. I that wrong?

The same thing seems to be relevant for data-loading from that cube to a further data-target (via DTP).

As long as the aggreggates weren't initiated/rolled-up the DTP always extracted 0 records from the cube.

As soon as the aggregates where initiated, the same DTP found data for extraction and forwarded it to the target-cube.

In short words: Is reporting and data-loading from an cube with uninitiated aggregates impossible?

[marco_simon2 · Accepted solution]

Any input on that topic?

Is reporting generally not possible if existing aggregates aren't initiated?

[Former Member · Accepted solution]

you can do reporting as well as loading even if the existing aggregates are not rolled up.

During reporting, the query will first try to fetch the data from aggreagates if present, & if no data is found then it'll check into cube data.

In your case, there may be two possibilities ---

1. Either 0 records are getting updated in cube.i.e. records are deleted in start routine.

2. Or there is some selections/filters in query. for these selections/filters there is no data in cube.

[marco_simon2 · Accepted solution]

Thanks for your reply!

So how is it explicable that a request, which just has been loaded to the cube is not available for reporting (that's the request's status displayed in Cube>Manage>Requests).

But as soon as I roll-up that request to the aggregates, it becomes available for reporting...

[former_member184494 · Accepted solution]

Simon,

To correct Pallavi....

You CANNOT report on data in a cube which has ACTIVE Aggregates...

If you do not want to rollup aggregates - then deactivate them... I am not sure if switching them off will enable reporting .. but if the aggregates are active then you cannot report on the data...

The reason is thus :

The data reported on a cube which has aggregates will be aggregates with first priority... and all requests will have to be rolled up because the aggregates have to be current if the reported data has to be current.

Hence when there are active aggregates BIW just assumes that the new request is yet to be rolled up and hence not available for reporting... because BIW does not have the intelligence to sense if the existing ACTIVE aggregates are empty or with data and there fore if the reporting was available then data in the aggregates are the cube would mismatcvh and the reports runnig for the aggregate and reports running on the cube will mismatch which should not be the case...

I would also sughgect you to try switching off the aggregates and see if reporting is possible - otherwise you will have to deactivate them...

Arun

[Former Member · Accepted solution]

Hi

Deactivatate the aggregates and then the requests will be available for reporting. If aggregates exist on the infocube and if they are active, the loaded requests will not be available for reporting.

You may active and fill the aggregates once the reporting option becomes available in Manage.

Thanks