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........

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 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 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.

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

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

Attribute Change Run in Process Chain failed with SQL 942 error

Hi,
Attribute change run in th eprocess chain failed with the message " SQL Error 942" and ran succesfully after repeating the step.Searched in Forums for similar error but the solutions were not apt.
Any pointers would be of great help!!
Thanks in advance,
Bhagyarekha.

Hi Bhagyarekha,
The reason behind that error could be:
An attempt is made to activate a characteristic whose compounding was replaced and whose navigation attributes were simultaneously deleted. The replacement of the compounding temporarily deletes the M view of the characteristic during internal activation. The process of deleting navigation attributes involves converting the attribute SID tables. However, the M-view of the characteristic, which has just been deleted, is needed for this conversion.
Check this SAP Note:
Note 684405 - Replacing the compounding and deleting navigation attr.
Hope it helps.
Veerendra.

Attribute change run process type failed with short dump

Hi all,
In the process chain Attribute change run process type failed with short dump. I checked the locks in SM12 but there are no locks associated. I checked in the attribute change run screen through RSA1 -> infoobject list but there are no infoobjects there. I think the ACR was completed successfully, still the process type in the PC was in red colour. What to do and let me know what happened here.
Thanks,
Jack

1. This kind of scenario is extremely rare but it happens sometimes. It might be the case that 2 attribute change runs are running at the same time.
2. Same IO is being used in Differnet PC and getting activated.
I think if this frequently occurs you need to check at the time of locking all running jobs and see whether anywhere else or simultaneously 2 ACR are running.
Please do close the thread if that answers your questions. Please help us keep the forums clean and open useful information only.
For more information search on help.sap.com and you will get lots of material.
Regards.
Den

Due to attribute change run(sid's is missing)...process chain is failed

Hi All,
Due to attribute change run (SID's is missing) process chain is failed.kindly suggest me how we can rectify for this issue.
Thanks
Ragav

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

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.

Issue: attributes change run triggers the rebuilt of 0IC_C03 aggregates

Hello Guru,
I am facing to a problem that I don't understand.
Here is below the detail of the messages of a '3-infoobjects attributes change run' step of a Master Data process chain.
22:06:14     Job started
22:06:14     Step 001 started (program RSPROCESS, variant &0000000231235, user ID RFC_BW)
22:06:16     Starting process type ATTRIBCHAN with 3 objects...
22:06:16     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 22061600
22:06:16     Editing of aggregate 100139; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 22:06:16/07.07.2010
22:06:18     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 22061601
22:06:18     Editing of aggregate 100143; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 22:06:18/07.07.2010
23:02:29     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 23022900
23:02:29     Editing of aggregate 100140; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 23:02:29/07.07.2010
23:52:38     Starting process type MDHIERACT with 2 objects...
23:52:39     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIACTI_D8FCR9Y1NWOP2T4F76FYE0HDG with ID 23523900
23:52:39     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIACTI_D8FCR9Y1NWOP2T4F76FYE0HDG with ID 23523901
23:53:10     Aggregate 100139: Repair indexes
23:57:14     Aggregate 100140: Repair indexes
00:17:23     Aggregate 100143: Repair indexes
00:50:09     3 aggregates are condensed
00:50:09     Starting process type CONDAGGR with 3 objects...
00:50:10     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501000
00:50:10     Editing of aggregate 100143; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:10/08.07.2010
00:50:10     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501001
00:50:10     Editing of aggregate 100140; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:10/08.07.2010
00:50:16     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501600
00:50:16     Editing of aggregate 100139; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:16/08.07.2010
00:50:22     Hierarchy/attribute change successfully carried out
00:50:23     Event RSPROCESS with parameter D59BE8XWZMHY0IFP2VLEFP671 successfully triggered
00:50:23     Job finished
As you can observe, the step takes almost 3 hours !!!!!!! After anlyses BICHNG_* concerns
22:06:16 Job started
22:06:16 Step 001 started (program RSBATCH_EXECUTE_PROZESS, variant &0000000891873, user ID RFC_BW)
22:06:18 Aggregate 100139( 0IC_C03) is being adapted / rebuilt
22:06:18 Statistic UID of the aggregate process: 'D8FC4Q9KSAMRDWQ1RDPPKMF3O' (RSDDSTATAGGR)
22:06:27 Aggregate 100139: Read (1) from table /BI0/E0ICC03_ (max 500000 records)22:06:27 SQL: 07.07.2010 22:06:27 RFC_BW
I don't understand what is the link between the '3-infoobjects attributes change run' (BBATCH, 0MAT_SALES, 0MAT_PLANT) and the rebuilt of 3 0IC_C03 (Material Stocks/Movements) aggregates (why does the 'attribute chan run' trigger the rebuit of aggregates???).
The rebuilt of the 3 aggregates takes 1 416, 3 366, 3 009 secondes...
Does anyone understand my problematic? If not I can give you more details.
Thanks in advance for your help.
Samuel

1/ Exactly Fred
Here is the definitions of the aggregate:
100139:
0PLANT
0STOR_LOC
0MAT_PLANT__0VAL_CLASS
0STOCKCAT
0STOCKTYPE
BMODIFIC
BMVTSTOCK
0MATL_TYPE
0CALxxx
2/ For my information in the aggregate 100140 , does the presence of BBATCH (one of the 3 IO) trigger the rebuilt or is it only 0MAT_PLANT__0VAL_CLASS ?
100140:
0PLANT
0STOR_LOC
0MATERIAL
0MAT_PLANT__0VAL_CLASS
BBATCH
0STOCKCAT
0STOCKTYPE
BMODIFIC
BMVTSTOCK
0MATL_TYPE
0CALxxx
3/ In the same process chain, I have another Attributes Change Run: 0MATERIAL. Several active aggregates using 0MATERIAL__0MATL_TYPE are built on a CO-PA cube.
Why did the '0MATERIAL Attributes Change Run' rebuild no aggregate? (see below)
22:06:04     Job started
22:06:04     Step 001 started (program RSPROCESS, variant &0000000231238, user ID RFC_BW)
22:06:06     Activation of master data for 0MATERIAL
22:06:07     154 Data records deleted
22:06:11     154 Data records deleted
22:06:12     154 Data records updated
22:06:13     154 Data records updated
22:06:13     0 aggregates are condensed
22:06:14     Hierarchy/attribute change successfully carried out
22:06:14     Event RSPROCESS with parameter D59BEEE069HKRCRU0ZPYFUPB1 successfully triggered
22:06:14     Job finished
Samuel

Attribute change run

Hi all,
As Iu2019m very new to SAP BW, can u plz tell me how to complete the attribute change run that has failed in a process chain?

Hi
Goto T-code: SE38, Run program: RSDDS_CHANGERUN_MONITOR.
It will show the staus of change runs. Here you will get execute button option to execute it again.
Note: It might take bit long time to open.
Thanks,
Jitender.
Edited by: Jitenderkumar Danduvia on Mar 30, 2010 11:00 AM

Continuation of aborted change run failed in BW 3.5

Hello experts,
everytime when an attribute / hierarchy change run has been aborted (by means of unexpected runtime errors) I failed in starting it next time. Error RSENQ 2 ("Lock not set for: activation of hierarchy") occured in this case. I found a way to overcome this by manually setting flag CLOSEDFL = X in table RSDDAGGRMODSTATE.
Now I found SAP note 903886 which forbids to do so by reason of potential inconsistencies.
Does anybody know how to handle the specified situation in a right way?
Thanks in advance for your help,
Oliver

Hello Shabar,
I implicitly postulate that the reasons for the failure always have been detected before trying once more.
For example, implementing a wrong SAP note (1006192) caused runtime errors. After resetting the note implementation the error disappeared.
Sorry, this was not my question!
The point is that change run failes as long as the flag has not been set in RSDDAGGRMODSTATE even if the reason for the failure has been fixed.
Yours,
Oliver

How to trigger attribute change run manaully

Hi all,
i need to update a master data object with new data. i have the flat file. i scheduled info package and exected DTP (datasource -
>Master data object). now I need to trigger attibute change run manually. How would i do that?
Pls help
Please search the forum before posting a thread
Edited by: Pravender on Feb 4, 2012 11:16 AM

HI Ramya,
Activation master data is different than running Attribute change run.
Activate master data will only activate the master data in info object(Change the records in M version to A version.
Attribute Change Run will activate the master data in info object and updates the aggregates with new data if you have any aggregates built on this info object.
Be specific while asking the question.
Regards,
Venkatesh

Attribute change Run Failed/Scheduled

Similar Messages

Maybe you are looking for