ACR Failed for your Master data objects? Simple tips to analyze
This document will gives you summarized view about the ACR failure and how to analyze the root cause for the issues.
The ACR for your master data objects are failing with error message “Locked against indexing or table” then the reason would be any of the below.
Reason 1 :
Loads to that master data object might be running in parallel with the ACR.
Solution : Stop/Cancel the loads and rerun the ACR manually. Later you can resume back your loads.
Reason 2 :
Check for any ROLLUP or BIA Indexing is running for the cubes associated with that Objects.
Solution : Wait till the ROLLUP or BIA Indexing completes and rerun the ACR manually.
Reason 3 :
Check for any daemon jobs running for that Objects.
Solution : Wait till the daemon job completes and rerun the ACR manually.
Reason 4 :
Check for any other ACR is already running for the same object.
Solution : If the failed ACR contains other Objects also, then repeat the ACR after the actively running change run is completed.
Tips to Quick check the ROLLUP or BIA Index running in the System.
Go to the T-Code SM37(where all the background processes running will be visible) -> type the Job Name “BI_PROCESS_ROLLUP” and check job status “Active”,”Finished” & “Cancelled” then execute. then check in the job logs.
Go to the T-Code SM37 -> type the Job Name “BIACTI_*” and check job status “Active”,”Finished” & “Cancelled” then execute.then check in the job logs.
For Checking the status of ACR, you can use T-Codes CHANGERUNMONI or RSATTR.
Other Usefull T-Codes are,
Note: Always rerun manully the failed ACR job from TCODE : CHANGERUNMONI because, If we are repeating ACR from the process chain, it will generate one more job. But already failed ACR job will be locked with BIA job. So it will get fail again. (If ACR job failed because of lock with the BIA Indexing then we have to follow above procedure).