Lite Optimize package failing and changing Planning Behavior

[Former Member]

Hi All,

We have scheduled a daily run of the Lite Optimize package. Some days the data load is very high. So sometimes, the Lite Optimize package fails (Aborted) when it runs over 5-10 minutes or so because it is exceeding the limit that is set in the backend. However, we do not face this issue when he select the optimize model from within the Admin screen of the BPC server URL. Does this mean that there would be different timeout limits depending on whether we run the Lite Optimize package from the Data manager screen or whether we execute it from the Admin screen?

The trouble we have is that, after aborting, it is changing the Real-time Planning behavior in the back-end which we are forced to change everytime the package aborts. Is there any solution for this?

Any help would be appreciated.

Thanks.

[Former Member]

hi sanmukh,

did u check the process chain behaviour in BW

[Former Member]

Hi Nagarjuna,

What exactly do I need to check with respect to the behaviour?

Can I modify the Process Chain in someway to override the 10 min limit set in RZ11.

Thanks.

[former_member190501]

Hi,

Usually light optimization fail if time limit exceeds. Execution time will depend on number records in the cube.  Try to analyse the record growth and set the time limit.

You can set time limit from RZ11 for rdisp/max_wprun_time to avoid short dumps. When you start light optimization system will change the load behaviour of infocube from Data loading not allowed to planning not allowed . This will be changed back only up on the success of optimization. Due to this changes system does not allow users to do normal operations if optimization process fails.

My advise is do not change load behaviour manually if optimization fails. Try to finish the job by changing time limit.

Thanks,

Raju