Infocube locked by terminate change run

Hi All,
Message "infocube locked by terminate change run" when I try delete infocube.
I use SM12(Display and Delete lock), but there is no lock list.
Anyone had this problem ? and how to fix it.
thanks in advance
supriatna

Hi All,
the cube cannot delete because some InfoObject changes was not applied, I try with
menu tools -> Execute Hierarchy/attribute changes (Ctrl+F9), and try to execute all the changes, after that the cube can deleted.
thanks roberto & frank for ur suggestion
supriatna
YM! asupna

Similar Messages

Cubes locked in terminated change runs

Hi guys,
Couple of cubes are locked in terminated change run......... how do i resolve this as there are no locks set form them in sm12 or db01
what is the way to go..........
Thanks,
Your help will be rightly appreciated

Please 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.,etc.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
The Problem is that there might be 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.
This blog will explain how to prevent this from happening.
http://sapbwneelam.blogspot.com/2007/08/how-to-avoid-attribute-change-run.html
Hope this helps.
Award points if useful.

Attributes of characteristics cont_acct are locked by terminated change run

Hello Guys ,
Today we have a failure of master data load, when i checked in the details tab i saw the below error can some one please help me in this.
Attributes of characteristics cont_acct are locked by terminated change run
Lock not set for : Loading master data attributes.
Thanks in advance!!!

Hi.....
It means that the infoobject cont_acct is locked by a terminated change run......this situation generally occurs if someone manually cancel a change run.......in this situation lock does'nt get released.......
If you have authorization to delete a lock......then you can delete the lock.........as suggested by Ajeet........
Otherwise run change run for this particular infoobject using the program : RSDDS_AGGREGATES_MAINTAIN....to release the lock........
Hope this helps.........
Regards,
Debjani.......

Attributes of characteristic 0MATERIAL are locked by terminated change run

Hi All,
i am planning tod see the data in 0material.when i click on maintiain master data button then i am getting Attributes of characteristic 0MATERIAL are locked by terminated change run 384436434.how can i solve this issues.please help me .
Thanks & Regards,
chandra

here you need to completed the terminated ACR first because Lock will never get released, until we repeat the
terminated Change run(Change Run id should be same). Also when a Change Run get cancelled automatically ,we should check the Job Log. If it is a Terminated Change Run, then again we should repeat the Terminated Change Run, then only lock will get Released.
For this......
*Go to RSA1 >> In the top TOOLS tab >> Select Apply Hierarchy/Attribute Change >> Click on Monitor and Start terminated
Change run >> there click on Start Change run with Set Filters.........it will restart the Terminated Change run.....*
then you can repeat your process chain.
Thanks,

Locked by terminated Change Run

Hello BW Experts,
Trying to load 1 million records master data. Attribute change run short dump due to lack of space. Then deleted the master data. Again running the load with less records ( 10k ). PSA --> Infobject load not starting due to the error
"Attributes for characteristic ZCUSTNUM are locked by a terminated change run
Message no. RSENQ063"
I have done the below checks:
1)     Cleared all the locks in sm12
2)     No records to be updated in sm13
3)     No other processes running in SM50
4)     No short dumps in ST22
Any faced problem like this before. What this problem means. Wondering if there is a table where the lock status is set. So that could be the reason why the locks are not visible in sm12, but still complains of having locks on characteric ZCUSTNUM>
Any suggestions appreciated.
Thanks,
BWer
Message was edited by: BWer
Message was edited by: BWer

Hi,
You have to close the cancelled change run before starting data loads for master data infoObjects that were included in the failed change run. This is done by running the change run again for your infoObjects. You can do this by using transaction RSATTR, select the infoObjects and execute the change run. Once the change run is completed successfully, you should be able to do your data load with no problems.
Also, you may want to check table RSDDAGGRMODSTATE to see if you have any change run job that are still open.

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

ERROR while running attribute change run.

hi sap xperts,
I got an error while running the attribute change run in a process chain.
At first i got an error "The action is locked by a change run"
SO I DID THE FOLLOWING STEPS.
1.RUN ATTRIB CHANGE RUN MANUALLY IT RUN SUCCESSFULLY,but the process chain is still red.
Q1.Is there any way to link the manually run attrib chnage to process chain so that the process chain becomes Green?
2.SM12 - realease the locks and right click the pc and repeat.It didn't work
Q1.While removing the locks what should we remove,bcoz i removed all the locks?
3.I again removed the lock and repeat the process but still i didn't work.Now its chowing "SQL ERROR OCCURED WHILE ACCESSING"
So the Process chain got stuck,Can any body help me to run the attrib chnage run.
If possible can anybody send the Process chain monitoring documents to my email id:
<email ID removed>
please.thanks in advance,i know how to say thanks in sdn.

At any point in time only one attribute change run can run in the system. The other ACR's will fail due to locks. In your case, to set the process chain to green, try the following steps.
Open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
The above steps will help you continue with the rest of the process chain (thus avoiding manual runs) but the failed step might still remain red. Hope this helps.

Change run error in Process Chain

Hi,
I got an error in running the change run step in the process chain.
The error is "The action is locked by a change run".
Could this mean that the change run was running when this step in the process chain was invoked.
I have a process chain with multiple(4) parallel processes and I would like to know from you gurus the best way to model such a process chain. Should I keep just one attribute change run at the end of the complete process chain or should I let the change run after every PC (each of the 4).
Any inputs will be appreciated
Thanks & Regards
Sid

Siddhartha,
Exactly, you need to keep the change run process at the end of the PC. no need to run the change run for every master data flow.
check whether change run is running? check in RS12 for locked entries.
All the best.
Regards,
Nagesh Ganisetti.

Problem with Customer master Attribute change run

Hello Experts
Master data load process chain for 0Customer failed in system at attribute change run step.
Because of that failed instance when ever we try to reload data get error message
"Attributes of characteristic 0CUSTOMER are locked by terminated change run 468502640"
"Lock NOT set for: Loading master data attributes"
It seems that last attribute change run step had locked master data object and lock is not yet released.
Kindly advice resoluiton to this problem.
Thanks in advance
Regards
Sudeep

Failed due to lock issue. check in SM12 you can find lock with respect to your change run 468502640.
Looks like master data step is running.
Wait till the masterdata for attributes of 0CUSTOMER completes and them repeat the attribute change run step.
To repat the attribute change run
Rsa1 --> Menu Tools -->Apply Hierarchy/change run or use transaction RSATTR
Click on monitor and Start Terminated Changes Runs(monitoring of Change runs)
Here you can check the failed Attribute change run object in red status.
after completion fo the master data and check the locks and click on execute button over there.

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 and Infocube Problem

Hi SAP BW Experts ,
I am getting the following problem
2 days back our production system was down when Attribute change run is running in a process chain . After the system is up I triggered the Attribute change run manually for that specific master data Object. But the jobs was cancled automatically. When I checked the Job log I found the following messages
InfoCube XXX is locked by a terminated change Run
System error: RSDU_TABLE_COPY_INI/DDIF_TABL_ACTIVATE /BIC/E200073 /BIC/E100073 0
Message no. DBMAN100
When I verified manage screen in the Infocube XXX , one request is not rolled up . when I tried to rollup that particular request manually again I am getting the same message InfoCube XXX is locked by a terminated change Run
When I tried to create Indexes on that Infocunbe XXX , Again I am getting the same message InfoCube XXX is locked by a terminated change Run
When I tried to load data in to that Infocube I am getting the same message InfoCube XXX is locked by a terminated change Run
The Steps Taken By Me:
1. In SM12 , there are no lock entries for the Infocube XXX
2. According to A.H.P reply I verified the Support package . We are having Import Support package 18 for 3.10( BW 3.10 patch 18 or SAPKW31018 )
so I think there is no problem from patch side.
So please let me know by doing which task , I can eliminate the error message InfoCube XXX is locked by a terminated change Run

I got this reference from one of other site. Hope this solves issues of most of our ques on this topic.
We faced this problem and reported to OSS. They solved our problem.Here is
the answer from OSS
I connected to your BWQ system. I checked the table RSDDAGGRMODSTATEand
found an entrie for a change run "not yet" finished.
CNSID CLOSEDFL TIMESTMP_START TIMESTMP_END TSTPNM
207,851,300 20,030,910,141,500 0 SIDTLHG
As you can see, the field CLOSEDFL is blank (should be 'X' for an ended
change run) and the field TIMESTMP_END is also zero.
You can also check with the function module RSDDS_CHANGERUN_MONITOR as
in note 388069 that both objects you reported are the ones involved
with thi change run error (Infocube ZINV and Infoobject ZELEM_PEP):
E_CR_STATE C
E_T_CHANM 1 Entry (IOBJNM = ZELEM_PEP)
E_T_HIEID 0 Entries
E_T_AGGRSTATE 1 Entry (AGGRID = 3QR79ZYB6VGSDS3C42HPXMA8S
ICUBE = ZINV)
E_T_MSG 1 Entry (IOBJNM = ZELEM_PEP)
You have two choices to solve this problem. You cn either:
1.- Restart the change run and let it finish with ok.
The change run usually fails due to database errors, tablespace
problems, and when some user manually cancel it (NEVER should be
done!!)
2.- Change manually the entry from table RSDDAGGRMODSTATE that isdescribed
above. Set the field CLOSEDFL with a 'X' and also fill the field
TIMESTMP_END with a value with the following format
yy,yym,mdd,hhm,mss. Use, for example, '20,030,910,181,500'
IMPORTANT!!!
After this change on table RSDDAGGRMODSTATE, you have todeactivate
all aggregates, activate again and refill them!!
Hope this solves your error. If the issue is solved, please close this
message with the [confirm] button.
Best regards,
David =C1lvarez
SAP Active Global Support
The answer refers to our problem.We chosed option 2. Here is the AbAPcode:
REPORT ZLOCKED .
tables: RSDDAGGRMODSTATE.
select * from RSDDAGGRMODSTATE where CLOSEDFL = ' '.
RSDDAGGRMODSTATE-CLOSEDFL = 'X'.
RSDDAGGRMODSTATE-TIMESTMP_END = 20020912195015.
MODIFY RSDDAGGRMODSTATE.
ENDSELECT.

Attribute Change Run process Locked for 0material..?

While loading Data from PSA(0Material field) to InfoCube,AttributeChangeRun had failed. How can we solve the problem means how we can load data to InfoCube after attribute change run successful.
Edited by: Mr D111 on May 12, 2010 2:41 PM

Hi,
What was the exact issue? As Attribute change run is a different step where as loading of data from PSA to cube is a different step...
So there is no reason of failure for attribute change run in between....
If ACR failed before to the loading of data to cube, then re-run the ACR from RSA1>Tools->aplly/monitor change run-->in the info objects list find the infoobject and execute....
Unless you clear this ACR failure issue you can't load the data to the cube as it may be in locked mode....
After this is successful, then u can load the data from PSA to cube.
rgds,

InfoCube blocked by Change run

Hi all,
we need to delete data for an InfoCube, it was blocked by a Change run that was taking some time running, so we cancel the process to delete first the data. The problem is that it still says that the InfoCube is blocked by the "canceled" change run process.
We run the process again to let it finnish and then delete the data, and the process never finnish, on the change run screen says that the process is running, on monitor says that is restructuring the aggregates for the cube that we want to empty, but there is no activity on SM50 and its been a whole day in this state.
The InfoCube is still blocked by the change run (that says that is running, but its not). What can i do to solve it ?
tnx a lot.
cheers

Hi Juan.......
We should not cancel any Change run...............bcoz if we manually cancel any change run.....lock will never get released........until we repeat the terminated Change run(Change Run id should be same).......
Also when a Change Run get cancelled automatically..........we should check the Log...........if it is a Terminated Change Run...........then again we should repeat the same Terminated Change Run.......
As per my knowledge...........u will not be able to find these locks in SM12.......
Due to this the infocube is still locked and the restructuring the aggregates job is not progressing..........
Do one thing................again cancel the Change run...........
First go to SM12 >> there u will find one Log for Change run..it will be like CHANGERUN 410465767 ...........where 410465767 is the Change run id...........then
As krishna told...............go to RSA1 >> In the top TOOLS tab >> Select * Apply Hierarchy/Attribute Change* >> Click on Monitor and Start terminated Change run >> there click on Start Change run with Set Filters.........it will restart the Terminated Change run.....
After that again Check in SM12...........whether the Change run id is same or not.............it should be same.......
I think this time u will not face any problem............and after completion of the Change run only..delete the cube content...........
Regards,
Debjani.......

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

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

Infocube locked by terminate change run

Similar Messages

Maybe you are looking for