cancel
Showing results for 
Search instead for 
Did you mean: 

BPC 7.5 Lite Optimize not Collapsing Records

Former Member
0 Kudos


Environment is BPC 7.5 SP16

An example of the issue is an app that has 11 records visible through RSA1 with the same "key".

The data values are (as example)  +3, -3, + 3, -3, +3, -3, +3, -3, +3, -3, +3

I would expect lite optimize to compress (collapse) these 11 records into a single record with data value of +3

This is NOT happening now.  I "know" it did at some point in the past.  This behavior is causing the record count in the app to explode.

Has anyone seen this?  Any possible reasons?

I really would like to resolve before beginning a BPC 10 upgrade.

We have checked the process chain in BW through RSPC and it looks as it always did.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

This is a screen shot of the DM package log - indicating success.

However, the following image from RSA1 clearly shows some Request ID's, which I thought went away after a lite optimize.  So, I question if it really worked. The last two records do not have Request ID's so I conclude it worked at some point.

I looked at the process chain in RSPC.  It looks different than ones I have seen in other posts and examples.  I see a Plan Mode On  immediately following the Load Mode On.  Would this make it fail?  If this is wrong, where can I find the correct one?

Finally, here is the switch settings on Collapse.

What is going on?

former_member186338
Active Contributor
0 Kudos

Hi Jim,

For BPC 7.5 the story is not the same as with 10! The chain also depends on BPC SP level.

Look on RSPC:

And:

Vadim

former_member186338
Active Contributor
0 Kudos

But the advanced script of DM package in BPC NW 7.5 is:

TASK(/CPMB/SWITCH_TO_LOAD,INFOCUBE,%APPBINAME%)

TASK(/CPMB/SWITCH_TO_PLAN,INFOCUBE,%APPBINAME%)

TASK(/CPMB/CREATE_STATISTICS,DTA_CUBE,%APPBINAME%)

TASK(/CPMB/LIGHT_COMPRESS,DTA_CUBE,%APPBINAME%)

TASK(/CPMB/ROLL_UP,DTA_CUBE,%APPBINAME%)

TASK(/CPMB/LIGHT_COMPRESS,ZERO_ELIMINATION_ON,X)

with the bold line for zero elimination (not supported in BPC NW 10)

Vadim

Former Member
0 Kudos

Vadim,

Thank you for your responses.  I can surely add that highlighted line to the DM package script.

I do not now see the process chain image I thought I added in my prior message.  I will insert it again.  It has three additional steps that are not in your image:  Plan Mode On (BPC: Switch cube to plan mode);  Indexes (BPA: Full Optimization - Delete Index); and Create Index (BPC: Full Optimization - Create Index).  We are on 7.5 SP 16.  Should I have these steps removed from the process chain.

My chain again:


former_member186338
Active Contributor
0 Kudos

Hi Jim,

Not sure you properly performed all postinstallation steps of SP's

Vadim

Former Member
0 Kudos

I do not install the SP's, our BASIS team does.  Can you suggest where I might go to see what should have been done?

And do I need to remove those three steps from our process chain?


former_member186338
Active Contributor
0 Kudos

You can read all notes related to SP installation (central note).

Vadim

former_member200327
Active Contributor
0 Kudos

Plan mode on and off must be in that Process Chain. Deletion and recreation on indexes depend on the data base: in some of them compress goes faster without indexes, in some with indexes.

former_member186338
Active Contributor
0 Kudos

Hi Jim,

Please, provide details with logs, RSA1 and RSPC screenshots etc.

Vadim

Former Member
0 Kudos

Hi Jim,

How long did it to run the lite optimise?

maybe try to run it 3 times, maybe the first run didn't complete process all the records.

Andy

Shrikant_Jadhav
Active Contributor
0 Kudos

Hi Jim,

Can you check the Number of requests that you do not want to collapse = 0 or not.

Kindly go through the below link may be helpful

Shrikant

Shrikant_Jadhav
Active Contributor
0 Kudos

P.S. Also go through the below link

Shrikant