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

Similar Messages

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

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

How to run change run in process chain when it fails

HI All,
How to run attribute change run in process chain when it fails. Give me the procedure with clear description. Is there is any difference with 3.x versions in running this.
Thanks,
Pratap Reddy

Hi Pratap.
If BI Accelerator is not being implemented by ur company, in that case if change run fails u'll proceed by 'Repeat' process option as usual we do in 3.x.
If BIA is exists, in this scenario u can not repeat as we do in 3.x. U have to drop the indexes on cubes effecting that change run and run the change runs. Once it is finished recreate BIA Indexes on cubes.
Warm Regards,
Ramki

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.

BW : Query change run

Hi ,
Can anybody please tell me under what conditions the changerun gets "terminated".Please advise.I checked with alternatives but still finding no reason for the termination.
Thanks in advance,
Madhavi.

Hi,
you mean attribute change run??
When ever a change run fails it will give the reason in the log of the job....like infoobject is locked or something like that.
You should be able to see that.
Reason could be
1)Try to fill roll up or fill the aggregate at the time of change run.
2)Try to change infoobject or do any transports which does changes to cube or infooobject when change run is running.
3) Loading data in the cube or DSO using those characteristics which are part of change run at the same time when chain run is in process.
4) Loading data into any infoobject which is part of attribute change run.
5)Try to change aggregates duriong change run.
6) DSO activation step which have the option "SID creation during activation" running at the time of change run and using characteristics which are part of attribute change run.
Hope it clears.
Thanks
Ajeet

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.

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

Attribute Change Run aborted with an error :Not all data indexed for index

Hi,
I have an issue where the master data Attribute Change Run aborted with an error pointing to the BWA:
Attribute Change Run aborted with an error :Not all data indexed for index
we tried to load only 0 data into it,the error still occured.

Detail message is following:
not all data was indexed for index 'GBP_BIC:XYCH_098('0' for '114')
creation of The BIA INDEX for infocube 'YBC_SD015' terminated while filling

Continuation of aborted change run failed in BW 3.5

Similar Messages

Maybe you are looking for