cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BPC 10 Lite Optimize Still Running DB Statistics even when there are no changes

bob_ciarletta2
Discoverer
0 Likes
359

Up until June 2016, if there was no data loaded into bpc through either input schedules or data manager packages, and no master data changes, then the Light Optimize would run for 2 minutes, not performing the db statistics.  Starting in June 2016, the Light Optimize is now running 30 minutes under the same conditions however now it is running db statistics even though no data changes have been made.  Normal run times would be 2 minutes without data changes and less than 15 minutes with data changes.  However currently we are seeing 30 minutes without data changes and anywhere from 45 minutes to 2 hours with data changes. This is causing unnecessary down-time.  No patches were installed during this time period.  What is causing the db statistics to be triggered to run when no data is changing?  This is only occurring in our production environment, both our dev and qa environments are running a Light Optimize in 2 minutes. BPC_STATISTICS is set to OFF Software Versions SAP_BASIS 740 SP13 BI_CONT 757 SP 7 SAP_BW 740 SP13 CPMBPC 801 SP13

Accepted Solutions (0)

Answers (1)

Answers (1)

akos_beres
Contributor
0 Likes

Bob,

I'm not going to pretend I'm a basis consultant but what you are experiencing in your system is not normal. Reach out to your Basis contact and see if they can pinpoint what is causing the issues on the database side. There are performance notes out there for BPC like these:

https://launchpad.support.sap.com/#/notes/2272366/E

https://launchpad.support.sap.com/#/notes/1634922/E

... but you will probably need a technical resource to help you with them.

Hope this helps!

Akos

bob_ciarletta2
Discoverer
0 Likes

Akos,   This is a reply from our basis guy: Apparently the issue is with the Lite Optimization Process Chain. Per the definition of the Process Chain, DB stats step would be skipped if a prior data compression step is not executed. Somehow data compression occurs every time; even if there is no data load. Activities in database (like db stats etc) happen due to process change steps / events. Something is causing lite optimization process chain to execute data compression which in return calls db stats. Thanks Bob

akos_beres
Contributor
0 Likes

Bob,

I think I understand what he is saying but not sure if I agree but I'll let it go. As I said I'm not a basis expert but from the functional side, something doesn't seem right in regards to BW sizing. It sounds like either the amount of data hitting your system or concurrent users are overwhelming BW. Again the above two notes have some performance tuning tips that might be able to help. You can also ask SAP to help you identify the bottleneck. So one more question ....


This is causing unnecessary down-time.

Can you explain the above?

Why does lite optimize run during the day? Do you have 24 hour operations, is BPC used around the clock? Is the input template load volume so large during the day that lite optimize has to run to speed up the system?

All I'm suggesting is there might be a functional solution to this issue.

Akos

bob_ciarletta2
Discoverer
0 Likes

Akos

  the unnecessary down-time is related to users not being able to load data while the lite optimize is running which when lite optimize runs for 2 to 15 minutes is not an issue.  We only run the lite optimize once at midnight which is during the day for some of our foreign divisions.  On days when there is no dataloads and the lite optimize still takes 30 minutes... the system is not overwhelmed.  Is there a different forum for BPC Basis/BW questions since this does not appear to be functional or performance related?

thanks

bob

akos_beres
Contributor
0 Likes

Bob,

make sense that's what I thought. There is a BW forum but most of the people on there are not familiar with BPC process chains. I have posted a process chain question a while back and didn't get a single response. You can try though and see if you have better luck.

Your best option at this point is to open a ticket with SAP and see if they can help.

Akos