@NEJANO ,

Is there any other failed transaction before this or is this the only failed transaction? It seems something is trying to update that same record but usually a lock shouldnt last for very long. Once lock is released you should be able to resend the FT.

Hi @Ibrahim Naazir , This is the only FT that exists for this user.

Hi @NEJANO ,

Then I guess database investigations need to be done. Check if there are any sessions running and what SQL is executed on these sessions. Maybe one of these is trying to update this record in the mobile_sync_data_tab and maybe its stuck or something.

If the assignment is completed is there any effects or concern its causing? Does it block you of any further functionality?

Did you also try to resend it again? 

Hi, For this FT only a couple of journal entries were in the queue, so we have deleted the FT. However, the same user has gotten the same FT for the next assignment as well. Any idea?

Does someone know from where MOBILE_SYNC_DATA_API is called? There are no dependencies in Oracle to that package which means it is not called from another method. I find no calls in the FNDMOB code available either.

The method that is called Modify__ method and that seems to be called from a PLSQL block. But what is calling that method and how is that done? Can that logic be executed parallelly and cause this problem?

Hi,

Mobile_Sync_Data_API is called via native containers. You will not see any PLSQL logic for Sync optimizer related functionalities. Going back to the original error, this is something can be seen in a environment where mobile transactions / Data Sync takes longer time to execute and result could ebe oracle LOCK error after XXX minutes. We do not allow same user executes PUSH, BATCH at the same time (No concurrent data sync). But we allow client to send transactions back to server. So FT can be seen in such case but FT get re process via a scheduled task (Default ever 15 min) to clear such errors. But if you see the same error after re process the FT, then this is something else I would say. Can you enable device Sync Trace while re process the transaction? Then we can see more traces. 

Thanks

Kapila