cancel
Showing results for 
Search instead for 
Did you mean: 

Aggregates

Former Member
0 Kudos

Hi,

When Creating a Cube , will it automatically create aggregates?

We are not using any aggregates.

But i am getting an error in the PC while Compressing a cube.

It is showing that "Lock not set " and also "Active, empty,filled Aggregates Present for the Cube" and the PC is stopping there.

After sometime if we do the "Repeat" its working.The data in the Cube is Compressing.

I want to know whether this problem is due to Locking or some other thing.....

Thanks in Advance!!!!

Accepted Solutions (1)

Accepted Solutions (1)

praneeth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

When you create the cube, the aggregates are not created automatically. You need to explicitly create the aggregates. select your info-provider, in the context menu choose 'Manage'. under the roll-up tab, click on 'Aggregates'. It shows you if there are any aggregates build on your cube.

Thanks,

Praneeth.

Former Member
0 Kudos

We dont have any aggregates , but while running Process Chain its stopping at the Compression step stating that "Active, Empty , filled aggregates present for the Cube, Abort", if after sometime , if we try to repeat the step its running without any errors.

is this a problem with the Table Locking......

Former Member
0 Kudos

Hi JS,

You might have activated your cube along with the aggregates from the business content, and so there might be some aggregates existing for the cube.

So when you try to compress the cube the system is proposing for a roll-up for the aggregates which should be done before the compression.

Check out for any active aggregates on the cube and switch them off or deactivate the aggregates. A icon will be displayed in front of the cube name(after the technical name) if there are any aggregates existing.

Hope this helps,

Regards.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi JS,

Are you loading some master data attributes also in the process chain. If so, then may be you forgot to include the "attribute change run" step in the process chain. Once you do that before the cube load may be the error would not appear.

Bye

Dinesh