This document dictates the process/configuration changes of how to control timings of ACR runs and also how to handle the situation wherein the ACR got stuck.
Author: Nainpreet Singh
Company: HCL AXON
Created on: 01 November 2010
Author Bio
Nainpreet Singh is certfied SAP BI Lead Consultant working for HCL AXON. He is having around 8 yrs of rich design experience in SAP BI/BW area wherein he worked with various industries like Retail, Consumer goods ,utilities ,gaseous etc throughout globe.Currently he is working on the Roles of Solutions Architect in North America.His expertise includes BI/BW, ABAP, BPS,BOBJ.
Steps to Overcome Long ACR run: .................................................................................................................... 4
Points to Consider: ........................................................................................................................................... 10
Related Content ................................................................................................................................................ 11
Disclaimer and Liability Notice .......................................................................................................................... 12
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Attribute change run is the process in BW wherein the master data get activated (whatever has been recently loaded) and adjusted in the aggregates. This process plays vital role in our day to day batch processes because ACR process takes maximum time in batch processing in most of the implementations.
This document dictates the process/configuration changes of how to control timings of ACR runs and also how to handle the situation wherein the ACR got stucked.
Configuration
ACR has a threshold value, which takes the decision of aggregates jobs either to rebuilt or to fill up with delta process (Old records get updated negatively and new records get updated positively). This decision depends upon the percentage of changes. If percentage of changes is equal or less then this value (Limit with Delta) then aggregate will be rolled up and if the percentage of master data changes are more then threshold value then aggregates will be rebuilt. Below transaction to analyis/ change Aggregates threshold is RSCUSTV8.
As per the system response one can increase this delta limit till you get minimum timings on ACR process. This depends upon system to system but ideal limit is 20.
Block size is use to prevent overflow of temporary tablespace i.e. PSATEMP. This is used if E table or F table of Infocube is larger then the Blocksize then source to update aggregates will not be read at once rather divided into blocks.
Ideal size of blocksize is 999999999.
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Below steps dictates how to overcome and resolve situation wherein you figure out that in Batch process ACR is running from long and doing nothing or stucked somewhere. I called below process” forcefully ACR completion”.
In normal scenarios we came across various situations wherein ACR is kept on running and there is no alternative rather then wait and watch.
To overcome these situations I’ve one workaround. This workaround comprises of following steps:
1. First Make sure you’re ACR got stuck
2. Identify the aggregate.
3. Kill ACR Job
4. Deactivate the aggregate manually
5. Restart failed ACR
6. Wait for ACR to finish
7. Activate deactivated aggregate
Details:
First Make sure you’re ACR got stuck- Normally we get an idea by analyzing the statistics of aggregates rebuild time.
For Example: If ACR got Stuck on one of the aggregate and that aggregate ACR had already spent 6 hrs on that particular aggregate and you know normal filling (rebuilt) of this aggregate from scratch won’t take more then 3 hrs then you would be in problem.
Identify the aggregate: Aggregate name can be found on ACR Monitor, to get to ACR Monitor use ABAP report RSDDS_CHANGERUN_MONITOR and execute this in SE38.
Below Details is for ACR when it is not Running (this is just to explain details)
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
After execution of report this will display following screen with summary of changes in ACR.
The above screen will show you summary not details so number of actual aggregates affected, characteristics and number of changes can only be seen after clicking details button.
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
After Clicking Details Button, It is clear that only one aggregate is affected, not 8 and it also displays the details of changes.
Further Drill down will display cube, aggregate name and the process for adjustment adapted by aggregate. Below adjustment has been adapted by delta as shown in screen shot.
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Select the required job in SM66 and kill without core.
Deactivate Aggregate Manually
As per the details of aggregate analysis screen traverse to the cube and the aggregate, deactivate the same.
Restart Failed ACR
Use programme, to get to ACR Monitor use ABAP report RSDDS_CHANGERUN_MONITOR and execute this in SE38, restart failed ACR.
To Restart Change run Press Highlighted Execute Button:
Note: incase of failed ACR instead of green light you’ll find Red light on left side of screen. This below screen is for non-failed ACR. But Start button will remains the same.
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
1. This method is used to handle situation wherein Batch process got stucked on ACR job and there is no other option left.
2. Make sure ACR job Ran successfully once you restarted.
3. This can be done on various aggregates; it’s possible that ACR job might get stucked on 2 or more aggregates.
4. Pls use precaution and common sense before executing this procedure because some time cost of rebuilding aggregate is heavy in terms of time it takes to rebuild.
Attribute Change Run (ACR) Performance Optimization and Forceful Completion
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.
