- Oracle uses snapshot isolation for all transactions. In order to not lose data that may be committed in an open transaction after the synchronization time, the MobiLink synchronization server generates the last download time for the next timestamp-based synchronization as the start time of the longest running open transaction on the Oracle Database server.
- If an Oracle Database instance manages multiple databases, the oldest transaction used by the MobiLink synchronization server is selected among all transactions in all databases, even if they are not directly involved in synchronization.
- The timestamp generated may be older than the current open transaction time for the current database, causing a repetition of data to be sent to remotes.
- SAP SQL Anywhere / MobiLink Synchronization Server
- Oracle Database (all supported versions)
SAP SQL Anywhere 16.0 ; SAP SQL Anywhere 17.0 ; SAP Sybase SQL Anywhere 12.0
-dt option switch , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.