Symptom
The delta synchronization fails randomly and takes really long time. There aren't any custom Offline OData settings in SMP.
From the network traffic:
- Deltas are being ignored, so the whole tables are being sent.
- Some tables are empty.
Error messages:
#WARN#com.sap.odata.offline.scripts.ODataSyncHandler##Delta link, http://<hostname>:<port>/com.COMPANYNAME.XYZ/Something1?$filter=(Something2%20eq%123456)&!deltatoken=ML_ODATA_123456_789102, expired; a new database is required for the Offline OData client. |
#DEBUG#com.sap.odata.offline.scripts.ODataSyncHandler##ML_SCRIPT Exit handle_DownloadData: remoteID=<remoteID> |
#ERROR##java.lang.NullPointerException: while trying to get the length of a null array loaded from local variable 'metadataVersion' |
Read more...
Environment
- SAP Mobile Platform (SMP) 3.0 - SP12 PL03 or prior
- SAP Mobile Platform (SMP) SDK 3.0 - Offline OData SDK
Product
Keywords
offline odata, delta, synch, fail, fails, failing, whole, entire, full, data, metadata, service, request, rows , KBA , MOB-SDK-OOD , SAP Mobile SDK Offline OData Client , MOB-ONP-OOD , SAP Mobile On Premise Offline OData Server , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.