Attribute Change run failed due to the User Lock

Hi Friends,
attribute change run has failed due to the user lock.
can any one tell me how to process and what is the main cause behind on this.
thanks in advance

if master data is loading at same time while the attr/hier change run is occuring,it cause the change run to fail.
Usually u get error message like..user ALEREMOTE has locked the MD tables..
Wait for some time and then try attr change run manually by going to rsa1->tools->apply hier/attr change..
if it still shows locked..try to see in rsmo if a MD load has got stuck..
else..see in sm12 to find lock is on which tables..
last resort..delete lock forcefully from sm12..
first option is wait for some time and give a try again..
cheers,
Vishvesh

Similar Messages

Attribute change run Failing in Process Chain

Hi guys,
Every day my process chains is failing due to Attribute change run and I am maually running attribute change run.
And one more thing when the attr. change run is triggered automatically,then it is generating 2 change counters in RSATTR tcode instead of 1.
One is successfully completes and one is still in schedule.After 2days days it is showing like completed change count id.
Please help me.
Regards,
Tiragati.

Hi,
As you said Attribute change run step is failing every day.
can you post the error message. is it failing because of Lock issue or some other issue.
Mostly attribute change runs fails with lock issues. if its the same problem in your case. make sure that no master data objects runs at the time attribute change run runs.
Try to put some delay in the process of the Attribute change run so that it will not get failed.
Check if its the same ACR scheduled or diff objects?
Regards
KP

Attribute change run fails - "Error when deleting the data record /B05/X.."

Hello,
I get the error message "Error when deleting the data record /B05/X.." on doing the change run.
I have already done RSRV on this objects and found no errors, but still the activation fails.
please give your suggestions ASAP to fix the issue as it is on production system.
Thanks.

Attribute change run could fails due to 2 reasons-
(1) attribute xchange run is already runnnig for any toher object(monitor lock) (check by thi prog-RSDDS_CHANGERUN_MONITOR)
(2) data is loading deleting from the object on which attribut changerun is running.(go in a manage tab and check)
check this two conditions and rerun the attribute changrun again from program - RSDDS_AGGREGATES_MAINTAIN and give the master data name in the selection.
Hope it helps you.

Attribute change Run Failed/Scheduled

Hello All,
For a process Chain Attribute Change Run has failed in BW 3.5,and I Repeated the Change Run in Chain only
where Repeat option is ,now the problem is in RSA1 it is now that change run is scheduled
and sm37 it is showing that Canceled.
Now there is Other Process Chain in BI7.0 which picks data from 3.5
Should I repeat the Master data Chain in BW 3.5 followed by in BI 7.0
Or any other way is possible as in BI7 the chain has run successfully..
Thanks,
Kiran

Hi Kiran.......
BI 7.0 and BW 3.5............totally two seperate systems..............here BW 3.5 is just act as a source system of BI 7.0.............if change run fails in BW3.5...............it is not going to effect BI 7.0.............
As ajeet already said............it will effect the SID s in 3.5.............because attribute change run activates the master data...........and SID get generated during the activation of master data.......
Also it will effect the aggregates............because aggregates also get adjusted during change run.......if any of the aggregates contains the master data.........which are getting activated in the change run....
Now u r saying........that in SM37 it is showing that the job got cancelled............So it will not locked the master data..............terminated change runs generally lock the master data............then we hav to repeat the chain run to release the lock.........and u hav already repeated the change run............so no issue........
Hope this helps..........
Regards,
Debjani........

Attribute Change Run terminating - repeated several times - not locked

I had a failure in my master data chain tonight. The attribute change run that ran yesterday ran for 11k seconds and was cancelled (it says manually). When the chain ran tonight, the process failed again. I checked the log and it says "UNCAUGHT_EXCEPTION" and it created a short dump. I tried repeating to see if it did anything and it gave me the same message.
I went into the change run monitor and reset the status and manually tried to run the change run again. Same result "UNCAUGHT_EXCEPTION".
I then checked table RSDDAGGRMODSTATE and there was no blank CNSID entries, but there was a blank "completed flag" entry. I don't have change access to the table in prod so I cannot manually change it to X (meaning closed). I reset the status again in the chagne run monitor and the record with the blank "completed flag" disappeared. I repeated the change run and it failed again and a new record with the "completed flag" being blank appeared in the RSDDAGGRMODSTATE table.
I checked SM12 and there are no locks there. I'm on 7.0 so I can't manually right click on 0CUSTOMER and activate the master data either.
As a last resort I did run the function module RSDDS_AGGR_MOD_CLOSE but that short dumped too.
Any ideas? Please? This will fail my other chains that have 0CUSTOMER in the aggregates. Thanks.

HI,
Firstly try this FM RSDDS_AGGREGATES_MAINTAIN
if not possible
Try doing it manually
Uncaught exception may come due to many reasons
IN RSA1 go to tools and select attribute change run
Check the blog it shows you how to manually do attribute change run step by Step (for BI7.0 also)
/people/debjani.das/blog/2009/03/30/attribute-change-run-acr
Regards,
MADhu.
Edited by: MadhuMarupudi on Aug 21, 2009 5:49 AM

Attribute change run process doesn't run in the chain

Hello everyone,
I have implemented a process chain with multiple parallel processes (12, like the batch processes in the application server) and I have put for each stream a loading of master data followed by the attribute change run process. When I run my chain then I find that one o two Attribute change run process doesn't run (the InfoObject chosen seem to be random!). The chain remain in yellow color. Can you help me anyone about this question?
Regards,
Francesco

Couple of thing you should keep in mind while loading master data.
if two loads are targeted to the same infoobject they will collide and as a result the later load will fail.
it is a good practice to use only one Attribute change run in the end before you load master data. but if there are dependecies you can use several in series
Also when you set up Attribute change run make sure that Attribute change run will pickup only the particualr infoobject not all the objects in the Attribute change run list.

ABAP program to add in the process chain before the attribute change run

Hi
I need a ABAP program to add in the process chain before the attribute change run(process) to avoid the locks, can any one send me the program
Regards,
Satish

I am not sure of any standard program .... but you can write your own... should be a small one..
you can check if the table RSDMDENQ has entry for your InfoObject... if yes, then its locked.. if not.. its not locked

Attribute Change run canceled

Hi
I have loaded master data for an Infoobject and executed Attribute change run by saving that object and execute. I got the message like Attribute change run is canceled((protocol/shortdump) now i can not able to run any attribute change runs since save button is not available in the window and also unable to load data to the same infoobject getting errored and giving messsage locked by attribute change run i have checked in sm12 no locks exist on this object
Thanks
Vani

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
The Problem may be that there is another change run triggered parallely to yours.In any SAP System only One attribute change run can run at one point of time. i. e If one attribute change run is running in system from any process chain or for any project and 2nd one fails, if start at same time due to locking problem. Due to this entire data load fails.
Just check it there are any other change run active in SM37. Repeat your change run once the other change run is over.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and may need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
thanks,
JituK

Regarding Attribute Change Run failure.

Dear All,
We have a process chain which contains many meta chains.
Now in each chain i mean meta chain there are attribute change runs
We have desegregated the attribute change run. is tere any method to place a check for attribute change run locks because at the last i have another attribute change run which is failing every day because of the attribute change run is still happenign in some chain.
how do i implement it?
Thanks in advance
Janardhan Kumar.

Hi Janardhan,
In master data process chain where you have added process of attribute change, just insert a program before this process:
The program is: RSDDS_CHANGERUN_MONITOR
This program will check for any another attr change run running at that time and if there's any other attr change run runnning locking the object which your next attr change run requires then this program will not allow your attr change run to run.
Once all the locks all cleared for attr change run it will trigger the next node.
This program has a do loop which keeps on checking until unless locks are cleared.
Regards,
Vij

Attribute change run cancelled - Reg

Hi,
Can we run master data Job if attribute change run has cancelled for the same Master data Object?
Thanks,
Ajay

Hi,
if the attribute changerun is cancelled then you cannt run thw masterdata.. because it wil agian fail with the message :
locked by terminated changerun .. so first run the chaingerun succssfully to release the masterdata..
check the link to release the lock ..
Attribute ChangeRun issue
hope this helps you .
Reagrds,
Shikha.
Edited by: Shikha Goel on Oct 14, 2008 10:09 PM

Error with Attribute Change Run - Urjent

Hi All,
In our scenario we will load master data from APO&ECC to BW.When we are doing attribute change run we are geetting short dump and jobs are cancelling every time .
Please fidn the details below.
Short Dump : ORA-14400 with ABAP/4 DBIF_RSQL_SQL_ERROR..
When I have searched in the forum I got some information saying that we need to drop the index and recreate the index.But we have around 40 cubes.Then how I am going to deside on which I need to the relavent settings.
Please provide me the proper answer.We are facing this problem from past last two days.
Regards
Ramakanth.

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Please use the table RSDDCHNGPROT and find out the infocube affected by this change run and de-activate "ALL" the aggregates
of the infocube listed under CNSID=0. Then start the change-run.
You can rebuild/refill the aggregates once the change-run is finished.This is necessary because there are inconsistencies in the aggregates
Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
176606 - Apply Hierarchy/Attribute change ... long runtime
175309 - Hierarchy/attribute - change run improved
oss note 322644
Hope this helps.
Thanks,
JituK

Attribute change run taking more time

Hi Gurus
I am loading master data 0mat_plant everyday
nearly 2 to 3 lakhs record .The extracrion and loading is taking 30 min but attribute change run is taking 3 hrs .Is there any way to reduce attribute change run time.

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes.
There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
Note 903886 - Hierarchy and attribute change run
thanks,
JituK

Process chain best practice - attribute change runs

When building attribute change runs into Process Chains I see that there are potentially two main options to consider:
1. One to One mapping. Incorporate a separate attribute change run object type after each InfoObject has been loaded.
2. Many to One mapping. Build the process chain so that one single attribute change run occurs after all the InfoObjects have been loaded.
I would be interested to see how other people have incorporated their attribute loading into Process Chains.
any info appreciated.
Mike

We run the attribute change run twice in our daily process chain, here's our order:
- Load all master data
- Attrib change run
- Load all tx data
- Run ABAP programs that generate master data
- Attrib change run
I doubt there will be much of a performance difference if you do the change run after each master data load, but it makes the process chain a lot easier to read.

How to do Collective Attribute Change Run ?

Hello SDN s,
How ya all ?
I have maintained about 20 Master Data Attribute InfoPackages in a Process Chain. I planned to do a Collective Attribute Change Run, I dragged & dropped the ATTRIBUTE CHANGE RUN process from expanding the OTHER BW PROCESS TYPE created a Process Variant for that and here i got struck !!! ???
What to give in the OBJECT TYPE & OBJECT NAME entries ? In the OBJECT TYPE InfoObject is there, but what about the OBJECT NAME ? what i should select ? It is a collective one.
Faster Replies would make me to learn faster !!!
Thanks !!!
Best Regards....
Sankar Kumar
+91 98403 47141

Hello BhaNu,
How r u ?
Happy to see your reply man, sorry Woman
So u r saying that i have to maintain the entries for each and every InfoObject ??
Suppose, if i load the attributes for 100 InfoObjects then i have to maintain the entries for all of them ?
Best Regards....
Sankar

Attribute Change Run in Procee chain.

I am trying to create a process chain for loading employee master data. I have three datasources populating this data.
So in the process chain I have to add the Change Run process type only after loading data from all datasources right ?
what is the process type 'Attribute Change Run' useful for anyway ?

You are correct. If the loads to the employee Master Data Attributes are done serially, then you can end it with the 'Attribute Change Run' variant. If the loads to the employee Master Data Attributes are done in parallel, then you can have all three InfoPackages flow into an 'AND' variant and then have the 'Attribute Change Run' variant.
The 'Attribute Change Run' in effect activates the Master Data Attributes, much like the activation process of activation of a DSO. The way it does it technically behind the scenes, however, is different.

Attribute Change run failed due to the User Lock

Similar Messages

Maybe you are looking for