Skip to Content
avatar image
Former Member

ERRORS FOUND RETRIEVING DATA FROM BPC REPORT DURING LIGHT OPTIMIZATION

Good morning:

My understanding is that Lite Optimization doesn’t take the system offline, and can be scheduled during normal business activity (e.g. after a data load). So my expectation is that users can run reports on a cube/application even if a light optimization is running on that cube e.g. I thought I read something about temp tables created behind the scenes by BPC during the light optimization / compressions to make the light optimization process transparent to the end users.

We are on BW 73005 and BPC NW 7.50.12 and when running a report with EVDRE during BPC LIGHT optimization we get error message "BPC ERRORS FOUND RETRIEVING DATA". The application log also shows an MDX statement error:"Due to cube /CPMB/xxx being locked, query cannot be executed"

Is is standard/expected behavior that BPC users cannot run/expand a report (with EVDRE) during a BPC light optimization ?

- If yes, are there any workarounds (other than not scheduling the light optimization during business hours) ?

- If not, any suggestions to resolve/prevent this error.

Thank you,

Catherine

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jul 20, 2012 at 10:49 AM

    Hi Catherine,

    The simple reason which I can think of is that during lite optimization, records are being compressed (if at all multiple records for same key exists) plus there are other things like deletion of infocube statistics, movement of records from E to F table, etc. So, when you execute a report/input shedule at the same time, the system is unable to retrieve data.

    Not sure about workarounds, I doubt there is one except that schedule optimization during non-business hours.

    Hope it helps!!

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Catherine

      We have the same problem. Having come from the MS environment where this isn't the case it is very frustrating. Did you get a satifactory answer from SAP?

      Thanks

      Gayle