Skip to Content

Light Optimization job takes a lot of time, and sometimes is cancelled after 2 hours. In the ST12 trace, a lot of time is spent on table RSSELDONE which seems not related to BPC at all. Here job is checking the status of requests in the Infocube to get the lock for  ‘DB Statistics’.

Note 1709595.png

Reason and Prerequisites:

Newly input data leads the system generating a new open request, and if it is opened just before ‘DB Statistics’ step, the lock for ‘DB Statistics’ cannot be obtained. System tries the lock 3600 times, and after that (7200 seconds required), this step fails.

Solution:

Implement SAP Note 1709595 Block data input during the whole process of optimize. This Note requires upgrade to the next patch level, but you can manually change the optimization process chain.

The steps in light optimization before this Note:

START->MODIFY->DELETE INDEX->CREATE INDEX->LOAD MODE ON->PLAN MODE ON->ROLL UP->COMPRESS->UPDATE DB STATISTICS->END

The idea here is that step “UPDATE DB STATISTICS” should start before “PLAN MODE ON”. But step “PLAN MODE ON” do need wait for step  “UPDATE DB STATISTICS” to be finished. After step “UPDATE DB STATISTICS” started, it is OK to change back to “PLAN MODE ON”.

When plan mode is changed to “LOAD MODE ON”, user will not able to input data through input schedule. So you can try the process chain below, change the plan mod e to “LOAD MODE ON”, immediately  trigger the  “UPDATE DB STATISTICS”. Meanwhile delay 3 seconds and change the plan mode on in parallel.

This process chain has not been tested.

ZLIGHT_OPTIIMZIE1.JPG

Other related SAP Note:

1625384 How to determine which variant step of a BPC process chain has failed

1704602 – Light Optimize fails with error “RSSM_PROCESS_DBSTAT terminated because InfoCube/DSO Object [Tech.Name] could not be locked”

1632608 – Lite Optimize in BPC NW fails on the ‘Plan Mode On’ variant step

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply