SAP Knowledge Base Article - Preview

2445448 - Random delta synchronization issue - SMP 3.0

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##nosec_identity#Thread-19499ab265e-515b-4ac2-b638-a934650f6a8a#com.COMPANYNAME.XYZ#02151147-b446-4582-9d32-23f22a4afc81#RequestResponse#200#{SMPARCH-5015-otp-two-factor-authentication=false, ALWAYS-USE-APPLICATION-SECCONF-NON-BI=true, SMPSRVRUN2-1755-use-start-pattern-for-rewriting=false, SMPSRVRUN4-636-HTTP-Traffic-Tracing=false, SMPARCH-5684-tenant-cors-configuration=true, SMPARCH-5622-principal-connection-pooling=false, SMPARCH-4846-odp-cookie-store=true}##Delta link, http://<hostname>:<port>/com.COMPANYNAME.XYZ/VActivitys?$filter=(PlantId%20eq%2046040)&!deltatoken=ML_ODATA_3710159_3693131_3710160, expired; a new database is required for the Offline OData client. |

#DEBUG#com.sap.odata.offline.scripts.ODataSyncHandler###Thread-143#########ML_SCRIPT Exit handle_DownloadData: remoteID=3da13d04-e930-4afd-9a18-b0761b16ca3c |
#ERROR#System.err###Thread-143#########java.lang.NullPointerException: while trying to get the length of a null array loaded from local variable 'metadataVersion' |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.MetadataCache$MetadataCacheKey.<init>(MetadataCache.java:164) |
#+0100#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.MetadataCache.remove(MetadataCache.java:112) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.ODataSyncHandler.removeFromMetadataCache(ODataSyncHandler.java:502) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.ODataSyncHandler.processMetadata(ODataSyncHandler.java:604) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.ODataSyncHandler.doHandleDownloadData(ODataSyncHandler.java:288) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.ODataSyncHandler$2.call(ODataSyncHandler.java:265) |
#ERROR#System.err###Thread-143######### at com.sap.mobile.platform.server.mobilink.MODataServiceSupport.executeWithContext(MODataServiceSupport.java:123) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.util.MODataServiceImpl.executeWithContext(MODataServiceImpl.java:85) |
#ERROR#System.err###Thread-143######### at com.sap.odata.offline.scripts.ODataSyncHandler.handle_DownloadData(ODataSyncHandler.java:270) |
#ERROR#System.err###Thread-143######### at sun.reflect.GeneratedMethodAccessor257.invoke(Unknown Source) |
#ERROR#System.err###Thread-143######### at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) |
#ERROR#System.err###Thread-143######### at java.lang.reflect.Method.invoke(Method.java:497) |
#ERROR#System.err###Thread-143######### at ianywhere.ml.script.MethodInfo.invoke(MethodInfo.java:12304) |


Read more...

Environment

  • SAP Mobile Platform (SMP) 3.0 - SP12 PL03 or prior
  • Offline OData application

Product

SAP Mobile Platform 3.0

Keywords

KBA , MOB-SDK-OOD , SAP Mobile SDK Offline OData Client , Problem

About this page

This 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.