cancel
Showing results for 
Search instead for 
Did you mean: 

Attributes of characteristic 0CACONT_ACC locked by terminated change run

Former Member
0 Kudos

Hi,

I'm facing the following error message when running "Attribute Change Run" process of standard characteristic 0CACONT_ACC: "Lock NOT set for: Cargar atributos de datos maestros. Error 1 in the update. Attributes of characteristic 0CACONT_ACC are locked by terminated change run 433884123".

The real cause of this "Terminated change run 433884123" mentioned in error message, was "Some characteristics/hierarchies already locked in other change runs. Characteristic 0CACONT_ACC in change run 433884123 (start time: 20091117232203; user: ALEREMOTE)".

This attribute change run process is referenced in more than one process chain and this process changes attibutes of both characteristics 0CACONT_ACC and 0FC_ACCNTBP. Do you think this may be causing some trouble? I thought that it might be usefull to configurate separate attribute change process for each characteristic and avoid using the same process in more than one process chain. May it help?

I also tried the following in order to liberate locks:

1. Run RSA1 transaction

2. Tools -> Apply Hierarchy/Attibutes Change... menu option

3. Clic at "Monitor and Start terminated Change Runs" button (at the bottom of the screen)

4. Clic "Reset Status" button at Run ID 433884123

But, there I get "SAPSQL_ARRAY_INSERT_DUPREC - CX_SY_OPEN_SQL_DB" short dump and cannot reset status so that lock persists. I'm getting the error at "insert rsddchngprot from table l_t_chngprot." sentence. I have read that it could be caused to a duplicated key.

Instead of this, I understand that I have to solve the first error message and then liberate locks from 0CACONT_ACC and 0FC_ACCNTBP characteristics.

Does anybody know which is the real cause of the problem with this extractor? Could you please detail the step by step in order to solve this problem?

If you need aditional information, please let me know.

Thanks in advance.

Best regards,

Ana G. Miranda

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Whenever an Attribute changerun fails it locks all the objects included in that, so when u want to run some loads/roll-ups/indexes on that object it shows the error as locked by terminated changerun.

Now coming to ur issue, first we have to finish the terminated change run..., as tried by u to reset the status it was not working so once try to chk the locks in SM12 and delete them. and reset the status and execute...

still if the problem persists then we can use a FM in se37 in serious cases whcih was not recomemded by SAP...

Use RSDDS_AGGR_MOD_CLOSE in se37 and execute--->there give ur failed change run no(433884123) beside I_CNSID and execute...

It releases all the locks by that change run....and continue with ur further work/jobs...

--

rgds,

Edited by: Krishna Rao on Nov 24, 2009 8:41 PM

Former Member
0 Kudos

Hi Krishna Rao,

Thanks for your prompt response. It was really helpful. I could delete locked attributes by executing the FM you told me at SM37 then repeated change run process and it ended successfully. Now I'm loading the rest of the data to characteristic 0CACONT_ACC.

Which is the real cause of the change run process cancelation? I mean the one that generates the characteristics locks.

Besides that, I implemented this solution to solve another cancelation related to standard characteristic 0EQUIPMENT. It was a similar situation to 0CACONT_ACC but the diference was that I could delete locks in RSA1, Tools -> Apply Hierarchy/Attributes Change..., Monitor and Start Terminated Change Runs for 0EQUIPMENT. But after deleting it I repeated change run process and it ended with message error "Error updating the data records /BI0/XEQUIPMENT" and the lock reappeared.

So that I run RSDDS_AGGR_MOD_CLOSE FM for adecuated RUN ID and then everything was ok when repeating change run process. Whole process chain ended successfully.

Now my question is which actions are performed through the excution of this FM? Which is the diference with deleting locks through the menu option?

Thanks for your help.

Best regards,

Ana

Former Member
0 Kudos

Hi Krishna,

Locks for 0EQUIPMENT characteristic disappeared executing RSDDS_AGGR_MOD_CLOSE FM. After that I could make a full loading to it.

This full loading failed because of a lock. Two datapackages try to access the characteristic at the same time locking it each other. Do you know if there is any note to solve it? I guess that there should be something like wait until commit is done by the first datapackage. Do you know?

And, in second place, I tried to repeat the change run process after running the full data load and it also failed and generate lock for 0EQUIPMENT characteristic again.

Please, could you help me?

Thaks in advance.

Best regards.

Ana

Former Member
0 Kudos

Hi,

This happens soemtimes when u run full loads having huge data volumes..

If there are any locks during data loading that can be viewed in SM12 no need to run FM for this....u can delte that locks from SM12...and chk in SM51 is there any process going on for this loads...

if no process is running then u can manually update the failed/locked data packets one by one by right click on each data packet and select manual update.....

and then try to repeat the attribute change run.....here in this case don't run FM always as it is to crucial...

--

rgds

Edited by: Krishna Rao on Nov 27, 2009 8:23 PM

Former Member
0 Kudos

Krishna,

Full load ended sucessfully. Then, when I try to active manually 0EQUIPMENT data I get the following error message:

"Error updating the data records /BI0/XEQUIPMENT."

This time locks didn't appear again but data is not actived yet.