Change run program failing..

Hello BW experts,
I have checked that the change run program is again and again failed while loading master data.
After executing the Change run program I check the related job in SM37. It get successfuly completed.
But if I again check the Change run program , I can see the same master data infoobject again.
I run this attribute change run program 5 times and everytime again and again I observe that the same Master data infoobject is present in the Attribute change run program . though the job is successfully completed in SM37.
Due to this error we are also getting message ALEREMOTE locks and can not able to load master data .
Any help please.
Best regards,
Amol.

Amol
Don't run the this program again and again, that's the reason why ALEREMOTE is getting Locked. Please check Transaction code SM51 also along with SM37 because jobs must be running at the back end in SM51. Make sure the jobs completely and stsrt the new job.
Hope this helps
Thanks
Sat

Similar Messages

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

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

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.

Change run failure: Master data still in M version

Hi Experts,
We have an attribute change run that failed. We checked the master data and there are still entries in M version. We have tried to execute change run manually, but the infoobject is not listed. Checking RSRV we have the error "value 1000 for 0MATERIAL is in external and not internal format," and "there are values with the wrong internal format in the SID table."
We are thinking this is a probable reason why change run is failing.

Hi.........
Check the conversion Routine for 0MATERIAL.........What conversion routine u hav used.........We r using ALPHA.......this is the standard one........hav u changed it.......
Check this...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7108a690-0201-0010-4cbc-9bca94f9ad9c
Also u can check the Log of the Change run..............Go to RSA1 >> In the top TOOLS tab >> Apply Hierarchy/Attribute Change >> Select the Attribute Change run and click on LOG....
Regards,
Debjani....

Failed change run in CHANGERUNMONI

Hi all,
How to change the status of a failed change run in CHANGERUNMONI, actually one of our change run failed so we are trying to restart it using CHANGERUNMONI, and trying to restart the status forcefully, but it's giving us short dump.
Please give some advice, its urgent.
Regards,
Partha

nformation on where terminated
 Termination occurred in the ABAP program "RSDDS_CHANGERUN_MONITOR" - in
 "ROLLBACK_CHANGERUN".
 The main program was "RSDDS_CHANGERUN_MONITOR ".
In the source code you have the termination point in line 152
 of the (Include) program "DS_CHANGERUN_MONITOR_F02".
 The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 procedure "ROLLBACK_CHANGERUN" "(METHOD)", but it was neither handled locally
 nor declared
 in the RAISING clause of its signature.
The procedure is in program "RSDDS_CHANGERUN_MONITOR "; its source code begins
 in line
 126 of the (Include program "DS_CHANGERUN_MONITOR_F02 ".
The ABAP code is
Source Code Extract
Line SourceCde
122 aggregatesdeactivate( l_th_node ).
123
124 ENDMETHOD.
125
126 method rollback_changerun.
127 data: l_TS_STATE_CR TYPE RSDDS_TS_STATE_CR,
128 l_s_state type rsdds_s_state_cr,
129 l_t_chngprot type standard table of rsddchngprot
130 with non-unique key TABLE_LINE,
131 l_s_chngprot type rsddchngprot.
132
133 * check that the changerun is not running
134 CALL FUNCTION 'RSDDS_AGGR_MOD_STATE_GET'
135 IMPORTING E_TS_STATE_CR = l_TS_STATE_CR.
136 read table l_ts_state_cr into l_s_state
137 with table KEY CNSID = i_cnsid.
138 check sy-subrc = 0
139 and l_s_state-running = rs_c_false.
140
141 * copy selected characteristics and hierarchies
142 * in protocol table
143 select * from rsddchngprot
144 into table l_t_chngprot
145 where cnsid = i_cnsid
146 and ( chabasnm <> space
147 or hieid <> space ).
148 l_s_chngprot-cnsid = 0.
149 modify l_t_chngprot from l_s_chngprot
150 TRANSPORTING cnsid
 TRANSPORTING cnsid
 where cnsid = i_cnsid.
 insert rsddchngprot from table l_t_chngprot.
 CALL FUNCTION 'RSDDS_AGGR_MOD_CLOSE'
 EXPORTING i_cnsid = i_cnsid.
 call function 'DB_COMMIT'.
endmethod.
METHOD getcr_objects.
 DATA: l_s_chabasnm_cr TYPE rsdds_s_chabasnm_cr,
 l_s_chabasnm TYPE rsdds_s_range_chabasnm,
 l_s_hier_cr TYPE rsdds_s_hier_cr,
 l_s_hieid TYPE rsdds_s_range_hieid.
 READ TABLE p_ts_state_cr INTO e_s_state
 WITH TABLE KEY cnsid = i_cnsid.
 IF sy-subrc NE 0.
 MESSAGE x299(brain) WITH 'RSDDS_CHANGERUN_MONITOR' '_GET_CR_OBJECTS' .
 ENDIF.
 l_s_chabasnm-sign = rs_c_range_sign-including.
 l_s_chabasnm-option = rs_c_range_opt-equal.
 LOOP AT p_ts_chabasnm_cr INTO l_s_chabasnm_cr
 WHERE cnsid = i_cnsid.

Getting no attributes changes after change run monitor program is executed

Hi ,
We have a z-program where we are calling function module RSDDS_CHANGE_MONITOR . The structure of this function module is changes after upgrade from BI 3.5 to 7.0. Accordingly i have adjusted the z-program . But the result is No Attribute Change Run Found .
The function module called is as follows
CALL FUNCTION 'RSDDS_CHANGERUN_MONITOR'
EXPORTING
I_WITH_DETAILS = RS_C_TRUE
I_T_CHABASNM =
I_T_HIEID =
 IMPORTING
 E_TS_STATE_CR = l_cr_state
 E_TS_CHANM_IN_AGGR = l_t_chanm
 E_TS_HIER_CR = l_t_hieid
 E_TS_CHABASNM_CR =
 E_T_AGGREGATE_CR = l_t_aggrstate
 E_TS_TREXAGGR_CR =
 E_TSX_MSG_CR = l_t_msg
 EXCEPTIONS
 ERROR = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
The l_cr_state has the details of the status in BI 7.0
But after upgrade , its empty.
Pls help on the issue.
Regards,
Sarang

go through this link:
http://help.sap.com/saphelp_nw04/helpdata/en/64/32a5682e6a4e0cbb3f8a33970d11a8/frameset.htm

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

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

Attr change run failed with exception

hi all,
My process chain failed at ACR( attr change run) with exception
"UNCAUGHT EXCEPTION" ...I 've again scheduled that process but it again
got failed.
I am not able to undestand what is the problem?
does anybody have any idea how to resolve this?

hi arun,
that was a short dump with the above exception .

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

Change run program failing..

Similar Messages

Maybe you are looking for