You need to sign in to do that
Don't have an account?
Miki Tosic
SFDC Accounts - UNABLE TO LOCK ROW
We use IBM WebSphere Cast Iron to integrate to SFDC. Our Accounts integration executes once per hour, 24x7, and in general processes all data with few issues other than the expected various data issues. However, once per month we run a larger than normal 'upsert' process (i.e. 1000-3000 upserts), and invariably a significant portion of these experience :
UNABLE_TO_LOCK_ROW
unable to obtain exclusive access to this record
Can anyone offer any ideas on what to look for here? We never experience this error with the regular hourly executions (i.e. 50-300 upserts). What could possibly cause the lock issue in this situation? What should be looked for? Is there any way to resolve this issue?
Thanks a lot for any assistance.
Miki Tosic
Life Fitness
UNABLE_TO_LOCK_ROW
unable to obtain exclusive access to this record
Can anyone offer any ideas on what to look for here? We never experience this error with the regular hourly executions (i.e. 50-300 upserts). What could possibly cause the lock issue in this situation? What should be looked for? Is there any way to resolve this issue?
Thanks a lot for any assistance.
Miki Tosic
Life Fitness
All Answers
Can you please let me know, what you have done in Cast Iron to get rid of this error. We are also facing same issues when upserting opportunities.
I had to write a new Cast Iron orchestration to follow the original process, and re-process all data failed with UNABLE_TO_LOCK_ROW but this time synchronously and serially (no batch upserts), also per the advice of 'pcon'. This has worked for us.