Hi Shaun

What’s the version of IFS Application? As per the error it looks like syn optimizer try to access this table from multiple threads. But it’s odd why you see it the client device. Becasue we do not send oracle errors back to device. Could be some thing else is happening here.  

Regards

Kapila

@kathlk We are currently on Apps 8 with plans to upgrade to Apps 10 next year.

This error is presented to the Mobile device and also in mobile logs.

Hi Shaun,

Can I know at which step mobile users are seeing this error? Is it visible when users are aborting initialization and trying to start again? Also,It is best to wait until the initialization completes.

Regards,

Dharshika

If this is App8 track then Sync Optimizer might blocking oracle tables just because of slowness of sync and it can also indirectly cause user to re try init again. So first thing you can check is Sync timing. In app8 you should be able to see sync timing in each entity. Try to find poor sync entity and address it first/ 

@kathlk We do have issues with engineers reinitialising daily or a few times a day to resolve issues they are experiencing!  

Do you know where we go within Apps 8 to look at sync timing?

Is there any guidance or documentation around troubleshooting poor sync performance?

We have tried with Wifi and 4G connections on devices and both seem to experience similar behaviour.

Hi Shaun,

You can check the sync timing in Apps8 from the Synchronized Date field of the Synchronized Entities tab in the Mobile Users Screen. This shows the Date timestamp values for each entity. In Apps10, this can be viewed with more information.

Best regards,

Dharshika